Manual 6130
Manual 6130
Nortel
Optical Multiservice Edge
6130
Planning Guide
What’s inside...
Introduction
Feature overview
Configurations and interworking
Hardware description
User interface description
OAM&P description
Technical specifications
Ordering information and system engineering rules
Technical assistance
Appendix A: Data communications planning
*N0082986*
Copyright © 2006 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. Except as expressly authorized in writing by Nortel Networks, the holder is granted no rights to use the
information contained herein.
Nortel, the Nortel logo, the Globemark are trademarks of Nortel Networks.
Printed in Canada
iii
Publication history 0
September 2006
Standard issue 1 of the document.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
v
Contents 0
Introduction 1-1
OME6130 applications 1-3
OME6130 service interfaces 1-3
Small form-factor pluggable interfaces 1-4
Point-to-point optical broadband services 1-4
TDM switching 1-5
Network management 1-5
Key features and benefits 1-6
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Contents vii
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Contents ix
equipment. 10-75
DCN example 11 - Using VC12 management channels through OM4000 network
to reach remote OME6130 network elements in SNCP ring with OM4000 and
legacy OSI network elements. Transparent DCC used to provided resilient
OSI communications. 10-82
DCN example 12 - Using E1 and VC12 management channels to reach remote
OME6130 network elements in SNCP ring with OM4000 and legacy OSI
network element. Transparent DCC used to provided resilient OSI
communications. 10-88
IP networks, addressing, and masks 10-93
Dotted decimal notation for IP addresses 10-94
Circuitless IP interface 10-95
ARP 10-96
IP routing protocols 10-97
OSPF 10-97
Route preference 10-102
Static and default routes 10-103
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
xi
Audience
The following members of your company are the intended audience of this
Nortel technical publication (NTP):
• planners
• provisioners
• network administrators
• transmission standards engineers
• maintenance personnel
Network
Interworking Guide
(NTCA68CA)
Planning Guide
(NT6Q92MA)
References
This document refers to the following Optical Multiservice Edge 6130 NTPs:
• About the OME6130 NTP Library, 323-1855-090
• Local Craft Access User Guide, 323-1855-195
• Installation, Commissioning and Testing Procedures, 323-1855-201
• Provisioning and Protection Switching Procedures, 323-1855-310
• Trouble Clearing and Module Replacement Procedures, 323-1855-543
This document refers to the following OME6130 supporting documentation:
• Data Communications Network Planning Guide, NTR710AM
• Network Interworking Guide, NTCA68CA
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
1-1
Introduction 1-
The OME6130 Release 1.0 supports SDH networking. SONET support will be
provided in the next release. Figure 1-1 displays the OME6130 network
element.
Figure 1-1
OME6130 network element
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Introduction 1-3
OME6130 applications
The OME6130 offers significant value across a range of network applications.
The principal OME6130 applications are:
• Feeder for Metro Optical networks: The OME6130 can be subtended
from Nortel’s larger Optical platforms to collect 10/100BT Ethernet,
Gigabit Ethernet, E1/DS1, E3/DS3 and STM-1o/e traffic from the Access
Edge. Its compact footprint and low price make it well suited for smaller
customer locations. The OME6130 can be subtended either in a SNCP or
1+1 MSP configuration. The capability to manage OME6130 using path
DCC bytes also allows it to be managed remotely over leased
STM-1/STM-4 circuits. The Regenerator Section and Multiplexer Section
overhead tunnel capability provides further flexibility in managing other
SDH equipment within the same ring.
• Private Enterprise Networks: The OME6130 can be deployed in smaller
private networks providing transport of 10/100BT Ethernet, Gigabit
Ethernet, E1/DS1, E3/DS3 and STM-1o/e services between sites. A light
weight management solution is available for such applications consisting
of a web-based craft interface running on the OME6130 for NE
provisioning and SNMP north bound interface for reporting alarms to a
generic SNMP alarm browser.
• Wireless Backhaul: The OME6130 is also well suited for wireless
backhaul applications where both space and cost are paramount. The
OME6130 can be used as a cost-effective backhaul of today’s E1/DS1s and
will support the 3G network transition to Ethernet.
Nortel Networks has been collaborating closely with leading SFP vendors to
improve the reliability, robustness and manageability of SFPs. The use of such
carrier-grade SFP technology enables service providers to enjoy the flexibility
of provisioning the interfaces per the requirements of the specific application.
SFPs also reduce the cost of sparing by enabling an upgrade of the optical line
interfaces as they become readily available.
Figure 1-2
Pluggable optical modules summary
155/622/1000 Mbps
155/622 Mbit/s
- Carrier grade
- Service tolerance:
- Reach (SR/IR/LR)
(STM-1/STM-4) OC-12/STM-4 future)
- Rate (OC-3/STM-1,
- GE (future)
- CWDM with wavelength per pluggable slot
- Operational simplification
- Expenditure matched with reach requirements
- CAPEX savings through reduced sparing
GFP provides an efficient mechanism for Ethernet transport over a SDH core
network via efficiently mapping varying client signals into SDH VC-12, VC-3
and VC-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 Ethernet signal, and enables
consistent SDH based PMs through the network. Since the Ethernet is mapped
into SDH frames, the existing core network can transport the Ethernet frames
transparently.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Introduction 1-5
Along with VCAT the OME6130 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 VCs as required.
TDM switching
In the OME6130 architecture, traffic is switched between working and
protection line interfaces via the switch matrix in the 2x155/622M aggregate
circuit pack.
All ingress service traffic is mapped into VC-11, VC-12, VC-3 or VC-4
containers and directed towards the switch matrix which is configured to
switch the incoming traffic to the appropriate line interface. The switch matrix
allows any input channel to be connected to any output channel. Hairpinning
is also supported between client ports.
Network management
The OME6130 is managed as an integral part of Nortel Networks' market
proven end-to-end optical portfolio management capabilities. This framework
supports a sophisticated and highly customizable desktop providing
centralized topology view and fault management, centralized launch pad for a
full suite of management applications, easy to use nodal managers and
seamless network element reach-through for Nortel Networks' complete
optical networks portfolio. These network management capabilities are
supported by the Optical Manager and Optical Application Platform, such as
OMEA and Optical Network Manager (formerly known as Preside), in
alignment with Nortel Networks overall optical networks portfolio.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
2-1
Feature overview 2-
• SDH support
• hardware:
— chassis
— 2x155/622M aggregate circuit pack
— service interface circuit packs:
– 8x10/100BT L1 circuit pack
– 2xGE L1 circuit pack
– 28xE1/DS1 circuit pack
– 3xE3/DS3 circuit pack
– 2x155M circuit pack
— pluggable modules:
– SR-0, I-1.1/I-4.1, S-1.1/S-4.1, L-1.1/L-4.1, L-1.2/L-4.2 SFPs
– CWDM SFPs (8 wavelengths, 1470 nm to 1610 nm)
– STM-1 BX, STM-1e
– GE SX, LX
— redundant DC power supply units
— OAM circuit pack
— fan module
— filler faceplate
• System Line-Up and Test (SLAT) procedure
• synchronization:
— SSM
— E1 BITS synchronization
— line timing
— port (E1 facility)
• fault management:
— alarm reporting control
— regenerator section alarms
— multiplex section alarms
— high order path alarms
— low order path alarms
— E1/E3/DS1/DS3 alarms
— 10/100BT Ethernet and Gigabit Ethernet alarms
• performance monitoring:
— SDH regenerator section, multiplex section PM parameters
— high order path PM parameters
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Feature overview 2-3
Table 2-1
Summary of features for current releases
OME6130 hardware
Single feed DC power supply unit Yes DC Power supply unit on page 4-4
8x10/100BT L1 Yes
2xGE L1 Yes
Tributary interface circuit pack
28xE1/DS1 Yes descriptions on page 4-10
3xE3/DS3 Yes
2x155M Yes
SFP modules
GE SX, LX Yes
Configurations
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Feature overview 2-5
Connection management
VC11, VC12, VC3 and VC4 cross-connects Yes Connection management on page
6-13
Service Mapping
Traffic protection
Synchronization
Performance monitoring
Loopbacks
Data management
NE data backup and restore Yes Backing up and restoring the network
element database on page 6-42
Topology Adjacency
Topology adjacency provisioning and discovery Yes Topology adjacency on page 6-41
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Feature overview 2-7
IP addressing Yes
Enable/disable OSPF per network interface Yes Data communications on page 6-22
IP over OSI GRE tunnel (auto or static) Yes and Appendix A: Data
communications planning on page
PPP/LAPD over DCC Yes 10-1
OME6130 management
Interworking
Physical description
The OME6130 hardware platform consists of a chassis which fits in a standard
19 in., 21 in., or 23 in. rack. The chassis is equipped with the following circuit
packs:
• one 2x155/622M aggregate circuit pack
• up to 4 service interfaces:
– 8x10/100BT L1 circuit pack
– 2xGE L1 circuit pack
– 28xE1/DS1 circuit pack
– 3xE3/DS3 circuit pack
– 2x155M circuit pack
• two single feed DC power supply unit
• OAM circuit pack
• fan module
• filler faceplate
Figure 2-1 provides an overview of the OME6130 chassis layout.
Figure 2-1
OME6130 chassis layout
PSU (2) OAM Tributary slots (4) Aggregate slots (2) Fan
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Feature overview 2-9
Table 2-2
OME6130 tributary circuit pack summary
Circuit pack Port density/ Notes
circuit pack
28xE1/DS1 28 • unframed E1
• CRC4 framed E1
• unframed DS1
• ESF DS1
3xE3/DS3 3 • unframed E3
• G.832 framed E3
• unframed DS3
• ASYNC framed DS3
For more information about the tributary circuit packs, refer to Tributary
interface circuit pack descriptions on page 4-10. For more information about
slot equipping rules, refer to Chassis layout on page 8-2.
For more information, refer to System Line-up and Test (SLAT) on page 6-2
Configurations
OME6130 currently supports the following configurations for the STM-1/4
line interfaces.
1+1 MSP protection
OME6130 supports 1+1 Multiplex Section Protection (MSP) configurations.
For more information, refer to 1+1 MSP on page 3-1.
SNCP
OME6130 supports Sub-network connection protection (SNCP) ring
configurations.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Feature overview 2-11
Connection management
OME6130 supports nodal port-to-port connection management. OME6130
supports the ability to provision bidirectional and unidirectional connections
at VC11, VC12, VC3, and VC4 rates.
Service mapping
All services (Ethernet, E1, DS1, E3, and DS3) are mapped to appropriate SDH
containers.
The OME6130 uses Generic Framing Procedure (GFP) as its standards based
SDH mapping for Ethernet services. GFP is an ITU standard (G.7041) which
describes a flexible mapping technique for transparent transport of multiple
protocols in SDH. GFP-Framed (GFP-F) is used for mapping Ethernet to SDH
tributaries and containers.
Traffic protection
OME6130 supports 1+1 MSP and 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-4
provides a summary of the protection schemes supported in this release.
Table 2-4
Traffic protection summary
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.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Feature overview 2-13
The following alarm reporting control features are supported: profile based
path alarm control, alarm filter, and facility alarm reporting. The user has the
option to enable or disable alarm reporting to the management system, on a per
alarm type and per port basis.
For more information, refer to Alarm and event management on page 6-27.
Performance monitoring
Performance monitoring (PM) refers to the continuous collection, analysis and
reporting of the performance data of a monitored entity. This monitoring
allows early detection of service degradations and facilitates preventive
maintenance without interruption of service. PMs can also be used to facilitate
trouble and fault isolation. Performance monitoring is performed on all
in-service optical and electrical interface ports.
Loopbacks
The OME6130 supports facility loopbacks on the STM-1/4, PDH/DSn and GE
ports, and terminal loopbacks on all ports, including the 10/100 Ethernet ports
on the 8x10/100BT L1 circuit pack. The loopbacks provide a quick and
reliable way to sectionalize connections during testing and troubleshooting.
Data management
The OME6130 is responsible for the resilience of its provisioning data and
ensures that a copy is preserved on flash.
For more information, refer to Backing up and restoring the network element
database on page 6-42.
Topology Adjacency
Through OMEA management, the topology adjacency feature on the
OME6130 provides the capability to manually provision the neighbor status
information or to automatically discover it.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Feature overview 2-15
OME6130 management
Local Craft Access Terminal
The OME6130 supports a comprehensive suite of OAM&P functionality
which can be managed through a web-based local craft access user interface.
The local craft user interface is a graphical, nodal management tool that is
inherent on the network element software load and can be launched via a web
browser.
The local craft access user interface is launched from a web browser which can
be running on Windows, UNIX or Solaris workstations ensuring field
technicians and NOC operators are operating with the same view.
SNMP traps
The OME6130 system events can be monitored through SNMP traps raised by
the NE, based on the MIB tables.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
3-1
This chapter describes how the Optical Multiservice Edge 6130 (OME6130)
Release 1.0 fits in a network and interworks with other Nortel Networks
products. Table 3-1 lists the topics in this chapter.
Table 3-1
Topics in this chapter
Topic Page
SNCP 3-1
1+1 MSP
1+1 Multiplex Section Protection (MSP) configuration is a line level traffic
protection scheme and consists of a point-point configuration with two optical
fiber pairs carrying the traffic (one for working and the other for protection).
The 1+1 MSP protection is also supported for STM-1e interface. Traffic is
carried on both working and protection STM-1/4 lines and the receiving
interfaces determine which line to select based on signal quality or
user-initiated actions. The OME6130 supports 1+1 MSP protection switching
on the STM-1/4 line interfaces.
For more information about 1+1 MSP protection configuration rules, refer to
Shelf equipping rules on page 8-4. For more information about the 1+1 MSP
protection scheme, refer to 1+1 MSP traffic protection on page 6-18.
SNCP
A Sub-network connection protection (SNCP) is a path level traffic protection
scheme. In SNCP configuration, the destination node selects one of the two
paths based on the quality of the received signal.
Unprotected configuration
OME6130 unprotected configuration on the STM-1/4 line interface ports has
a single pair of optical fibers interconnecting network elements. The
unprotected configuration is supported for STM-1e interface. Unprotected
connection configuration is also supported on all tributary circuit packs
available in this release:
• 8x10/100BT L1 circuit pack
• 2xGE L1 circuit pack
• 28xE1/DS1 circuit pack
• 3xE3/DS3 circuit pack
• 2x155M circuit pack
For more information about the unprotected protection scheme, refer to
Unprotected connections on page 6-21.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Configurations and interworking 3-3
As shown in Table 3-2, OME6130 Release 1.0 operates with the following
network management software.
Table 3-2
Network management software that operates with OME6130 Release 1.0
In order to be able to launch the Craft UI from the Optical Network Manager
(ONM AP) platform, a file needs to be installed on the ONM AP server. Refer
to the Optical Manager Element Adapter NTP Library, Installation and
Configuration Guide, 450-3121-201 for more information.
Product Release
TN-1C 7
TN-1X 9
Note: See Interoperating with non-Nortel portfolio on page 2-16 for more
details.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
4-1
Hardware description 4-
Topic Page
Hardware architecture 4-2
Chassis 4-3
DC Power supply unit 4-4
Fan module 4-5
OAM circuit pack 4-6
2x155/622M aggregate circuit pack 4-8
Tributary interface circuit pack descriptions 4-10
Filler faceplate 4-18
E1 75 ohm termination panel 4-18
Cable routing 4-19
Hardware architecture
The OME6130 platform, as shown in Figure 4-1, consists of a chassis which
can be equipped with the following cards:
• 2x155/622M aggregate circuit pack
• Tributary interface circuit packs:
– 8x10/100BT L1 circuit pack
– 2xGE L1 circuit pack
– 28xE1/DS1 circuit pack
– 3xE3/DS3 circuit pack
– 2x155M circuit pack
• single feed DC power supply unit
• OAM circuit pack
• fan module
Figure 4-1
OME6130 chassis dimensions
height 4 U
176 mm
(6.9 in.)
width
445 mm
(17.5 in.)
depth (shelf only)
231 mm (9.1 in.)
depth including cable
routing brackets
295 mm (11.6 in.)
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-3
Chassis
Figure 4-2 provides an overview of the OME6130 chassis layout.
Figure 4-2
OME6130 chassis layout
PSU (2) OAM Tributary slots (4) Aggregate slots (2) Fan
ESD connector
The Table 4-2 provide the PEC for the OME6130 chassis.
Table 4-2
OME6130 chassis
Refer to Ordering information and system engineering rules on page 8-1 for
more information.
Slot numbers
Figure 4-3 shows the slot numbers for the OME6130 chassis.
Figure 4-3
OME6130 slot numbers
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-5
Figure 4-4
OME6130 DC power supply unit
PSU (2)
Fan module
The OME6130 chassis is equipped with a fan module that is located on the
right side of the chassis, as shown in Figure 4-2 on page 4-3. Four fans are
integrated within the module and are continuously being monitored for
failures.
The air filter is field replaceable and it can be ordered separately for sparing or
replacement.
ESD interface
The ESD interface is located below the fan module and is used to connect an
antistatic wrist strap required when handling circuit packs to avoid damage as
a result of electrostatic discharge. Figure 4-5 on page 4-6 shows the location
of the ESD interface below the fan module of the OME6130.
Figure 4-5
OME6130 fan module
ESD
Refer to Ordering information and system engineering rules on page 8-1 for
the PEC information. The fan module comes equipped with the chassis, but
can also be ordered separately for sparing.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-7
Figure 4-6
OAM circuit pack
Table 4-3
OAM port descriptions
Refer to Connector pinouts on page 7-5 for details on the connector pinouts for
the OAM ports.
The 2x155/622M aggregate circuit pack is the main circuit pack of the
OME6130 NE and it provides the following functionality:
The STM-1 ports of the 2x155/622M aggregate circuit pack can be equipped
with electrical SFP modules for intra office applications when the OME6130
NE is commissioned with STM-1 line rate.
The PEC for the 2x155/622M aggregate circuit pack is listed in Table 4-4.
Table 4-4
2x155/622M aggregate circuit pack
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-9
The PEC for the 2x155/622M aggregate circuit pack with Release 1.0 software
is listed in Table 4-5.
Table 4-5
2x155/622M aggregate circuit pack with Release 1.0 software
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-11
The PEC for the 8x10/100BT L1 circuit pack is listed in Table 4-7.
Table 4-7
8x10/100BT L1 circuit pack
8x10/100BT L1 NT6Q13AB
Figure 4-8
8x10/100BT L1 circuit pack
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-13
The 2xGE L1 circuit pack supports pluggable optical transceivers for the two
GE interfaces. The GE optical interfaces use small form-factor pluggable
(SFP) interfaces to deliver optical rate and reach flexibility on a per port basis.
The GE optical interfaces use SFP modules for short reach (SX) and
intermediate reach (LX) applications. Figure 4-9 shows the GE optical
interface ports on the 2xGE L1 circuit pack.
The PEC for the 2xGE L1 circuit pack is listed in Table 4-8.
Table 4-8
2xGE L1 circuit pack
2xGE L1 NT6Q20AA
Figure 4-9
2xGE L1 circuit pack
• the total bandwidth available for connections on the 2xGE L1 circuit pack
is 4 x STM-1 (622 Mb/s). The bandwidth is shared between the two GE
ports of the circuit pack
• supports provisionable Ethernet link integrity (Enabled or Disabled)
• supports provisionable Ethernet auto-negotiation (Enable or Disable) with
the local Ethernet link partner as per clause 37 of IEEE 802.3-2000
• supports full duplex mode
• 64 byte to 9600 byte Ethernet frame support
• supports provisionable Ethernet maximum transfer unit (MTU) between
64 and 9600 (default) bytes
• supports Ethernet flow control capabilities
— None (advertises flow control not supported)
— Both (advertises asymmetric or symmetric flow control toward the
local device)
— Asymmetric (default) (advertises asymmetric flow control toward the
link partner)
— Symmetric (advertises symmetric flow control toward the link partner)
Note: This attribute is ignored when auto-negotiation is disabled.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-15
The PEC for the 28xE1/DS1 circuit pack is listed in Table 4-9.
Table 4-9
28xE1/DS1 circuit pack
28xE1/DS1 NT6Q10AA
NT6Q10AB
Figure 4-10
28xE1/DS1 circuit pack faceplate
The PEC for the 3xE3/DS3 circuit pack is listed in Table 4-10.
Table 4-10
3xE3/DS3 circuit pack
3xE3/DS3 NT6Q12AA
Figure 4-11
3xE3/DS3 circuit pack faceplate
3XE3DS3
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-17
The 2x155M circuit pack supports pluggable optical and electrical transceivers
for the two STM-1 line interfaces. The STM-1 optical and electrical interfaces
use small form-factor pluggable (SFP) interfaces to deliver optical and
electrical rate and reach flexibility on a per port basis. The STM-1 optical
interfaces use SFP modules for short reach, intermediate reach and long reach,
and CWDM access applications. The STM-1 electrical interfaces use SFP
modules for intra office applications. Figure 4-7 shows the STM-1 interface
ports on the center of the 2x155M circuit pack.
The PEC for the 2x155M circuit pack is listed in Table 4-11.
Table 4-11
2x155M circuit pack
2x155M NT6Q17AA
Figure 4-12
2x155M circuit pack faceplate
Filler faceplate
The filler faceplate is required to cover the unused tributary slots 4, 5, 8 and 9.
The slot 7 will be used in a future release for the protection aggregate circuit
pack but in OME6130 Rel 1.0, the slot 7 must be equipped with a filler
faceplate. If no additional tributary circuit packs are required a filler faceplate
must be used to cover the empty slots to ensure proper airflow through the
chassis and to ensure EMI compliance. Figure 4-2 on page 4-3 displays the
chassis with a filler faceplate installed over the slot 7.
Refer to Ordering information and system engineering rules on page 8-1 for
the associated PEC. The filler faceplate must be ordered separately.
Note: The 75 ohm termination panel is labeled from 1-16 by default, but
includes an additional overlay label which can be installed by the user
when connecting the ports 17-28 of the 28xE1/DS1 circuit pack.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Hardware description 4-19
Cable routing
The cable routing brackets which are installed at either side of the OME6130
shelf allows for the management of the power cables, OAM cables, optical
fibers and the Ethernet/PDH/DSn service cables. The cable routing brackets
are placed over the mounting brackets during the installation of the OME6130
shelf. Figure 4-13 shows the mounting and cable routing brackets for
OME6130.
For more information on the installation of the cable routing brackets, refer to
Installation, Commissioning and Testing Procedures, 323-1855-201. The
cable routing brackets come as part of the OME6130 shelf assembly kit. Refer
to Ordering information and system engineering rules on page 8-1 for ordering
details of the OME6130 shelf assembly kit.
Figure 4-13
OME6130 mounting and cable routing brackets
The PEC for the OME6130 shelf assembly kit is listed in Table 4-12.
Table 4-12
OME6130 Shelf assembly kit
Refer to Ordering information and system engineering rules on page 8-1 for
ordering details of the OME6130 shelf assembly kit.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
5-1
This chapter provides an overview of the craft user interface available for the
Optical Multiservice Edge 6130 (OME6130) Release 1.0. Table 5-1 lists the
topics in this chapter.
Table 5-1
Topics in this chapter
Topic Page
Table 5-2
OME6130 local craft access terminal requirements
The local craft access terminal 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
• nodal security management
• 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 OME6130 Release 1.0.
For more information on the Local Craft Access Terminal and the supported
applications, refer to the Local Craft Access User Guide, 323-1855-195.
SNMP traps
The OME6130 supports autonomous forwarding of system events through
SNMP traps for consolidated alarm reporting. The SNMP traps are sent to an
SNMP manager, such as HP Open View, where they can be used to alert a
system operator.
For more information on how to provision the SNMP trap destinations, refer
to Provisioning and Protection Switching Procedures, 323-1855-310.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
6-1
OAM&P description 6-
Topic Page
SDH Configuration 6-2
System Line-up and Test (SLAT) 6-2
Network element management 6-3
Equipment management 6-3
Facility management 6-4
Loopbacks 6-6
Synchronization management 6-7
Connection management 6-13
Traffic protection 6-17
1+1 MSP traffic protection 6-18
SNCP Traffic Protection 6-20
Unprotected connections 6-21
Data communications 6-22
Alarm and event management 6-27
Performance monitoring 6-32
Security and administration 6-38
Topology adjacency 6-41
Backing up and restoring the network element database 6-42
SDH Configuration
Optical Multiservice Edge 6130 Release 1.0 is a platform that can be deployed
in a SDH environment.
Commissioning process
The commissioning process starts after completion of the installation of the
OME6130 chassis into a 19”, 21” or 23” rack, circuit packs in the aggregate
and tributary slots, service cables and optical fibers routed but not connected,
and power cables connected but power switched off.
The commissioning process can be broken down into the following phases:
• network element powering up
In this phase, the user verifies the network element equipment and the
power supply, and then powers up the shelf.
• network element commissioning
In this phase, the user logs in to the OME6130 network element by
connecting to the Craft port on the OAM circuit pack. The user uses the
SLAT WUI page to either restore a saved configuration onto the new
network element or manually enter the network element commissioning
data and DCN parameters.
The node capability is provisioned to either STM-1 or STM-4 during initial
commissioning from the Configure Node application. The two SFP
interfaces of the 2x155/622M aggregate circuit pack are operating at the
rate of the node capability value.
Note: You cannot change the node capability from STM-1 to STM-4 or
vice versa while in-service. To change the node capability of the network
element, you must first use the “Restore factory default” application to
delete all configuration, events, and PM data. Power cycle the network
element and then use the Configure Node page to enter the required
commissioning information and node capability or to restore from a saved
configuration.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-3
Testing process
The testing process occurs after the user has completed the powering up and
commissioning of the OME6130 network element. The testing process
consists of a system level test as follows:
• system testing
The user performs system testing after all the network elements for a
system are physically connected into a linear or ring configuration. In this
phase, the user sets up and verifies the system configuration, connects the
test equipment, establishes a loopback, provisions a traffic connection, and
performs a traffic continuity and performance test on the system.
Refer to Installation, Commissioning and Testing Procedures, 323-1855-201,
for detailed installation, commissioning, and system testing procedures.
Equipment management
In OME6130, equipment is a logical entity and is the software representation
of a circuit pack. The user provisioned data about a circuit pack is stored in the
corresponding equipment object and the equipment object is not deleted from
the node inventory list when a circuit pack is removed. The equipment entities
for the OME6130 platform are as follows:
• chassis
• 2x155/622M aggregate circuit pack
• 8x10/100BT L1 circuit pack
• 2xGE L1 circuit pack
• 28xE1/DS1 circuit pack
• 3xE3/DS3 circuit pack
• 2x155M circuit pack
• power supply unit
• OAM circuit pack
• fan module
• SFP modules
The OME6130 supports automatic detection of new circuit packs in the
tributary slots. After insertion of a circuit pack in a previously unprovisioned
tributary slot, the system autoprovisions the circuit pack with default values
and places the circuit pack in-service. The circuit packs are immediately
Before you can delete the equipment from the inventory, you must physically
remove the module from its slot.For more information, refer to Provisioning
and Protection Switching Procedures, 323-1855-310.
Facility management
A facility represents an equipment’s OAM&P capabilities that allows the user
to provision, inspect, and control that interface. For the OME6130, a facility
represents an optical, electrical or service interfaces, such as:
• STM-4 optical interfaces and STM-1 optical and electrical interfaces on
the 2x155/622M aggregate circuit pack
• STM-1 optical and electrical interfaces on the 2x155M circuit pack
• 10/100BT Ethernet interface ports on the 8x10/100BT L1 circuit pack
• Gigabit Ethernet optical interfaces on the 2xGE L1 circuit pack
• WAN ports associated to 10/100BT Ethernet and Gigabit Ethernet
interface ports
• E1/DS1 interface ports on the 28xE1/DS1 circuit pack
• E3/DS3 interface ports on the 3xE3/DS3 circuit pack
For a complete list of editable and retrievable facility parameters, refer to
Provisioning and Protection Switching Procedures, 323-1855-310.
Managing facilities
Facility provisioning is a nodal function that allows you to query and edit
facility attributes on a specific interface.
The user manages facilities from the corresponding application menu in the
Provisioning main menu:
• STM
• Ethernet
• WAN
• E1/E3/DS1/DS3
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-5
Loopbacks
The OME6130 supports loopbacks on STM-1/4, 10/100BT Ethernet, Gigabit
Ethernet, E1/DS1 and E3/DS3 ports:
• Facility - the received signal is looped back towards the transmitter port
immediately on entering the interface port. AIS is inserted in the signal
towards the cross-connect on the 2x155/622M aggregate circuit pack.
• Terminal - the signal is looped back towards the cross-connect on the
2x155/622M aggregate circuit pack just before reaching the interface
transmitter.
Figure 6-1 provides an overview of terminal and facility loopbacks.
Figure 6-1
Facility and terminal loopbacks
Tx Tx
STM-1/4
STM-1/OC-3 interface
optical ports
interface ports
E1/DS1 and E3/DS3 services
E1, DS1, E3, DS3 and GE services
Terminal loopback
10/100BT Rx
Ethernet
Ethernet
interface
services Tx
10/100BT
EthernetEthernet
interfaceservices
ports
Table 6-2 on page 6-6 summarizes the supported loopback types for the
different ports and the appropriate AIS alarm conditioning.
Table 6-2
Loopbacks and AIS alarm conditioning
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-7
Table 6-2
Loopbacks and AIS alarm conditioning
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.
Timing generation
Timing generation is the ability of the OME6130 to extract and use the
synchronization reference from any of the defined synchronization inputs. The
OME6130 generates shelf timing signals based on external, line or internal
(freerun or holdover) references. The OME6130 supports a timing generation
hierarchy for two timing references.
The OME6130 is capable of generating a 4.6 ppm quality clock internally. This
clock is the default synchronization reference. The OME6130 supports
synchronizing to a reference clock signal derived from the following sources
(provisioned by the user as defined by the network synchronization plan):
• internal timing
When the internal clock is provisioned as a timing reference, the network
element goes to internal freerun mode rather than holdover mode, when the
internal clock becomes the active timing reference. See Figure 6-2 on page
6-9 example (a).
• external timing
As shown in Figure 6-2 on page 6-9 example (b), from the external
synchronization input (ESI) port on the OAM circuit pack, the OME6130
supports external timing reference inputs. The supported BITS signals are
detailed in Table 6-3 on page 6-8 below:
Table 6-3
Supported BITS signals
In Out In Out
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-9
sources or lockouts), the OME6130 falls into holdover mode. In the holdover
mode, the internal clock operates at a fixed frequency according to the last
known frequency reference for a minimum of 24 hours followed by freerun
mode (internal stratum 3 [ST3]/G.813 Option 1 compliant 4.6ppm clock). See
Figure 6-2 on page 6-9 example (a).
Refer to Viewing and management on page 6-12 for information about the
Synchronization application in the Configuration main menu of the local
craft access terminal for the OME6130.
Figure 6-2
Flow of synchronization timing signals
Stratum 3/G.813
Option 1 or better
OME6110 faceplate
Port Port
Base chassis
Legend
Synchronization timing
Traffic flow
Timing distribution
Timing distribution is the ability of the OME6130 to provide a synchronization
reference to external devices. The OME6130 supports the following timing
distribution reference signals:
• CLKOUT and DATAOUT ports on the ESI port located on the faceplate of
the OAM circuit pack
• one or two STM-1/4 ports on the 2x155/622M aggregate circuit pack
• one or two STM-1 ports on the 2x155M circuit pack
The following items need to be considered when using the OME6130 as a
timing source.
• the signal format of the external timing source (E1 or 2.048 MHz for SDH)
• the connector type/impedance of the ESI port (120 ohm balanced or 75
ohm unbalanced)
• the reference sources to be used for timing distribution and the hierarchy
Synchronization operating modes
The OME6130 synchronization operating modes describe the state that the
synchronization hardware is operating in. These modes are not provisionable
by the user and consists of the following:
• freerun
• locked
• holdover
Freerun mode
In freerun mode, the system clock is not locked to a timing reference and runs
at its natural frequency. The synchronization hardware on the 2xSTM-1/4
aggregate circuit pack provides timing references quality as specified in
internal G.813 Option 1 (4.6 ppm). The OME6130 is in this mode if the user
has provisioned the shelf timing as internal or the holdover period has expired
in which case a warning condition is raised to advise the user.
Locked mode
In locked mode, the system clock is locked to a timing reference. The
OME6130 is in this mode when a timing reference is active and working
during trouble free operations.
Holdover mode
The synchronization hardware enters holdover mode automatically if the
target mode is locked but all timing references have become unavailable. The
system clock in the synchronization hardware holds within a certain frequency
range of the last locked-in timing reference in which case a warning condition
is raised to advise the user.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-11
A network element can select the best of the two timing signals provided by
the timing sources provisioned by the user. The selection is based on the
quality values carried in the SSMs if the quality mode is enabled, otherwise,
the selection is based on the priority level set by the user. As the timing passes
from one network element to the next, each network element sends SSMs. If
the quality of the timing changes, the SSMs inform the next network element
of the change.
If a timing reference is not to be used for synchronization, the SSM will
contain a do not use for synchronization (DNU) message. See Table 6-4 on
page 6-11 for an overview of SSM designations supported by OME6130 in
SDH mode.
Table 6-4
Synchronization status messages in SDH mode
The outgoing override can be used when a remote network element expects a
particular SSM value.
Synchronization protection
Synchronization protection deals with the protection of the timing references.
The OME6130 supports the protection of the timing reference used for timing
generation. The timing generation reference for the system is selected from the
pool of provisioned reference sources.
From the local craft access terminal, the Synchronization application in the
Configuration main menu displays the protection status of the provisioned
synchronization hierarchies for the network element. The application shows
the 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
For more information synchronization protection, refer to Provisioning and
Protection Switching Procedures, 323-1855-310.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-13
Connection management
In the OME6130 architecture, traffic is switched between interface ports on the
circuit packs through the cross-connect matrix located on the 2x155/622M
aggregate circuit pack.
All services (Ethernet, E1/DS1 and E3/DS3) are mapped to the appropriate VC
containers. The OME6130 uses Generic Framing Procedure (GFP) as its
standards based SDH mapping for Ethernet services.
Generic Framing Procedure
GFP is an ITU standard (G.7041) which describes a flexible mapping
technique for transparent transport of multiple protocols in SDH. GFP
provides an efficient mechanism for Ethernet data services to be transported
over an SDH network via efficiently mapping varying client signals into VC
containers with a virtual concatenation group (VCG). OME6130 supports:
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-15
Table 6-5
OME6130 service mapping
10/100BT Ethernet, Gigabit Ethernet and PDH services are mapped to SDH
containers and assigned as SDH level connections to STM-1/4 interfaces. The
traffic protection schemes supported by the STM-1/4 interfaces can therefore
be used to provide a protected Ethernet, E1/DS1 or E3/DS3 service without the
requirement of a redundant handoff from the subtending 10/100BT Ethernet,
Gigabit Ethernet, E1/DS1 or E3/DS3 equipment. See Traffic protection on
page 6-17 for more information.
Hair-pinning
The OME6130 provides the ability to provision hairpin connections for PDH
services.
• E1-to-E1
• DS1-to-DS1
• E3-to-E3
• DS3-to-DS3
Connection management application
OME6130 connection management is based on a nodal, port-to-port
connection management philosophy that takes protection schemes into
account to rearrange connections at the physical level to implement traffic
protection. See Traffic protection on page 6-17 for more details.
The Cross-connect application in the local craft access terminal allows the
user to perform the following:
• filter, and display nodal connections
• provision nodal connections from any E1/E3/DS1/DS3 interface port to
any available timeslot of an STM-1/4 interface or of another
E1/E3/DS1/DS3 interface port on the same OME6130 network element.
Each cross-connect can have a Circuit Identifier which allows the user to
label the cross-connect.
Note 1: The systems blocks any cross-connects that are illegal. For
example, if a low-order VC12 cross-connect is provisioned, the system
blocks cross-connects of the corresponding VC3/VC4.
• operate or release user-initiated switch commands on SNCP connections.
• delete a nodal connection (supports multiple deletes)
The WAN application in the local craft access terminal allows the user to
perform the following:
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-17
Traffic protection
Traffic protection is a mechanism to enhance the dependability of a transport
service. The OME6130 provides a variety of protection mechanisms which
can be deployed to tailor the resilience of the platform to that required by the
customer. The system monitors the traffic facilities for performance
degradation and failure and performs protection switching when these
conditions are present. The following traffic protection configurations are
currently available:
Table 6-6
Traffic protection summary
The working and protection ports of the 1+1 MSP traffic protection group must
be provisioned on the same slot (i.e. slot 6 ports 1 and 2) for the STM-1/4
interfaces of the 2x155/622M aggregate circuit pack.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-19
The working and protection ports of the 1+1 MSP traffic protection groups can
be provisioned on the same slot or on different slots for the STM-1 interfaces
of the 2x155M tributary circuit packs.
The user provisions the Route Diversity for the 1+1 MSP traffic protection
group. The route diversity can be set to enable or disable for the STM-1/4 of
the 2x155/622M aggregate circuit pack. By default, the route diversity is set to
enable. The route diversity must be set to enable for the STM-1 of the 2x155
tributary circuit pack.
For detailed procedures for 1+1 MSP protection, refer to Provisioning and
Protection Switching Procedures, 323-1855-310.
The working and protection paths of the SNCP connections can be provisioned
on the same slot or on different slots for the STM-1/4 interfaces of the
2x155/622M aggregate and 2x155M tributary circuit packs. The timeslots for
the working and protection paths of the SNCP connections can be different.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-21
Forced switch 2
Wait-to-Restore 8 (lowest)
Unprotected connections
Unprotected configurations consists of end-to-end paths that do not have an
alternate path. In the case of the a fault on the unprotected path, traffic is lost.
Data communications
The OME6130 supports data communication features to provide the
capabilities for local and remote management of the OME6130 network
element and for interworking with other network elements to provide a
cohesive network management solution. The OME6130 OAM interfaces
provided are as follows:
• STM-1/4 interfaces using RS DCC (D1-D3 bytes), RS F1 byte, MS DCC
(D4-D12 bytes), or HO Path (F2, F3 and F2-F3 bytes) for OAM&P access
to remote network elements
• LAN port for interface to a data communications network (DCN).
• Craft port for interface to a local craft terminal PC.
• M1/F1 port for modem access or for user byte access
• Management channel via physical E1 port
• Management channel via VC12 payload
Interfaces
The interfaces/protocols are configured from various applications available
from the local craft access terminal. For DCN provisioning procedures, see
Provisioning and Protection Switching Procedures, 323-1855-310.
LAN interface
The LAN interface provides a mechanism to connect the OME6130 network
element to the office DCN for connectivity to a management system for remote
management of the OME6130 network and subtending network elements.The
LAN interface consists of a 10/100Base-T RJ-45 port located on the front of
the OAM circuit pack.
The LAN port can be enabled or disabled with the default being enabled.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-23
Proxy ARP is supported on the LAN interface when the OME6130 NE is used
as a gateway NE. The gateway OME6130 NE responds to ARP requests for
the subtending NEs when Proxy ARP is enabled. The subtending NEs need to
be added as Proxy ARP neighbours at the gateway OME6130 NE.
The LAN interface can be configured from the Network interface application
available from the Configuration/DCN menu item in the local craft access
terminal. For a detailed procedures, see Provisioning and Protection Switching
Procedures, 323-1855-310. To know how to provision the IP address for the
LAN port, refer to Installation, Commissioning and Testing Procedures,
323-1855-201.
Craft interface
The Craft interface provides a mechanism to connect a local craft terminal PC
directly to the OME6130 network element for local access to the OME6130
network and subtending network elements.The Craft interface consists of a
10/100Base-T RJ-45 port located on the front of the OAM circuit pack.
The Craft port can be enabled or disabled with the default being enabled.
The Craft interface can be configured from the Network interface application
available from the Configuration/DCN menu item in the local craft access
terminal. For a detailed procedures, see Provisioning and Protection Switching
Procedures, 323-1855-310. To know how to provision the IP address for the
Craft port, refer to Installation, Commissioning and Testing Procedures,
323-1855-201.
M1/F1 interface
The M1/F1 interface provides a mechanism to connect a PC or a modem to the
OME6130 network element for user byte clear channel access or remote
management. The RS-232 serial port is exposed as a RJ-45 connector located
on the front of the OAM circuit pack.
Note: Only the first E1 port of the 28xE1/DS1 circuit pack can be used for
the E1 management channel.
The generic routing encapsulation (GRE) protocol is used for OSI based DCC
interfaces. The GRE tunnels can be provisioned statically or dynamically
(auto-GRE tunneling).
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-25
DCC Transparency
The OME6130 supports DCC transparency via overhead tunnel provisioning.
This feature allows two STM-1/4 interfaces to be connected together so the
network element appears transparent to subtending network elements (NEs
connected to the OME6130 via the STM-1/4 interfaces).
The user can select the bytes on which the overhead tunnel should be passing
through. The available values are:
• E1
• E2
• F1
• DCC_R
• DCC_M
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-27
For more information about the local alarm indications, refer to Trouble
Clearing and Module Replacement Procedures, 323-1855-543.
For more information about the alarm banner, refer to Local Craft Access User
Guide, 323-1855-195.
For more information about the active alarm and alarm clearing procedures,
refer to Local Craft Access User Guide, 323-1855-195 and Trouble Clearing
and Module Replacement Procedures, 323-1855-543.
Viewing/provisioning alarm filters
The Alarm Filters application in the Faults menu of the local craft access
terminal provides the ability for users to create alarm filter rules whereby
selected alarms on chosen entities are not displayed in the active alarm list. The
application gives the user the ability to view, add or delete an alarm filter rule.
An alarm filter rule can be created for an object type against only one object
instance, where a selected alarm or all alarms are filtered out. When an alarm
filter is created, any active alarm which matches the filter rule are no longer
displayed in the active alarm list, and the filtered alarm is displayed in the
suppressed alarm list. An alarm filter can be deleted at any time.
For more information about the alarm filter and detailed procedures on
managing alarm filters, refer to Local Craft Access User Guide, 323-1855-195
and Trouble Clearing and Module Replacement Procedures, 323-1855-543.
Viewing suppressed alarms
The Suppressed alarms application in the Faults menu of the WUI allows the
user to view any alarms that have been suppressed by the Alarm Filter or by
the Alarm Reporting Control feature.
For more information about the suppressed alarms and alarm clearing
procedures, refer to Local Craft Access User Guide, 323-1855-195 and
Trouble Clearing and Module Replacement Procedures, 323-1855-543.
Viewing event history
The user views the events on an OME6130 shelf by selecting the Event
history application in the Faults menu of local craft access terminal. The
Events history application supports the viewing of historical (current and
cleared) alarms and events for the OME6130 network element.
For more information about the event history and alarm clearing procedures,
refer to Local Craft Access User Guide, 323-1855-195 and Trouble Clearing
and Module Replacement Procedures, 323-1855-543.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-29
For more information about the alarm severities and detailed procedures on
managing alarm severities, refer to Local Craft Access User Guide,
323-1855-195 and Trouble Clearing and Module Replacement Procedures,
323-1855-543.
The path alarm profile specifies the consequent actions upon TIM, PLM and
UNEQ conditions. The path alarm profile also specifies the path level alarms
that should be masked. The eight default path alarm profiles can not be deleted
and their defined actions can not be modified, while the user can create or
delete the user defined path profiles and edit the defined actions.
Once a connection is created with the path alarm profile assigned according to
the STM Port Profile, the path alarm profile can be manually changed at the
AU/TU levels.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-31
The OME6130 also supports the capability of displaying the network element
summary alarms onto an external device. The Critical, Major, and Minor
alarms can be reported to an external control device by connecting to the
ALM.OUT RJ-45 connector on the front of the OAM circuit pack.
Table 6-10 on page 6-31 summarizes the PDH/DSn alarms for the different
circuit packs.
Card type Line alarm Path alarm (near-end) Path alarm (far-end)
Note 1: The underlined path alarms have limited monitoring support and the non-underlined path
alarms have full monitoring support
Note 2: All line and path alarms have full monitoring support
Performance monitoring
Performance monitoring (PM) refers to the continuous collection, analysis,
and reporting of the performance data of a monitored entity. This monitoring
allows early detection of service degradations and facilitates preventive
maintenance without interruption of service. PMs can also be used to facilitate
trouble/fault isolation.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-33
STM PM parameters
STM PM parameters are accumulated for the STM-1/4 interfaces on the circuit
packs. Table 6-11 provides a summary of the supported STM PM parameters.
Table 6-11
SDH PM parameters summary
Facility PM parameter
Regenerator SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI
Section (RS)
Multiplex section SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI, ES-FE,
(MS) SES-FE, BBE-FE, UAS-FE, SEP-FE
Path (HO AU) SDH: ES, SES, UAS, SEP, EB, BBE, PPJE, NPJE, ESR, SESR, BBER, SEPI,
ES-FE, SES-FE, BBE-FE, UAS-FE, SEP-FE
Tributary Unit (LO SDH: ES, SES, UAS, SEP, EB, BBE, ESR, SESR, BBER, SEPI, ES-FE,
TU) SES-FE, BBE-FE, UAS-FE, SEP-FE
Tranceiver Received Power, Transmit Power, Laser Bias, Laser Voltage, Laser
(physical) Temperature
Path performance parameters are monitored when the path monitoring mode
for the selected framed port is set to Alarm and Performance Monitoring. Path
performance parameters are also counted for unframed E1/DS1 ports only
based on AIS condition.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-35
Table 6-13
10/100BT Ethernet and Gigabit Ethernet PM parameters summary
Facility PM parameter
Facility PM parameter
Gigabit Ethernet • ES
• Ethernet Interval Valid
• Frame Too Long Errors
• Frame Too Short Errors
• FCS Error Bytes
• FCS Error Frames
• Frames Dropped Rx
• Frames Dropped Tx
• Frames Received
• Frames Transmitted
• Idle Seconds
• Octets Received
• Octets Transmitted
• Pause Frames Received
• Pause Frames Transmitted
• SES
• UAS
WAN PM parameters
WAN PM parameters are accumulated for the 10/100BT Ethernet interfaces on
the 8x10/100BT L1 circuit pack and the Gigabit Ethernet interfaces on the
2xGE L1 circuit pack. Table 6-14 provides a summary of the supported VCG
PM parameters.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-37
Table 6-14
WAN PM parameters summary
Facility PM parameter
PM time intervals
For PM parameters, the following PM counts are stored and can be retrieved:
• current 15-minute interval
• last 32 15-minute intervals
• current day
• previous day
PM enable/disable
The 15-minutes and 1-Day Threshold Cross Alerts for the STM-1/4/PDH/DSn
facilities are disabled by default. The system does not generate TCAs if the
port/facility is in the admin down state.
PM inhibition
The system inhibits the collection of PMs when the associated facility is in the
the admin down state and for some parameters during various trouble
conditions.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-39
Security levels
OME6130 network elements support multiple security access levels. This
feature reduces accidental or intrusive interruption of service. As defined in,
there are 3 user access classes that allow a range of task execution capabilities.
Table 6-15
User access classes for OME6130
The OME6130 has a default ADMIN level account named ADMIN with
ADMIN password. Nortel Networks recommends that the default passwords
be changed. See “Local password management” on page 6-40 for more
information.
There is no restriction on the number of user account per user access class, as
long as the total number of local user accounts does not exceed nine (9).
Login sessions
To manage an OME6130 network element and issue commands, the user must
be logged in on that node which creates a login session. The maximum number
of login sessions to a network element is ten.
Multiple login sessions
Several user accounts can be active at the same time as long as the maximum
number of ten login sessions is not exceeded. When several sessions are active,
commands can be sent to the network element simultaneously from each active
session.
Table 6-16
User ID and password details
User ID • is unique
• can be alphabetic/numeric/alphanumeric
• supports special characters except space
• supports up to 32 characters
• is case sensitive
Password • is unique
• must be exactly eight characters long
• can be alphabetic/numeric/alphanumeric
• supports special characters except space
• is case sensitive
• and the user ID cannot be identical
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
OAM&P description 6-41
Note: When managing the OME6130 network element using OMEA, the
first two NTP servers will automatically be provisioned by the OMEA
server. If additional time servers are desired, these should be provisioned
against other than the first two sources.
The user can provision TOD synchronization from the Set time server
application in the System Time menu of the local craft access terminal.
Topology adjacency
The topology adjacency feature on the OME6130 is used by the network
management to build the network topology for end-to-end connection
management. The network topology is built based on the neighbour status
information, which can be manually provisioned by the user or set to be
automatically discovered upon establishing connectivity to neighbour nodes.
The user manages database backups from the Backup configuration and
Restore configuration applications in the Maintenance/Configuration
Management menu of the local craft access terminal. The applications allow
the user to manage backup copies of the network element database for each
network element within a network and restore the network element database to
an operational state following a system initialization.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
7-1
Technical specifications 7-
This chapter provides technical specifications, as listed in Table 7-1, for the
Optical Multiservice Edge 6130 (OME6130) network element.
Table 7-1
Topics in this chapter
Topic Page
Physical specifications
Table 7-2 lists the following physical specifications for OME6130 network
elements.
Table 7-2
Physical specifications for OME6130 platform
Circuit packs
OME6130 chassis
Width 445.0 mm / 17.5 in. • Figure 7-1 on page 7-3 for an overview
of the OME6130 chassis
Depth 231.0 mm / 9.1 in. (shelf only) • OME6130 network element
295.0 mm / 11.6 in. (including configuration rules on page 8-2 for
cable routing brackets) more information about physical
specifications
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-3
Figure 7-1
OME6130 chassis - physical specifications
PSU (2) OAM Tributary slots (4) Aggregate slots (2) Fan
Power specifications
The OME6130 equipped with the DC PSU operates from -40 V dc to -57.5 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-3 lists the estimated power requirement for the common
equipment at -54 V dc
• Table 7-4 lists the estimated power requirement for each interface circuit
pack -54 V dc
• Table 7-5 lists the estimated power requirement for each small form-factor
pluggable (SFP) module at -54 V dc
• Table 7-6 lists the recommended feeders for the chassis
Table 7-3
Power consumption for common equipment at -54 V dc
Fan module 13
Chassis 0
Table 7-4
Power consumption for each circuit pack at -54 V dc
Table 7-5
Power consumption for each SFP at -54 V dc
Table 7-6
Recommended feeders
Refer to Table 8-20 on page 8-18 for a list of power cables assemblies available
and the Installation, Commissioning and Testing Procedures, 323-1855-201
for details on installing and connecting power to an OME6130 shelf.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-5
Connector pinouts
Table 7-7 lists the connectors and the respective tables providing the details of
their pin assignments and front views.
Table 7-7
Connector pin assignment details
Connector Details
DC power connector
Table 7-8
DC power connector - pin assignment (in NT6Q59CA, NT6Q59DA, NT6Q59PA
and NT6Q59QA)
Pin Connector
1 RET
2 GND
3 -48V
Pin Description
1 ALARMIN_1
2 ALARMIN_7
3 ALARMIN_6
1 2 3 4 5 6 7 8 4 ALARMIN_5
5 ALARMIN_4
6 ALARMIN_3
7 ALARMIN_2
8 COMMON
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-7
1 ALARMOUT_4_RET Unused
2 ALARMOUT_4
3 ALARMOUT_3_RET Minor
1 2 3 4 5 6 7 8 4 ALARMOUT_3
5 ALARMOUT_2_RET Major
6 ALARMOUT_2
7 ALARMOUT_1_RET Critical
8 ALARMOUT_1
M1/F1 connector
Table 7-11
M1/F1 connector - pin assignment (NT6Q71AG/NT6Q71AF)
1 DSR
2 CD
3 DTR
1 2 3 4 5 6 7 8 4 GND GND
5 RD RD
6 TD TD
7 CTS
8 RTS
ESI connector
Table 7-12
ESI connector - pin assignment (NT6Q71AC/NT6Q71AE)
Pin Signal
1 CLKIN+
2 CLKIN-
3 DATAIN+
1 2 3 4 5 6 7 8 4 CLKOUT-
5 CLKOUT+
6 DATAIN-
7 DATAOUT+
8 DATAOUT-
Note 1: BITS-1-2-1 (IN) uses pins 1 & 2 and BITS-1-2-2 (IN) uses pins 3 & 6
Note 2: BITS-1-2-1 (OUT) uses pins 4 & 5 and BITS-1-2-2 (OUT) uses pins 7 & 8
Pin Signal
1 RX+
2 RX-
3 TX+
6 TX-
Note: The Ethernet cables connecting to the 10/100BT ports on the 8x10/100BT L1
circuit pack must be shielded twisted pair. Refer to Ethernet service cable
assemblies on page 8-14 for ordering information.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-9
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-11
Note: Right routing E1 cables connecting to the 28xE1/DS1 circuit pack must have a shielded
connector. Refer to Table 7-21 on page 7-21 for details on the shielded connector specifications.
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
(WH/BR) (WH/BR)
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-13
Note: Right routing DS1 cables connecting to the 28xE1/DS1 circuit pack must have a shielded
connector. Refer to Table 7-21 on page 7-21 for details on the shielded connector specifications.
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
25 NC 57 NC P25
26 NC 58 NC P26
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-15
27 NC 59 NC P27
28 NC 60 NC P28
29 NC 61 NC P29
30 NC 62 NC P30
31 NC 63 NC P31
32 NC 64 NC P32
Note: Right routing E1 cables connecting to the 28xE1/DS1 circuit pack must have a shielded
connector. Refer to Table 7-21 on page 7-21 for details on the shielded connector specifications.
32 31 30 29 28 27 26 25 24 23 22 21 20 19 18 17 16 15 14 13 12 11 10 9 8 7 6 5 4 3 2 1
(WH/BR) (WH/BR)
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-17
25 NC 57 NC P25
26 NC 58 NC P26
27 NC 59 NC P27
28 NC 60 NC P28
29 NC 61 NC P29
30 NC 62 NC P30
31 NC 63 NC P31
32 NC 64 NC P32
Note: Right routing DS1 cables connecting to the 28xE1/DS1 circuit pack must have a shielded
connector. Refer to Table 7-21 on page 7-21 for details on the shielded connector specifications.
The following sections detail the pinouts and port mappings for the 120/100
ohm cable assemblies and for the 75 ohm termination panel. The E1/DS1
cables come with right routing.
These cable assemblies can be ordered from Nortel (see E1/DS1 cable
assemblies on page 8-12) or produced locally to the specifications provided:
• Table 7-14 on page 7-10 provides the 120 ohm cable connector pin
assignment, which applies for E1 services on the first connector on the
28xE1/DS1 circuit pack.
• Table 7-15 on page 7-12 provides the 100 ohm cable connector pin
assignment, which applies for DS1 services on the first connector on the
28xE1/DS1 circuit pack.
• Table 7-16 on page 7-14 provides the 120 ohm E1 cable connector pin
assignment for the second connector on the 28xE1/DS1 circuit pack.
• Table 7-17 on page 7-16 provides the 100 ohm DS1 cable connector pin
assignment for the second connector on the 28xE1/DS1 circuit pack.
• Figure 7-3 on page 7-19 shows the 75 ohm BNC termination panel for 16
channels. Using the termination panel, the 120 ohm balanced E1 services
can be converted to 75 ohm unbalanced.
• Table 7-18 on page 7-19 lists the physical specifications for the 75 ohm
BNC termination panel
• Table 7-19 on page 7-20 lists the cable specifications for connecting the E1
ports of the 28xE1/DS1 circuit pack.
• Table 7-20 on page 7-21 lists the cable specifications for connecting the
DS1 ports of the 28xE1/DS1 circuit pack.
• Table 7-21 on page 7-21 lists the connector specifications for the shield
connector required for the right routing E1 and DS1 cables for use with the
28xE1/DS1 circuit pack.
• Figure 7-4 on page 7-22 shows the 120 ohm twisted pair E1 cable bundle.
• Figure 7-5 on page 7-23 shows the 64-pin 100 degree right routing cable
connector.
Note: The color codes and pinout provided apply to the suggested E1/DS1
cables. Color codes and pinout may vary by manufacturer.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-19
Figure 7-3
75 ohm termination panel - 16 channel
Note: The 75 ohm termination panel is labeled from 1-16 by default, but
includes an additional overlay label which can be installed by the user
when connecting the ports 17-28 of the 28xE1/DS1 circuit pack.
Table 7-18
Physical specifications for 75 ohm BNC termination panel
120 ohm connector 64-pin Telco See Table 7-14 on page 7-10 for pinout
(for interconnection with information on 64-pin connector.
OME6130 shelf)
Table 7-19 lists the E1 cable specifications and Table 7-20 lists the DS1 cable
specifications for connecting E1 and DS1 ports respectively, on the
28xE1/DS1 circuit pack.
Table 7-19
Cable specifications for connecting E1 ports
Pairs Two conductors twisted into pairs with varying lay length
Jacket Four pair groups are jacketed with PVC and each group is numbered
Shield Overall Aluminum/Mylar foil shield with aluminum side facing out. 26
AWG tinned copper drain wire over the foil with a 34 AWG tin plated
copper braid, 65% coverage.
Electrical Characteristics
Dielectric Strength
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-21
Table 7-20
Cable specifications for connecting DS1 ports
Pairs Two conductors twisted into pairs with varying lay length
Colour Code Refer to Table 7-15 on page 7-12 for colour coding information
Shield 24 AWG tinned copper drain wire over the foil with a 34 AWG tin plated
copper braid, 65% coverage.
Electrical Characteristics
Dielectric Strength
For applications with the 28xE1/DS1 circuit pack, right routing E1 or DS1
cables must be used. The cable connectors for the right routing cables must
comply to the specifications provided in Table 7-21. Refer to Figure 7-5 on
page 7-23 for more details.
Table 7-21
Connector specifications for right routing E1/DS1 cables
Connector
Connector type 64 POS Male AMP Champ (0.085) or equivalent ‘key telephone’
connector
Hood
Depth 60 mm maximum connector hood and cable depth from connector mating
face
Component Metal plated plastic (100% coverage) or fully metal shielded connector
hood
Terminations Shielded hood terminated to cable shield and to both hood mounting
screws via the cable drain wires (both mounting screws must attach to
the drain wire through Y’d arrangement, or two drain wires) and
interference contact to exposed braid at the exit of the cable from hood.
Figure 7-4
E1 coaxial cable bundle specification
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-23
Figure 7-5
64-pin E1/DS1 100 degree right routing cable connector
Optical specifications
The following sections provide details of the optical specifications. All the
optical SFPs for the OME6130 are equipped with LC type connectors.
The following assumptions were made when calculating the dispersion and
attenuation limited distances quoted in the optical specifications:
• NSDF fiber plant is being used
• dispersion and attenuation coefficient are as listed in Table 7-22.
Table 7-22
Optical specifications - assumed dispersion and attenuation coefficient
Wavelength
ATTENTION
The dispersion and attenuation limited distances quoted in the optical
specifications are based on the dispersion and attenuation coefficients
detailed in Table 7-22 and are for guidance only and must be verified by a full
link budget calculation. The actual limiting distance is the lower of the
dispersion limited or attenuation limited distances.
Transmitter
Transmit output power (min) -20 dBm -15 dBm -5 dBm -5 dBm
Receiver
Receiver type PIN photodiode APD APD APD
Receiver sensitivity -30 dBm -28 dBm -34 dBm -34 dBm
Path penalty - 1 dB 1 dB 1 dB
Optical path
Attenuation range 0 dB 0 dB to 12 dB 10 dB to 28 dB 10 dB to
to 10 dB 28 dB
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-25
Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-10
when used over G.652 specified SMF-28 fiber. The exception is SR0 where the values are for use over
62.5 μm core, 500 MHz-km modal bandwidth MMF as specified in ANSI T1.416.01-1999.
Note 2: Power monitor accuracy figures are for normal operating range (minimum to maximum transmit
power, receiver sensitivity to overload).
Note 3: Nominal reach figures are for classification purposes only as defined in the appropriate
standards.
Note 4: The dispersion and attenuation limited distances are based on the dispersion and attenuation
coefficients detailed in Table 7-22 on page 7-23 and are for guidance only and must be verified by a full
link budget calculation. The actual limiting distance is the lower of the dispersion limited or attenuation
limited distances.
Table 7-24 lists the optical specifications for the STM-4 optical SFPs.
Table 7-24
Optical specifications for STM-4 SFPs
Classification L4.1 L4.2
PEC NTTP05EF NTTP05FF
Transmitter
Transmitter type DFB laser DFB laser
Nominal wavelength 1310 nm 1550 nm
Transmit output power (max) +2 dBm +2 dBm
Transmit output power (min) -3 dBm -3 dBm
Spectral width 1 nm (-20 dB) 1 nm (-20 dB)
Minimum side mode suppression ratio 30 dB 30 dB
Minimum extinction ratio 10 dB 10 dB
Power monitor accuracy (see Note 2) +/- 2 dB +/- 2 dB
Receiver
Receiver type APD APD
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-27
Table 7-25 lists the optical specifications for the STM-1/4 optical SFP.
Table 7-25
Optical specifications for STM-1/4 SFPs
Classification IR1/S1.1_S4.1
PEC NTTP04CF
Transmitter
Receiver
Path penalty 1 dB
Optical path
Attenuation range 0 dB to 12 dB
Classification IR1/S1.1_S4.1
Note 1: All parameter values in the above table achieve an optical system BER
better than 1x10-10 when used over G.652 specified SMF-28 fiber.
Note 2: Power monitor accuracy figures are for normal operating range (minimum
to maximum transmit power, receiver sensitivity to overload).
Note 3: Nominal reach figures are for classification purposes only as defined in the
appropriate standards.
Note 4: The dispersion and attenuation limited distances are based on the
dispersion and attenuation coefficients detailed in Table 7-22 on page 7-23 and are
for guidance only and must be verified by a full link budget calculation. The actual
limiting distance is the lower of the dispersion limited or attenuation limited
distances.
Table 7-26 lists the optical specifications for the STM-1/4 CWDM optical
SFPs.
Table 7-26
Optical specifications for STM-1/4/16 SFPs
PEC NTK590xH
(see Note 6)
Transmitter
Receiver
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-29
Optical path
Note 1: All parameter values in the table achieve an optical system BER better than
1x10-10 when used over G.652 specified SMF-28 fiber except for the CWDM value
which is for an optical system BER better than 1x10-12.
Note 2: Power monitor accuracy figures are for normal operating range (minimum
to maximum transmit power, receiver sensitivity to overload).
Note 3: Nominal reach figures are for classification purposes only as defined in the
appropriate standards.
Note 4: CWDM reach is consistent with Appendix II of ITU-T G.695 (refer to G.695
Table II.2 for parameter values and G.695 Table II.1 for attenuation values).
Dispersion limits are based on 21.1 ps/nm-km.
Note 5: The dispersion and attenuation limited distances are based on the
dispersion and attenuation coefficients detailed in Table 7-22 on page 7-23 and are
for guidance only and must be verified by a full link budget calculation. The actual
limiting distance is the lower of the dispersion limited or attenuation limited
distances.
Note 6: Refer to Ordering information and system engineering rules on page 8-1 for
a list of supported wavelengths and PECs.
Table 7-27 lists the optical specifications for the STM-1 (100Base)
Bidirectional SFPs.
Table 7-27
Optical specifications for STM-1 (100Base) Bidirectional SFPs
Classification 100Base 100Base
BX10-U BX10-D
(see Note 3) (see Note 3)
PEC NTTP09BD NTTP10BD
Transmitter
Transmitter type FP laser FP laser
Nominal wavelength 1310 nm 1530 nm
Transmit output power (max) -8 dBm -8 dBm
Transmit output power (min) -14 dBm -14 dBm
Spectral width 7.7 nm (RMS) 4.4 nm (RMS)
Minimum extinction ratio 6.6 dB 6.6 dB
Receiver
Receiver type PIN photodiode PIN photodiode
Wavelength range 1480 nm to 1260 nm to
1580 nm 1360 nm
Nominal wavelength 1530 nm 1310 nm
Receiver sensitivity -28.2 dBm -28.2 dBm
Receiver overload - 8 dBm - 8 dBm
Path penalty 4.5 dB 4.5 dB
Maximum receive reflectance -12 dB -12 dB
Optical path
Reach 10 km 10 km
(see Note 2) (see Note 2)
Note 1: All parameter values in the above table achieve an optical system BER better than 1x10-12.
Note 2: 0.5 m to 10 km over G.652 SMF.
Note 3: Used for a bidirectional link over a single fiber with an upstream SFP fitted at one end of the
link and an downstream SFP fitted at the other end of the link. The upstream SFP transmits at 1310 nm
and receives at 1530 nm, the downstream SFP transmits at 1530 nm and receives at 1310 nm.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-31
Table 7-28 lists the optical specifications for the GE optical SFPs.
Table 7-28
Optical specifications for GE SFPs
Classification SX (see Note 2) LX
PEC NTTP01AF NTTP01CF
Transmitter
Transmitter type VCSEL FP laser
Nominal Wavelength 850 nm 1310 nm
Transmit output power (max) <0 dBm (see Note 3) -3 dBm
Transmit output power (min) -9.5 dBm -9.5 dBm
Spectral width 0.85 nm (RMS) 4 nm (RMS)
Minimum side mode suppression ratio - -
Minimum extinction ratio 9 dB 9 dB
Receiver
Receiver type PIN photodiode PIN photodiode
Wavelength range 770 nm to 860 nm 1270 nm to 1355 nm
Nominal wavelength 850 nm 1310 nm
Receiver sensitivity -17 dBm -20 dBm
Receiver overload 0 dBm -3 dBm
Path penalty - -
Maximum receive reflectance -12 dB -12 dB
Optical path
Attenuation range - -
Nominal reach (see Note 4) 2 m to 550 m 10 km
(see Note 5) (see Note 6)
Maximum dispersion - -
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-33
Electrical specifications
Table 7-29 to Table 7-33 lists the electrical specifications for the E1, E3, DS3,
DS1, and STM-1e interfaces.
Table 7-29
E1 electrical specifications
Parameter Value
Line rate 2048 kbit/s +/- 50 ppm
Line code HDB3
Framing application CRC4
Impedance 75 ohm or 120 ohm (see Note)
Output voltage (nominal) 75 ohm: 2.37 V (mark), 0 ± 0.237 V (space)
120 ohm: 3.00 V (mark), 0 ± 0.300 V (space)
Minimum output return loss 6 dB (51 kHz to 102 kHz), 8 dB (102 kHz to 3072 kHz)
Cable loss to input 0 dB to 6 dB at 1024 kHz
Minimum input return loss 12 dB (51 kHz to 102 kHz), 18 dB (102 kHz to
2048 kHz), 14 dB (2048 kHz to 3072 kHz)
Note: A termination panel must be used for 75 ohm E1 applications.
Table 7-30
E3 electrical specifications
Parameter Value
Line rate 34368 kbit/s +/- 20 ppm
Line code HDB3
Framing application G.832
Impedance 75 ohm
Output voltage (nominal) 75 ohm: 1.0 V (mark), 0 ± 0.1 V (space)
Cable loss to input 0 dB to 12 dB at 17184 kHz
Minimum input return loss 12 dB (860 kHz to 1720 kHz), 18 dB (1720 kHz to
34368 kHz), 14 dB (34368 kHz to 51550 kHz)
Table 7-31
DS1 electrical specifications
Parameter Value
Line rate 1544 kbit/s +/- 50 ppm
Line code B8ZS
Framing application Extended Super Frame (ESF)
Impedance 100 ohm ± 5%
Table 7-32
DS3 electrical specifications
Parameter Value
Line rate 44736 kbit/s +/- 20 ppm
Line code B3ZS
Framing application ASYNC
Impedance 75 ohm ± 5%, unbalanced
Pulse amplitude 0.36 V to 0.85 V peak
Power level -4.7 dBm to +3.6 dBm
Cable distances Maximum 450 ft (137.1 m)
Line build-out (LBO) Using 735A cables (recommended) (NTTC03xx):
ranges 0 to 255 ft (77.7 m), 255 ft (77.7 m) to 450 ft (137.1 m)
Table 7-33
STM-1e electrical specifications
Parameter Value
Line rate 155520 kbit/s +/- 20 ppm
Line code CMI
Impedance 75 ohm
Peak output voltage 1.00 V ± 0.1 V
Minimum output return loss 15 dB (8 MHz to 240 MHz)
Cable loss to input 0 dB to 12.7 dB at 78 MHz
Minimum input return loss 15 dB (8 MHz to 240 MHz)
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-35
Environmental specifications
The following section outlines the environmental specifications including:
• operating environment specifications
• storage and transportation specifications
Operating environment specifications
Table 7-34 outlines the OME6130 operating environment specifications.
Table 7-34
Operating environmental specifications for OME6130 system
Operational vibration 0.1 g from 5 to 100 Hz and • Telcordia GR-63 CORE (NEBS)
return to 5 Hz at a rate of 0.1
octave/minute
Electromagnetic specifications
Table 7-35 lists the electromagnetic compatibility of the OME6130 network
element.
Table 7-35
Electromagnetic specifications for OME6130
Direct and indirect Direct and indirect ESD • EN 300 386 V1.3.3
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+A1:2001+A2:2003
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-37
Electrical fast transient (EFT) power and signal cables • EN 300 386 V1.3.3
4 kV - ground • Telcordia GR-1089-CORE, Iss.3
1 kV - power • EN 55024:1998+A1:2001+A2:2003
0.5 kV - signal
Safety specifications
The following section outlines the safety specifications, including:
• general commercial and regulatory
• laser emissions
General commercial and regulatory
The OME6130 complies with the safety requirements of the following
specifications:
• IEC/EN 60950-1:2001+A11:2004
• Telcordia GR-1089-CORE, Iss.3
Laser emission
The OME6130 meets the requirements of the following specifications:
• IEC/EN 60825-1:1994+A11:1996+A2:2001+A1:2002
• IEC/EN 60825-2:2004
• FDA 21 CFR 1040.10
The OME6130 is a class 1 laser product/optical fiber communications system.
Topic References
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical specifications 7-39
Topic References
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
8-1
This chapter provides the ordering information and engineering rules for the
Optical Multiservice Edge 6130 (OME6130) network element. Table 8-1 lists
the topics in this chapter.
Table 8-1
Topics in this chapter
Topic Page
List of parts
Topic Page
Ordering procedures
Chassis layout
Table 8-2 lists the circuit packs or components that can be inserted into the
OME6130 chassis and the corresponding slot numbers. Figure 8-1 shows the
OME6130 chassis layout.
Table 8-2
Chassis components
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-3
Figure 8-1
OME6130 chassis layout
For more information on the OME6130 chassis, refer to Chassis on page 4-3.
Engineering rules
1 Each shelf at an OME6130 site is a stand-alone network element.
2 The node capability is provisioned to either STM-1 or STM-4 during initial
commissioning. The two SFP interfaces of the 2x155/622M aggregate
circuit pack are operating at the rate of the node capability value. The
appropriate SFPs (i.e. STM-1 or STM-4 rate) must be selected for the
2x155/622M aggregate circuit pack.
3 Each shelf requires the following components:
— two power supply units (one in slot 1 and one in slot 3)
— one OAM circuit pack in slot 2
— one 2x155/622M aggregate circuit pack in slot 6
— one filler panel in slot 7 (slot reserved for future release)
— one filler panel for each slots 4, 5, 8 and 9 (if no tributary circuit packs
are used)
— one fan module in slot 10
Note: The SFPs interfaces must be ordered separately.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-5
6 You can only replace (spare) a circuit pack with a circuit pack with the
same product engineering code (PEC).
7 1+1 MSP, SNCP, and unprotected traffic protection schemes are available.
The STM-1/4 interfaces must be provisioned in a MSP group for 1+1 MSP
protection, or in unprotected mode for SNCP or unprotected configuration.
8 Only the 8x10/100BT L1, 2xGE L1, 28xE1/DS1, 3xE3/DS3 and 2x155M
circuit packs can be inserted in the tributary slots (slots 4, 5, 8, 9).
Note: When the tributary slots are not equipped with a circuit pack, a filler
panel must be installed.
5 E1/DS1 electrical interface cable should be routed on the right side of the
bay for the 28xE1/DS1 circuit pack.
6 Install power cables on the left side of the OME6130 bay.
7 Install OAM cables (for Alarm Input, Alarm Output, M1/F1 and ESI ports)
on the left side of the OME6130 bay.
8 The Ethernet cables should be routed on the right side of the bay for the
8xETH circuit pack, and on the left side of the bay for the LAN and Craft
ports for DCN access.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-7
List of parts
This section provides the orderable codes available for the OME6130 product.
Use these tables with the ordering procedures (Procedure 8-1 on page 8-22
through Procedure 8-2 on page 8-29) to make sure that a complete and
accurate bill of material is created.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-9
Circuit packs
Table 8-7 provides a list of all the circuit packs that can be inserted into the
tributary slots of the OME6130 chassis.
For rules on equipping the shelf, refer to Shelf equipping rules on page 8-4.
Table 8-7
Circuit packs for optional service slot
Note 1: Up to four tributary circuit packs can be inserted into the OME6130 chassis.
Note 2: SFPs for the STM-1 and GE interfaces need to be ordered separately.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-11
Note: Refer to E1/DS1 cable pinouts and assemblies on page 7-18 for the
cable requirements if the cables are to be sourced locally.
Table 8-10
E1 cable assemblies
Table 8-11
DS1 cable assemblies
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-13
Table 8-12
E3/DS3 cable assemblies
Table 8-13
STM-1e cable assemblies
Table 8-14
Ethernet service cable assemblies
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-15
1 meter A
2 meters B
3 meters C
5 meters D
7 meters E
10 meters F
13 meters G
15 meters H
20 meters J
25 meters K
30 meters L
Note: This table defines the length and last digit of the
order codes shown in Table 8-15 on page 8-14. For
example, an NTTC50AD is an optical patchcord,
LC-LC, SM, Simplex, 5 meters.
Note: The LAN and Craft ports on the OAM circuit pack are wired as
MDI. Use crossover cables to connect the LAN and Craft ports to other
MDI ports (such as those on workstations). Use straight-through cables to
connect the LAN and Craft ports to MDI-X ports (such as those on
switches).
Table 8-17
DCN and craft access cables
F1 cable NT6Q71AF 1
Note 1: This F1 interface cable connects to the serial port on the OAM circuit pack and supports an
asynchronous interface.
Note 2: This modem cable has the DSR pin isolated.
Note 3: This cable provides an Ethernet connection between the Craft port on the OAM circuit pack to a
PC directly connected.
Note 4: This cable provides an Ethernet connection between the LAN port on the OAM circuit pack to the
DCN network.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-17
Table 8-18
Alarm and telemetry cables
Note 1: This environmental alarm cable kit provides a pair of alarm cables for the ALMIN and ALMOUT
ports.These cables provide the 7 alarm inputs or the critical, major, minor alarm outputs of the shelf to a
cross connect location.
Table 8-19
Synchronization cable
Note 1: This clock cable supports 120 ohm impedance with RJ-45 connector for connection to the RJ-45
ESI port on the OAM circuit pack.
Note 2: This clock cable supports 75 ohm impedance and comes with a balun converter for connection to
the RJ-45 ESI port on the OAM circuit pack.
Note 3: This clock cable supports 4 synchronization signals, (2 input and 2 output).
For more information on the PSU, refer to DC Power supply unit on page 4-4.
Refer to Procedure 8-2 on page 8-29 for ordering instructions.
Table 8-20
Power and earthing cable assemblies
Software load
This section provides the information for ordering OME6130 software, as
shown in Table 8-21.
Table 8-21
Software superset
Note 1: This code provides one copy of the OME6130 Release 1.0 software load on a CD-ROM. The
local craft access terminal load is imbedded in the network element software load.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-19
Note 1: One OME6130 software certificate is required for each OME6130 network element.
Note 2: One OME6130 Base RTU is required for each OME6130 network element.
Note 1: Nortel staging services are designed to prepare network components for integration into a
customer’s network. By centralizing the execution of services typically performed in the field at a staging
facility, the product can be delivered to the customer in its most simplified, cost effective, and integrated
form. Hot staging services for the OME6130 product consist of system testing validation prior to delivery
to the customer site.
OME6130 documentation
This section provides documentation ordering information and a brief
overview of the Nortel technical publication (NTPs) libraries and individual
documents that can be ordered for OME6130 network elements.
Documentation is available on paper and on CD-ROM. Table 8-24 lists the
ordering information for NTP packages.
Table 8-24
OME6130 documentation
Table 8-24
OME6130 documentation
Customers who operate within the EU must order the RoHS compliant version
of OME6130 equipment for equipment being supplied after 1st July 2006.
There is no change to the behavior or functionality of equipment that has been
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-21
updated to become RoHS compliant, nor is there any change required to the
software deployed - the revised RoHS compliant equipment is backward
compatible with the non-RoHS compliant version. Thus, customers outside the
EU may order the standard equipment but may receive a RoHS compliant
version.
Further information on the Nortel RoHS strategy will be made available on the
appropriate product pages on the Nortel web site (www.nortel.com).
Ordering procedures
Use the following procedures to order equipment, software, documentation,
and services for an OME6130 network deployment.
Procedure 8-1
Ordering OME6130 chassis, circuit packs, and
software
Use this procedure to order OME6130 chassis, circuit packs, and software.
Repeat this procedure for each network element at a site in the OME6130
network.
Procedure tasks
• Record requirements (step 1).
• Order chassis (step 15).
• Order circuit packs (step 16).
• Order OME6130 assembly kit (step 22).
• Order small form-factor pluggable (SFP) modules (step 24).
• Order the 75 ohm termination panel (step 25)
• Order E1/DS1 cables (step 26).
• Order software and RTU licences (step 29).
Expected results
• You have a complete list of chassis, circuit packs, and software for an OME6130 site.
• If the expected results do not occur:
— Review the network design and repeat the procedure.
— Contact your next level of support.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-23
Action
Step Action
Note: Use a photocopy of Table 8-26 on page 8-28 for this procedure. All line
number references are to this table unless noted otherwise.
1 Determine the number of 10/100BT Ethernet Private Line (EPL) services that
are required, record the number in Line 3. If no 10/100BT EPL services are
required, enter ‘none’ on Line 3.
Note: A maximum of 32 10/100BT EPL ports can be provisioned per
OME6130 shelf (8 ports for each 8x10/100BT L1 tributary circuit pack).
2 Determine the number of 8x10/100BT L1 tributary circuit pack that are
required. Divide the number recorded on Line 3 by 8 and record the round up
integer value on Line 4. Enter ‘none’ if no 8x10/100BT L1 tributary circuit pack
is required.
3 Determine the number of GE EPL services that are required, record the
number in Line 5. If no GE EPL services are required, enter ‘none’ on Line 5.
Note: A maximum of 8 GE EPL ports can be provisioned per OME6130 shelf
(2 ports for each 2xGE L1 tributary circuit pack).
4 Determine the number of 2xGE L1 tributary circuit pack that are required.
Divide the number recorded on Line 5 by 2 and record the round up integer
value on Line 6. Enter ‘none’ if no 2xGE L1 tributary circuit pack is required.
5 Determine the number of E1/DS1 services that are required, record the
number in Line 7. If no E1/DS1 services are required, enter ‘none’ on Line 7.
Note: A maximum of 112 E1/DS1 ports can be provisioned per OME6130
shelf (28 ports for each 28xE1/DS1 tributary circuit pack).
6 Determine the number of 28xE1/DS1 tributary circuit pack that are required.
Divide the number recorded on Line 7 by 28 and record the round up integer
value on Line 8. Enter ‘none’ if no 28xE1/DS1 tributary circuit pack is
required.
7 Determine the number of E3/DS3 services that are required, record the
number in Line 9. If no E3/DS3 services are required, enter ‘none’ on Line 9.
Note: A maximum of 12 E3/DS3 ports can be provisioned per OME6130
shelf (3 ports for each 3xE3/DS3 tributary circuit pack).
8 Determine the number of 3xE3/DS3 tributary circuit pack that are required.
Divide the number recorded on Line 9 by 3 and record the round up integer
value on Line 10. Enter ‘none’ if no 3xE3/DS3 tributary circuit pack is
required.
Step Action
9 Determine the number of STM-1o/e services that are required, record the
number in Line 11. If no STM-1o/e services are required, enter ‘none’ on Line
11.
Note: A maximum of 8 STM-1o/e ports can be provisioned per OME6130
shelf (2 ports for each 2x155M tributary circuit pack).
10 Determine the number of 2x155M tributary circuit pack that are required.
Divide the number recorded on Line 11 by 2 and record the round up integer
value on Line 12. Enter ‘none’ if no 2x155M tributary circuit pack is required.
11 Add the number of tributary circuit packs recorded on Line 4, Line 6, Line 8,
Line 10 and Line 12.
If you need Then
4 tributary circuit packs or less go to step 12
5 tributary circuit packs or more more than one OME6130 shelf needs to
be ordered. Re-assign some of the
services to another OME6130 shelf and
ensure that up to 4 tributary circuit pack
is required per shelf, then go to step 1
on page 8-23
Note: The OME6130 chassis has four tributary slots for services. Up to four
circuit packs can be added to the chassis. Refer to Shelf equipping rules on
page 8-4 for more details.
12 Determine the type of E1/DS1 cables required.
If you require Then
E1 electrical interfaces Enter ‘75 ohm’ in Line 13.
at 75 Ohm
E1 electrical interfaces Enter ‘120 ohm’ in Line 13.
at 120 Ohm
DS1 electrical interfaces Enter ‘100 ohm’ in Line 13.
at 100 Ohm
no electrical E1/DS1 services Enter ‘none’ in Line 13.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-25
Step Action
Step Action
26 Order the E1 cables for the 75 ohm termination panel for the 28xE1/DS1
circuit pack:
If Line 15 is Then order the number obtained at step 13 times of
1 one (1) NT6Q75AA (Right routing - 1 meter cable)
5 one (1) NT6Q75CA (Right routing - 5 meter cable)
Go to step 29.
27 Order the E1 cables for the 120 ohm application for the 28xE1/DS1 circuit
pack:
If Line 15 is Then order the number obtained at step 13 times of
5 one (1) NT6Q73BA (Right routing - 5 meter cable)
10 one (1) NT6Q73CA (Right routing - 10 meter cable)
15 one (1) NT6Q73DA (Right routing - 15 meter cable)
20 one (1) NT6Q73EA (Right routing - 20 meter cable)
Go to step 29.
28 Order the DS1 cables for the 28xE1/DS1 circuit pack:
If Line 15 is Then order the number obtained at step 13 times of
15 one (1) NT6Q73QA (Right routing - 15 meter cable)
30 one (1) NT6Q73TA (Right routing - 30 meter cable)
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-27
Step Action
29 Order one (1) NT6Q83AA CD-ROM copy of Release 1.0 software for each
site.
30 Order RTU licences. Order one NT6Q82AA for each OME6130 shelf.
31 Order software certificates. Order one NT6Q85AA for each OME6130 shelf.
32 Repeat this procedure for each network element at this site. When all network
elements have been ordered for this site, continue the ordering process with
Procedure 8-2 on page 8-29.
—end—
Table 8-26
OME6130 shelf ordering worksheet
Line Description Value
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-29
Procedure 8-2
Ordering cables, documentation, and services
Use this procedure to order cables, documentation, and services for the
OME6130 equipment ordered in Procedure 8-1 on page 8-22. Repeat this
procedure for each site in the OME6130 network.
Procedure tasks
• Record site specific information (step 1).
• Order power cables (step 2).
• Order optical fiber patch cords (step 3).
• Order OAM and LAN cables (DCN, user interface, alarm and synchronization) (step 4).
• Order documentation (step 10).
• Order services (step 11).
Expected results
• You have a complete list of cables, documentation, and services for an OME6130 site.
• If the expected results do not occur:
— Review the network design and repeat the procedure.
— Contact your next level of support.
Action
Step Action
Note: Use a photocopy of Table 8-27 on page 8-32 for this procedure. Line
references in this procedure refer to this table unless otherwise noted.
1 Record site specific information on Line 1 through Line 8 of Table 8-27 on
page 8-32.
2 Order DC power cables for the number of OME6130 NEs specified in Line 2.
Order the appropriate DC cable for the region, as specified in Line 1, and for
the length required, as shown on Line 3.
Note: Refer to Table 8-20 on page 8-18 and Bay equipping rules on page 8-4
for orderable codes and application rules.
Step Action
3 Order fiber patchcords. Refer to Table 8-15 on page 8-14 and Table 8-16 on
page 8-15 for orderable codes and application rules.
Note: The STM-1/4 optical SFP modules on the OME6130 support duplex
LC connections. Nortel Networks recommends the use of duplex patchcords
wherever allowed by the subtending equipment.
4 Order environmental alarm kits. Order one environmental alarm kit for the
number OME6130 network elements specified on Line 4.
Note: Refer to Table 8-18 on page 8-17 for orderable part numbers and
application rules.
5 Order the number of LAN 10/100BT Ethernet cables specified in Line 5 to
connect to the OME6130 network elements to the DCN.
Note: A regular straight 10/100BT Ethernet cable (RJ-45 to HUB RJ-45) will
accommodate this connection. Refer to Table 8-17 on page 8-16 for
orderable part numbers and application rules.
6 Determine the next step:
If Line 6 is Then go to
Yes step 7
No step 8
Note: Refer to Table 8-19 on page 8-17 for orderable part numbers and
application notes.
10 Order documentation. Nortel Networks recommends that one CD-ROM be
ordered for each site. Alternatively, a paper library is available.
Note: Refer to Table 8-24 on page 8-19 for orderable codes and application
notes.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-31
Step Action
Table 8-27
Worksheet for ordering cables, documentation and services for OME6130 network elements
Line 8 Are 75 ohm or 120 ohm interfaces required for ESI connector at
this site?
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-33
Table 8-28
RoHS codes and ordering summary
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-35
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Ordering information and system engineering rules 8-37
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
9-1
Technical assistance 9-
CE mark 9-3
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical assistance 9-3
CE mark
The following is an example of the Conformité Européenne (CE) mark
indicating that all electromagnetic compatibility (EMC) and other
electrotechnical requirements are met and that the product complies with all
applicable standards.
Note: Some of the information that you must provide (such as alarms
raised) require you to log in to the network element.
Customer Identification
Customer name:
Site location:
Originator name:
PEC:
Release:
Serial number:
Network element
NE name:
NE number:
NE type:
NE configuration:
Failure symptoms
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Technical assistance 9-5
Failure data
LED status:
Failure time
Troubleshooting data
Special instructions:
General comments:
Tracking information
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
10-1
Topic Page
Introduction 10-2
OAM&P Ports 10-3
Network Interface 10-4
STM-1/4 Data Communication Channel 10-7
IP communication 10-11
OSI data communications 10-16
Application protocols 10-21
Diagnostic commands 10-22
Firewall considerations 10-22
Engineering guidelines 10-23
Supported DCN design examples 10-25
IP networks, addressing, and masks 10-93
IP routing protocols 10-97
Introduction
OME6130 is an IP managed optical network element (NE), which has the
capabilities to communicate through both TCP/IP Internet Protocol (IP) and
OSI Connectionless Network Protocol (CLNP) based networks.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-3
OAM&P Ports
This section describes the ports which can be used to perform OAM&P
operations on an OME6130 network element.
M1/F1 port
OME6130 shelf supports a serial communication port which can operate under
the following applications:
/24 255.255.255.0
/25 255.255.255.128
/26 255.255.255.192
/27 255.255.255.224
/28 255.255.255.240
/29 255.255.255.248
/30 255.255.255.252
/32 255.255.255.255
Network Interface
The network interfaces of the OME6130 network element are logical
representation of the management channels for OAM&P. Each network
element has a minimum of one network interface (eth0) for the LAN port. A
maximum of ten DCC in-band channels can be provisioned per network
element. Besides the eth0 network interface, ten additional DCC network
interfaces can be a combination of the E1/VC12 management channel (mgmt1
or mgmt2) and the embedded communication channel of the SFP interfaces.
Static and dynamic (Auto) GRE tunnels are also represented as network
interface entities.
The eth0 network interface is created by default and can not be deleted.
The mgmt1 and mgmt2 network interfaces are created when the E1/VC12
management channels are provisioned via the DCN/Management Channel
application, and they are deleted when the E1/VC12 management channels are
unprovisioned from the application. Only IP/PPP is supported over the
E1/VC12 management channels (and it supports only OSPF as routing
protocols).
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-5
The static and Auto GRE tunnels are also created as network interfaces. When
iIS-IS is enabled at the nodal level on the network element, the Auto GRE
tunnel (AGRE) network interface is automatically created and will be deleted
upon disabling the iIS-IS nodal parameter. Upon enabling nodal iIS-IS on the
NE, a static GRE tunnel (SGRE) network interface can be created by
specifying the remote manual area address, remote system ID (MAC address)
and the NSAP selector byte.
Table 10-3
Network interface provisionable parameters summary
Note 1: It is recommended to leave the Eth0 network interface port in Admin Up state.
Note 2: OSPF and iISIS cannot be simultaneously enabled for a network interface.
Note 3: E1/VC12 management communication between OME6130 and OME6110 (Release 1, Release
2.0, Release 2.01 software) should use Layer 2 Protocol as Standard PPP, RFC1661.
Note 4: The Auto GRE tunnel is automatically created when iISIS is enabled at the nodal level on the
NE. The AGRE network interface parameters are not user-provisionable.
Note 5: The Static GRE tunnel can only be created if iISIS is enabled at the nodal level.
Table 10-4
Dynamic routing protocol parameters
Note 1: In this release, the L2 Default Metric and L2 Routing Only parameters are not
supported for iISIS routing protocol.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-7
Note 1: PPP uses IP Control Protocol (IPCP) over OSI Network Layer
Control Protocol (OSINLCP) to pass data between layer 2 and layer 3
protocols. Recommended for standard implementation.
Note 2: Use this option for interworking with any Nortel equipment which
supports IP/PPP over DCC channel.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-9
“Route diversity disabled” mode uses a single DCC channel which is switched
with the traffic for management, which is unlike the “route diversity enabled”
mode where each interface of the 1+1 MSP link has a separate DCC channel
that is not switched with the MSP protected traffic.
When an OME6130 NE, which has its DCC route diversity disabled, is
interworking in a 1+1 MSP uni-directional switching mode with other NE (e.g.
OM4000) with route diversity enabled, a single fibre break in the Rx direction
of the non-OME6130 NE in working path can result in lost of communication
between the two NEs because the OME6130 NE can still receive traffic on the
working interface which the transmit has failed, therefore bi-directional LAPD
adjacency can not be established on neither the working path nor the protection
path, and hence loss of communication. There will no loss of communication
if both fibres (Tx and Rx) on the working path fail at the same time so that
bi-directional LAPD adjacency can be establish on the protection path.
• Only one regenerator section (RS) or multiplex section (MS) DCC can be
enabled per optical port.
• Each DCC can support HDLC, PPP or LAPD. The default is PPP.
— When using DCC to connect to an OME6130 (or any network element
that supports IP based DCC datalink layer), select PPP as the protocol.
— When using DCC to connect to an OSI-based DCC datalink layer,
select LAPD as the protocol.
• Set the LAPD IP MTU size to 446 when interworking with Optical Cross
Connect DX/ HDXc/ HDX, and Optical Multiservice Edge 6500. The user
has to manually configure the connected SDH interfaces to 512 bytes for
the LAPD MTU. The OME6130 LAPD MTU is set to 512 by default.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-11
• Set the LAPD IP MTU size to 446 when interworking with Optical Metro
4000 and TN-1C family of products which has a fixed LAPD MTU of 512
bytes. The OME6130 LAPD MTU is set to 512 by default.
• On a DCC interface over SDH overhead bytes, both OSPF and iISIS
routing protocols cannot be enabled simultaneously.
IP communication
TCP/IP Internet Protocol (IP) is a network layer protocol and the OME6130
uses IPv4. Each OME6130 shelf must have one IP address assigned to it for
management purposes. Typically, the IP address used to manage the OME6130
is the circuitless IP address. The circuitless IP is designated as Router ID.
CAUTION
Circuitless IP (Router ID) address
The circuitless IP has a non-provisionable default subnet mask
of 255.255.255.255.
Static routing
As with standard routers, the OME6130 supports configuration of static
routes.
Static route implementation rules
You must observe the following rules when you implement a static route:
• Static routes can be provisioned on any of the network interfaces up to a
maximum of 10.
• Static routes on valid PPP interfaces, such as STM-1/4 ports, SGRE,
AGRE, E1 or VC12 management channels, should be provisioned with
next hop IP address 0.0.0.0.
• Set the OSPF parameter to Disable and provision the static route for the
appropriate PPP network interface.
Note: The static routes can be configured in the NE for redistribution
(advertising over routing protocols over to other NEs). The redistribution
is applied to the routing protocol that is provisioned on the NE: OSPF only,
iISIS only or both simultaneously. It is not possible to redistribute a static
route only over OSPF or only over iISIS, if both routing protocols are
enabled on the network element.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-13
The OME6130 supports enabling and disabling of OSPF routing protocol per
IP-carrying interface, including Eth0, PPP/cHDLC DCC, and SGRE
interfaces.
For more information about OSPF, see IP routing protocols on page 10-97.
OSPF routing implementation rules
You must observe the following rules when you implement the OSPF routing:
• Default user configurable OSPF area of 0.0.0.1 for all network interfaces
for which the OSPF parameter is enabled.
• Set the OSPF parameter to Enable to use dynamic routing over the
network interfaces.
• When OSPF is enabled on the eth0 network interface (LAN port), the
provisioned Ethernet sub-network is advertised as part of the OSPF link
state advertisement (LSA).
• The Router ID IP address is used only in OSPF hello packets to form OSPF
adjacencies. This allows multiple different OSPF areas of 0.0.0.1 to exist
in the customer network as long as the OME6130 NEs are connected to
different Area Border Routers (ABRs). See Figure 10-1 on page 10-14.
• It is recommended to use the Ethernet IP address as the Router ID IP
address if the NE has only direct LAN connectivity.
• It is recommended to use a different Router ID IP address other than the
Ethernet IP address if the NE has DCC enabled.
• When OSPF is enabled on the Ethernet port and DCC is being used to
provide OA&M, the Router ID IP address should be in a different
sub-network other than the Ethernet IP address sub-network.
• Re-distribution of static route into OSPF routing table is supported. By
default, static route re-distribution is disabled.
• Route redistribution between OSPF and iISIS routing protocols is not
supported.
Figure 10-1
Multiple OSPF 0.0.0.1 areas
ABR 2
ABR 1
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
iISIS routing protocol allows the creation of an Link State Packet (LSP)
database of all OSI only, IP only, and Dual Stack network elements within its
level 1 area. iISIS routing protocol creates IP Routing Information Base (RIB)
that contains route information for all network elements that have at least one
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-15
IP address configured and is in the same level 1 area. iISIS routing protocol
also creates CLNP forward information base (FIB) updates based on LSP
database for all reachable OSI network elements.
iISIS routing implementation rules
You must observe the following rules when you implement the iISIS routing:
• Support provisioning of three manual area addresses:
— MAA1 default value of 490000
— MAA2, blank with 3 to 13 bytes long
— MAA3, blank with 3 to 13 bytes long
• Level 1 routing is supported
• Enabling and disabling of iISIS routing protocol is done on a per PPP,
LAPD based DCN interface. The default value is iISIS-Disabled.
• The iISIS routing protocol will support only configuration of default
metric as the routing metric for each circuit. The range of the default metric
shall be [1 - 63] and the default value is 4.
• Route redistribution between OSPF and iISIS routing protocols is not
supported.
Routing protocol configuration
OME6130 supports nodal level configuration of enabling or disabling of
Integrated Intermediate System Intermediate System (iISIS) routing protocol.
By default, iISIS routing protocol is disabled. OSPF routing protocol is always
enabled at the nodal level, but must be provisioned per network interface.
Proxy ARP
Proxy ARP allows a gateway network element to respond to address resolution
protocol (ARP) requests for subtending network elements that are within the
same subnet as the customer DCN address range. The proxy ARP feature
removes the need for customers to provision static routes on their routers and
routing protocols (OSPF) between the gateway network elements and the
customer DCN.
Proxy ARP is only supported on the LAN interface of the OME6130 network
element. At the gateway OME6130 network element, the IP address of
neighbouring network elements can be provisioned for Proxy ARP. The GNE
will perform proxy ARP for IP addresses of neighbouring NEs that are on the
same subnet s the DCN router connected to the LAN interface.
• assign a subnet on the DCN router port that connects to the LAN port of
the gateway network element that is large enough to support the LAN port
and the router ID address of every network element for which the gateway
network element will proxy ARP
• provision the IP addresses of the proxy ARP neighbours for which the
gateway network element will respond for. The IP addresses should be of
the hosts, not the network.
• provision a maximum of 14 proxy ARP neighbours
• ensure that the DCN router interfaces connected to the LAN interface will
ARP for the specified ARP neighbours
• provision a static route to the DCN network. At the remote/neighbouring
NEs, static routes do not need to be provisioned to the router
CLNP
OSI Connectionless Network Protocol (CLNP) is a network layer 3 protocol
which provides services to the upper transport layer, similar to the Internet
Protocol (IP) in the a TCP/IP environment. CLNP is often referred to as
ISO-IP. CLNP uses NSAP addresses to identify network devices. The
OME6130 supports CLNP protocol as specified in ISO/IEC 8473-1.
The OME6130 provides the ability to tunnel IP communications over OSI. The
OME6130 will route (forward) only IP packets and OSI (CLNP) PDUs
(support of reassembly of segmented DPDUs).
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-17
The OME6130 provides a SNDCF interface that allows layer 2 protocols such
as LAPD and PPP to interface with CLNP, ESIS, and ISIS routing protocols.
The GRE layer module will interact with CLNP via the addition of Network
Service User of CLNP.
• OME6130 requires an OSI local manual area address to interop with other
OSI products. The local manual area addresses are used to form the NSAP
address of each network element in the OSI level 1 area.
• The default manual area address is 490000.
• Up to three local manual area address can be provisioned for iISIS. The
OME6130 NE can be part of up to 3 areas.
• All NSAP formats are supported:
— ISO Local Addressing Format - e.g. 490000
— ISO DCC Addressing Format - e.g. 39xxxxxxxxxxxxxxxx
• In order to communicate with an Intermediate System (IS) network
element, provision the Local Manual Area Address to be the same as the
Manual Area Address of the connected IS NE. The iISIS protocol will
establish adjacency between NEs in an area if they have one Manual Area
Address common.
• For communication to network elements in different OSI area, the Local
Manual Area Address has to be the unique area address used in the
networks which use both the default 490000 Manual Area Address and a
unique 39xxxxxxxxxxxxxxxxx Manual Area Address.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-19
The auto GRE tunnel is automatically configured and enabled when iISIS
routing protocol is enabled at the nodal level. There is no specific user
configuration required. The IP over OSI tunnel creation is done automatically
on a per packet basis over all the packets forwarded to the auto GRE interface
by IP. A default static route shall be provisioned automatically on the auto
GRE (called agre0) interface that is presented to the IP protocol stack. In this
scenario, the IP protocol stack shall forward packets that are not routable by
any other IP routing table entry to the auto GRE tunnel for further processing.
The default route shall have the last priority, as any user provisioned specific
static route shall have higher priority than default route when routing packets.
Figure 10-2
IP Packet Routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-21
• Provision the NSAP Selector Byte of the tunnel destination node. Use
hexadecimal 2F (47 in decimal) for GRE protocol.
Note: When provisioning a static GRE tunnel between the OME6130 and
OME6500, a mismatch of the NSAP selector bytes provisioned at the
OME6500 and the OME6130 is expected. The NSAP Selector Byte
provisioned at the OME6130 WUI should be set to 2F, and the network
selector (NSEL, last 2 bytes of NSAP) provisioned from the OME6500
craft interface must be set to 00. The OME6500 automatically sets the
NSEL internally to support the required transport service.
Application protocols
This section lists out the supported application protocols and commands which
can be useful while working and troubleshooting an OME6130 network
element.
ftp
TCP/IP File transfer protocol (FTP) is a standard application layer protocol
used for transferring files across a network. This protocol uses a client/server
architecture. Both the FTP client and server are enabled on the OME6130. The
OME6130 supports active FTP.
telnet
TCP/IP Telnet is a standard application layer terminal protocol used for
accessing remote computers, in a text based communications session between
a client and a host.
Both the Telnet client and server are enabled on the OME6130.
Diagnostic commands
This section lists the diagnostic commands which can be used on an OME6130
network element in a telnet session.
arp
Address resolution protocol utility
ifconfig
Displays status information for all interfaces.
ping
ICMP echo request and reply to test IP layer 3 connectivity. This command
requires root privilege.
route
Displays the kernel IP routing table.
tcpdump
Prints out headers of packets on all or specified interface. This command
requires root privilege.
Firewall considerations
The following ports must be passed through any firewall between the
management systems and the OME6130 network:
• TCP
— 20 (data), 21 (control) - FTP ports used for upgrades, or backup and
restore configurations.
— 2023 - Telnet port used for troubleshooting.
— 10001 - Used by TL-1 without prompt and character echo
— 10002 - Used by TL-1 with prompt and character echo
— 20080 - Used by HTTP for Web User Interface (WUI)
• UDP
— None used
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-23
Engineering guidelines
The following are DCN engineering guidelines:
ATTENTION
For configurations that exceed the following guidelines, contact Nortel for
assistance.
• STM-1/4 DCC
— Maximum of 10 DCCs per network element
— Maximum of 1 Regenerator section (RS) or Multiplex section (MS)
DCC per optical interface
— Regenerator section (RS) DCC using D1-D3 bytes at 192 kbps
— Multiplex section (MS) DCC using D4-D12 bytes at 576 kbps
• LAPD
— MTU frame size of 240 to 512 bytes (default is 512)
— Metric: The DCC default metric is set to 4. When interworking with
legacy network elements, use the following DCC metrics:
– MS DCC: 5
– RS DCC: 6
— CLNP supported over LAPD (Default MTU frame size of 512 bytes
when presented to CLNP. The MTU size is user configurable and
should be in the range [240-512] bytes).
• PPP
— MTU frame size of 1518 bytes
— Non-configurable default parameters:
– Maximum receive unit: no limitation
Note: Does not perform negotiation for MRU and accepts packets of any
size
• OSPF
— Configurable default area of 0.0.0.1
— Maximum of 150 routers in the same OSPF area as the OME6130 NE
— Supports non-stub area
— Configurable parameters:
– Hello Interval: 10 seconds. The range is [1-65535] seconds.
– Dead Interval: 40 seconds. The range is [1-65535] seconds.
— Non-configurable default parameters:
– Retransmit Interval: 5 seconds
– Transmit Delay: 1 second
– OSPF Ethernet Cost: 1
– OSPF DCC Cost: 1
– OSPF GRE Costs: 1
– OSPF LAN priority: 1
— OSPF Authentication mode : disabled (default) or Simple Password:
– Enabling and disabling of password based authentication for OSPF
on a per layer 2 interface level. If password based authentication is
enabled, then password is configurable.
— OSPF Authentication key: String configurable by the user if the OSPF
Authentication mode is set to Simple Password.
Note: For maximum network performance, the external DCN intervals
should be aligned with OME6130.
• IP
— Maximum of 4096 IP routes (static and dynamic). But for optimal
performance it is recommended that not more than 512 entries be
added in the IP routing table. (Note that the IP routing table entries
include the routing entries added by OSPF or iISIS or Static Route into
the IP routing protocol domain).
— Maximum of 10 static routes per NE
– Use Destination Network IP address of 0.0.0.0/0 with next hop IP
address for default route
— MTU packet size of 240 to 512 bytes for OSI CLNP/LAPD
— MTU packet size of 1518 bytes for IP/PPP
• GRE
— Tunnels between different OSI areas are supported
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-25
— MTU packet size should be 66 bytes less than the MTU for LAPD
• Telnet session
— on the number of concurrent sessions per network element
— Session timeout is not supported
• TL-1 sessions
— maximum of 4 concurrent sessions per network element
DCN performance
This section details the guidelines for DCN performance.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-27
Routing protocol (static or dynamic) is not required from the DCN router to
each of the OME6130 network element. The external router and the OME6130
LAN interfaces are in the same subnet. A static route is required from each of
the network element to the DCN router interface.
This example does not provide redundant access to any of the OME6130
network elements because each OME6130 NE is connected to the external
DCN with one Ethernet port (i.e. LAN port).
DCN provisioning details
Table 10-5 on page 10-29 and Table 10-6 on page 10-30 detail the DCN
parameters for the DCN example 1 configuration.
Figure 10-3
DCN example 1 - Static routing with direct LAN connections to OME6130 network elements
OMEA
IP DCN R6
IP
R1 R2 R3 R4 R5
IP IP IP
IP IP
OME OME OME
Target 61x0 61x0 61x0
Node B C D
OME OME
61x0 61x0
A No DCC E
Legend
= iIS-IS/OSI/LAPD/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME61x0 = OME6110 or OME6130
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-29
Figure 10-4
DCN example 1 - IP logical view
OMEA
IP DCN
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
Table 10-5
DCN example 1 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 47.1.3.5 47.1.3.12 47.1.4.5 47.1.4.18 47.1.4.26
Netmask /29 /29 /29 /29 /29
Default gateway - - - - -
Router ID:
IP address - - - - -
Netmask - - - - -
3 Set up DCC
STM1/4-x-1:
Protocol Disabled Disabled Disabled Disabled Disabled
MTU - - - - -
STM1/4-x-2
Protocol Disabled Disabled Disabled Disabled Disabled
MTU - - - - -
Table 10-6
DCN example 1 - Router and OMEA provisioning details
Ethernet interface:
IP address 47.1.3.1 47.1.3.9 47.1.4.1 47.1.4.17 47.1.4.25 47.1.1.1 47.1.1.5
Netmask /29 /29 /29 /29 /29 /29 /29
Default gateway - - - - - - 47.1.1.1
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-31
Static routes are used on both the OME6130 and the connected external DCN
router. The static route provisioned on the external DCN router is redistributed
inside the external DCN by the external DCN routing protocol so that the
proper route is available for the management system to reach the OME6130
sub-system.
This example does not provide redundant access to the OME6130 sub-system
from the external DCN because only one OME6130 NE is connected to the
external DCN. However, the DCC between the OME6130 NEs is redundant.
DCN provisioning details
Table 10-7 on page 10-33 and Table 10-8 on page 10-34 detail the DCN
parameters for the DCN example 2 configuration.
Figure 10-5
DCN example 2 - Single OME6130 GNE with static routing
OMEA R1
IP
R2
IP DCN
OME
61x0
B OME
61x0
Target A
node
OME
61x0
D
OME
61x0
C
Legend
= iIS-IS/OSI/LAPD/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME61x0 = OME6110 or OME6130
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-33
Figure 10-6
DCN example 2 - IP logical view
OMEA
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
Table 10-7
DCN example 2 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 47.1.3.6 192.168.1.254 192.168.1.254 192.168.1.254
Netmask /29 /24 /24 /24
Default gateway - - - -
Router ID:
IP address 47.1.3.66 47.1.3.67 47.1.3.68 47.1.3.69
Netmask /32 /32 /32 /32
3 Set up DCC
STM1/4-x-1:
Protocol PPP PPP PPP PPP
MTU 1518 1518 1518 1518
OSPF Enable Enable Enable Enable
STM1/4-x-2
Protocol PPP PPP PPP PPP
MTU 1518 1518 1518 1518
OSPF Enable Enable Enable Enable
Table 10-8
DCN example 2 - Router and OMEA provisioning details
Ethernet interface:
IP address 47.1.1.1 47.1.3.1 47.1.1.5
Netmask /29 /29 /29
Default gateway - - 47.1.1.1
Circuitless IP/ Loopback
IP Address 47.1.1.128 47.1.1.129 -
Netmask /32 /32 -
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-35
DCN example 3 - Using single OME6130 GNE with OSPF to external DCN.
OSPF is used in between OME6130 network elements.
In this example (see Figure 10-7 on page 10-36 and Figure 10-8 on page
10-37), a single OME6130 network element is used as the GNE to establish
communication between the external DCN and the OME6130 sub-system.
OSPF routing protocol is used in between the OME6130 GNE and the external
DCN router, and in between the OME6130 network elements using IP over
DCC.
The external DCN router connected to the OME6130 GNE is acting as an Area
Border Router (ABR) which can use the route summarization feature to group
the IP routes for the OME6130 sub-network into a single route covering all the
OME6130 Router ID IP addresses.
This example does not provide redundant access to the OME6130 sub-system
from the external DCN because only one OME6130 NE is connected to the
external DCN. However, the DCC between the OME6130 NEs is redundant.
DCN provisioning details
Table 10-9 on page 10-37 and Table 10-10 on page 10-38 detail the DCN
parameters for the DCN example 3 configuration.
Figure 10-7
DCN example 3 - Single OME6130 GNE with OSPF
OMEA R1
IP
R2
IP DCN
OME
61x0
B OME
61x0
Target A
node
OME
61x0
D
OME
61x0
C
Legend
= iIS-IS/OSI/LAPD/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME61x0 = OME6110 or OME6130
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-37
Figure 10-8
DCN example 3 - IP logical view
OMEA
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
Table 10-9
DCN example 3 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 47.1.3.6 192.168.1.254 192.168.1.254 192.168.1.254
Netmask /29 /24 /24 /24
Default gateway - - - -
Router ID:
IP address 47.1.3.65 47.1.3.66 47.1.3.67 47.1.3.68
Netmask /32 /32 /32 /32
2 Set up IP routing
STM1/4-x-1:
Protocol PPP PPP PPP PPP
MTU 1518 1518 1518 1518
OSPF Enable Enable Enable Enable
STM1/4-x-2
Protocol PPP PPP PPP PPP
MTU 1518 1518 1518 1518
OSPF Enable Enable Enable Enable
Table 10-10
DCN example 3 - Router and OMEA provisioning details
Ethernet interface:
IP address 47.1.1.1 47.1.3.1 47.1.1.5
Netmask /29 /29 /29
Default gateway - - 47.1.1.1
Circuitless IP/ Loopback
IP Address 47.1.1.128 47.1.1.129 -
Netmask /32 /32 -
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-39
DCN example 4 - Using OSPF with dual OME6130 GNEs to external OSPF
backbone.
In this example (see Figure 10-9 on page 10-40 and Figure 10-10 on page
10-41), two OME6130 network elements are used as dual GNEs to establish
communication between the external DCN and the OME6130 sub-system.
Typically, the two gateway NEs are located in two different sites and subnets
to maximize the network resilience.
When the OME6130 sub-system does not provide a resilient internal DCN
structure (e.g. linear chain), route summarization should not be used at the
ABR or resilient communications will be lost.
Note: Two or more GNEs can be used within the engineering limits.
DCN provisioning details
Table 10-11 on page 10-42, Table 10-12 on page 10-42 and Table 10-13 on
page 10-43 detail the DCN parameters for the DCN example 4 configuration.
Figure 10-9
DCN example 4 - Dual OME6130 GNEs with OSPF
OMEA
R1
IP
R3
IP DCN R2
OME
61x0
A OME
61x0
Target B
node
OME
61x0
C
OME
61x0
OME D
61x0
E
OME
61x0
F
OME
61x0
G
Legend
= iIS-IS/OSI/LAPD/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME61x0 = OME6110 or OME6130
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-41
Figure 10-10
DCN example 4 - IP logical view
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
Table 10-11
DCN example 4 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 47.1.3.6 47.1.3.18 47.1.3.81 47.1.3.85
Netmask /29 /28 /30 /30
Default gateway - - - -
Router ID:
IP address 47.1.3.65 47.1.3.66 47.1.3.67 47.1.3.68
Netmask /32 /32 /32 /32
2 Set up IP routing
3 Set up DCC
STM1/4-x-1:
Protocol PPP PPP PPP PPP
MTU 1518 1518 1518 1518
OSPF Enable Enable Enable Enable
STM1/4-x-2
Protocol PPP PPP PPP PPP
MTU 1518 1518 1518 1518
OSPF Enable Enable Enable Enable
Table 10-12
DCN example 4 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 47.1.3.82 47.1.3.86 192.168.1.254
Netmask /30 /30 /24
Default gateway - - -
Router ID:
IP address 47.1.3.69 47.1.3.70 47.1.3.71
Netmask /32 /32 /32
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-43
STM1/4-x-1:
Protocol PPP PPP PPP
MTU 1518 1518 1518
OSPF Enable Enable Enable
STM1/4-x-2
Protocol PPP PPP PPP
MTU 1518 1518 1518
OSPF Enable Enable Enable
Table 10-13
DCN example 4 - Router and OMEA provisioning details
Ethernet interface:
IP address 47.1.1.1 47.1.3.1 47.1.3.17 47.1.1.5
Netmask /29 /29 /28 /29
Default gateway - - - 47.1.1.1
Circuitless IP/ Loopback
IP Address 47.1.1.128 47.1.1.129 47.1.1.130 -
Netmask /32 /32 /32 -
2 Set up IP routing
DCN example 5 - Using single OM4000 GNE with GRE tunnels through
OM4000 network to reach remote OME6130 network elements in linear
spurs off OM4000 NE.
In this example (see Figure 10-11 on page 10-45 and Figure 10-12 on page
10-46), the OME6130 is subtended as 1+1 MSP link with OM4000 and IP
static routing between the router and OME6100 is possible using GRE tunnel.
The router has a static route over the GRE tunnel to the router ID IP address of
the OME6100 NE and the OME6100 NE has a static route over the GRE
tunnel to the router.
The external router redistributes the static IP route into a dynamic routing
protocol, in order to advertise the OME6130 router IP addresses to the external
DCN.
The router on which the IP over OSI GRE tunnels terminate can only be a
Cisco router that supports ISO CLNS, with an IOS which has the “IP over
CLNS tunnel (CTunnel)” using GRE encapsulation feature. Some older
versions of IOS support IP over OSI tunnels using Cisco proprietary
encapsulation which is not suitable in this application.
DCN provisioning details
Table 10-14 on page 10-46 and Table 10-15 on page 10-48 detail the DCN
parameters for the DCN example 5 configuration.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-45
Figure 10-11
DCN example 5 - Single OM4K GNE with GRE tunnels to remote OME6130 NEs in linear 1+1 MSP
with OM4K
OMEA R1
IP
IP and R2
OSI DCN
Target
node OME OSI (4K/3K)
1+1 MSP/APS OM
61x0 4K/3K
A E
OM
4K/3K
C
OM
4K/3K
D
Legend
= iIS-IS/OSI/LAPD/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME61x0 = OME6110 or OME6130
Figure 10-12
DCN example 5 - IP logical view
OMEA
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
Table 10-14
DCN example 5 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 192.168.1.254 192.168.1.254
Netmask /24 /24
Default gateway - -
Router ID:
IP address 47.1.3.65 47.1.3.66
Netmask /32 /32
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-47
4 Set up DCC
STM1/4-x-1:
Protocol LAPD LAPD
MTU 512 512
iISIS Enable Enable
STM1/4-x-2
Protocol - -
MTU - -
Table 10-15
DCN example 5 - Router, OMEA, and OM4K DCN provisioning details
Interface: - - - - -
IP address 47.1.1.1 - - - -
Netmask /29 - - - -
Interface: - - - - -
IP address - - - - 47.1.1.5
Netmask - - - - /29
Default gateway - - - - 47.1.1.1
Circuitless IP/ NE-IP:
IP address 47.1.1.128 47.1.1.129 - - -
Netmask /32 /32 - - -
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-49
DCN example 6 - Using single OM4000 GNE with GRE tunnels through
OM4000 network to reach remote OME6130 network elements in SNCP
ring with an OM4000 network element.
In this example (see Figure 10-13 on page 10-51 and Figure 10-14 on page
10-52), a single ABR is used at the DCN gateway site to establish
communication between the external DCN and the OME6130/OM4000
sub-systems.
A single OM4K is connected to the external DCN via an OSI only enabled port
and acts as the GNE for the other OM4K network elements.
For configurations with fully robust (meshed/ring) internal DCN connectivity
Data communication to the remote subtending OME6130 network elements is
achieved using IP over OSI GRE tunnels through the OM4K network and these
tunnels are terminated directly on the ABR. In order to provide resilient data
communication against any fiber breaks in the OME6130 system, two tunnels
are required from the ABR through the OM4KGNE. iISIS routing is used to
establish communication to all OME6130 within the ring.
Note: OSPF routing on the GRE tunnel to the router, and OSPF routing is
used between OME6130 network elements can be used.
The ABR on which the IP over OSI GRE tunnels terminate can only be a Cisco
router that supports ISO CLNS, with an IOS which has the “IP over CLNS
tunnel (CTunnel)” using GRE encapsulation feature. Some older versions of
IOS support IP over OSI tunnels using Cisco proprietary encapsulation which
is not suitable in this application.
DCN provisioning details
Table 10-16 on page 10-52 and Table 10-17 on page 10-54 detail the DCN
parameters for the DCN example 6 configuration.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-51
Figure 10-13
DCN example 6 - Single OM4K with GRE tunnels to remote OME6130 NEs in SNCP ring with OM4K
OMEA R1
IP
IP and R2
OSI DCN
OSI area OSI (4K/3K)
e.g. 0002
OM
4K/3K
OME F
61x0
A OM
Target 4K/3K
node D
OM
OME 4K/3K
61x0 E
B
OME
61x0
C
Legend
= iIS-IS/OSI/LAPD/DCC
= iIS-IS/IP/PPP/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME 61x0 = OME6110 or OME6130
Figure 10-14
DCN example 6 - IP logical view
OMEA
Legend
= IP connection
= OSPF routing between NEs
= iISIS routing between NEs
= Static/Default routing
Table 10-16
DCN example 6 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 192.168.1.254 192.168.1.254 192.168.1.254
Netmask /24 /24 /24
Default gateway - - -
Router ID:
IP address 47.1.3.65 47.1.3.66 47.1.3.67
Netmask /32 /32 /32
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-53
4 Set up DCC
STM1/4-x-1:
Protocol LAPD PPP PPP
MTU 512 1518 1518
iISIS Enable Enable Enable
STM1/4-x-2
Protocol PPP PPP LAPD
MTU 1518 1518 512
iISIS Enable Enable Enable
Table 10-17
DCN example 6 - Router, OMEA, and OM4K DCN provisioning details
Interface: - - - - -
IP address 47.1.1.1 - - - -
Netmask /29 - - - -
Interface: - - - - -
IP address - - - - 47.1.1.5
Netmask - - - - /29
Default gateway - - - - 47.1.1.1
Circuitless IP/ NE-IP:
IP address 47.1.1.128 47.1.1.129 - - -
Netmask /32 /32 - - -
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-55
DCN example 7 - Using dual OM4000 GNEs with GRE tunnels through
OM4000 network to reach remote OME6130 network elements in SNCP
ring with generic SDH network elements.
In this example (see Figure 10-15 on page 10-57 and Figure 10-16 on page
10-58), similar to previous configuration, but with multiple gateway locations
with GNEs and routers to maximize the resilience of this solution.
The ABR on which the IP over OSI GRE tunnels terminate can only be a Cisco
router that supports ISO CLNS, with an IOS which has the “IP over CLNS
tunnel (CTunnel)” using GRE encapsulation feature. Some older versions of
IOS support IP over OSI tunnels using Cisco proprietary encapsulation which
is not suitable in this application.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-57
Figure 10-15
DCN example 7 - Dual OM4K GNEs with GRE tunnels to remote OME6130 NEs in SNCP ring with
OM4K
OMEA
R1
R2
OM IP
4K/3K
F
OSI (4K/3K)
OME R3
61x0 OM
A 4K/3K
Target D OM
node 4K/3K
OM OM G
OME 4K/3K 4K/3K IP and
61x0 E H
OSI DCN
B
OME
61x0
C
Legend
= iIS-IS/OSI/LAPD/DCC
= iIS-IS/IP/PPP/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME 61x0 = OME6110 or OME6130
Figure 10-16
DCN example 7 - IP logical view
OMEA
Legend
= IP connection
= OSPF routing between NEs
= iISIS routing between NEs
= Static/Default routing
Table 10-18
DCN example 7 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 192.168.1.254 192.168.1.254 192.168.1.254
Netmask /24 /24 /24
Default gateway - - -
Router ID:
IP address 47.1.3.65 47.1.3.66 47.1.3.67
Netmask /32 /32 /32
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-59
4 Set up DCC
STM1/4-x-1:
Protocol LAPD PPP PPP
MTU 512 1518 1518
iISIS Enable Enable Enable
STM1/4-x-2
Protocol PPP PPP LAPD
MTU 1518 1518 512
iISIS Enable Enable Enable
Table 10-19
DCN example 7 - Router, OMEA, and OM4K DCN provisioning details
Interface: - - - - - -
IP address 47.1.1.1 - - - - -
Netmask /29 - - - - -
Interface: - - - - - -
IP address - - - - - 47.1.1.5
Netmask - - - - - /29
Default gateway - - - - - 47.1.1.1
Circuitless IP/ NE-IP:
IP address 47.1.1.128 47.1.1.129 47.1.1.130 - - -
Netmask /32 /32 /32 - - -
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-61
DCN example 8 - Using single OME6130 GNE with iISIS through OM4000
network to reach remote OME6130 network elements in SNCP/UPSR rings
with OM4000 network elements. Proxy ARP used at OME6130 GNE for
access to remote OME6130 NEs.
In this example (see Figure 10-17 on page 10-63 and Figure 10-18 on page
10-64), OME6130 network elements use iISIS routing to establish
communication to the remote OME6130 through the OM4K network.
Connection between OME6130 and OM4K is over SDH with DCC enabled,
with iISIS between various sub-tending OME6130 NEs in SNCP/UPSR rings
to provide resilience without the need for additional OME6130 GNEs. The
auto-tunnel interface (AGRE) should have a static route provisioned within the
subnet of the OME6130 network elements. The remote OME6130 NEs are
provisioned as proxy ARP neighbours at the OME6130 GNE.
An OSI enabled router can be used for the OSI communication for the OM4K
to the DCN network.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-63
Figure 10-17
DCN example 8 - Single OME6130 GNE with iISIS routing in SNCP/UPSR rings with OM4K
OMEA R1
IP
IP and R2 R3
OSI DCN
OME OME
61x0 61x0
D E
Legend
= iIS-IS/OSI/LAPD/DCC
= iIS-IS/IP/PPP/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME 61x0 = OME6110 or OME6130
Figure 10-18
DCN example 8 - IP logical view
Legend
= IP connection
= Static/Default routing
Table 10-20
DCN example 8 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 192.168.1.254 192.168.1.254 192.168.1.254
Netmask /24 /24 /24
Default gateway - - -
Router ID:
IP address 47.1.3.65 47.1.3.66 47.1.3.67
Netmask /32 /32 /32
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-65
4 Set up DCC
STM1/4-x-1:
Protocol LAPD PPP PPP
MTU 512 1518 1518
iISIS Enable Enable Enable
STM1/4-x-2
Protocol PPP PPP LAPD
MTU 1518 1518 512
iISIS Enable Enable Enable
Table 10-21
DCN example 8 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 192.168.1.254 192.168.1.254 47.1.3.64
Netmask /24 /24 /29
Default gateway - - -
Router ID:
IP address 47.1.3.68 47.1.3.69 47.1.3.70
Netmask /32 /32 /32
3 Set up DCC
STM1/4-x-1:
Protocol LAPD PPP LAPD
MTU 512 1518 512
iISIS Enable Enable Enable
STM1/4-x-2
Protocol PPP LAPD -
MTU 1518 512 -
iISIS Enable Enable -
Note: The OME6130 F (GNE) is being managed via the Eth0 IP address.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-67
Table 10-22
DCN example 8 - OM4K DCN provisioning details
2 Set up DCC
Table 10-23
DCN example 8 - Router and OMEA DCN provisioning details
Interface: - - - -
IP address 47.1.1.1 - - -
Netmask /29 - - -
Interface: - Eth0: VLAN1 Eth0: VLAN1 -
IP address - 47.1.3.72 47.1.3.73 47.1.1.5
Netmask - /28 /28 /29
Default gateway - - - 47.1.1.1
Circuitless IP/ NE-IP:
IP address 47.1.1.128 47.1.1.129 47.1.1.130 -
Netmask /32 /32 /32 -
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-69
The remote OME6130 NEs are provisioned as proxy ARP neighbours at the
OME6500 GNE.
DCN provisioning details
Table 10-24 on page 10-71, Table 10-25 on page 10-72 and Table 10-26 on
page 10-74 detail the DCN parameters for the DCN example 9 configuration.
Figure 10-19
DCN example 9 - Single OME6500 GNE with iISIS to remote OME6130 NEs
OMEA R1 IP
IP and R2
OSI DCN
OSI area
e.g. 0002
IP
OME
6500
OME H
61x0
A OME
Target 6500
node F
OME
OME MS DCC 6500
61x0 G
B
OME
61x0
C
Legend
= iIS-IS/OSI/LAPD/DCC
= iIS-IS/IP/PPP/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME61x0 = OME6110 or OME6130
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-71
Figure 10-20
DCN example 9 - IP logical view
OMEA
Legend
= IP connection
= Static/Default routing
Table 10-24
DCN example 9 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 192.168.1.254 192.168.1.254 192.168.1.254
Netmask /24 /24 /24
Default gateway - - -
Router ID:
IP address 47.1.3.65 47.1.3.66 47.1.3.67
Netmask /32 /32 /32
4 Set up DCC
STM1/4-x-1:
Protocol PPP PPP PPP
MTU 1518 1518 1518
iISIS Enable Enable Enable
STM1/4-x-2
Protocol PPP PPP PPP
MTU 1518 1518 1518
iISIS Enable Enable Enable
Table 10-25
DCN example 9 - OM6500 DCN provisioning details
Interface: COLANX - -
IP address 47.1.3.11 - -
Netmask /29 - -
Interface: - - -
IP address - - -
Netmask - - -
Default gateway - - -
Circuitless IP/ NE-IP:
IP address 47.1.3.92 47.1.3.93 47.1.1.94
Netmask /32 /32 /32
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-73
4 Set up MAA
Table 10-26
DCN example 9 - Router and OMEA DCN provisioning details
Interface: - - -
IP address 47.1.1.1 47.1.3.1 -
Netmask /29 /29 -
Interface: - - -
IP address - - 47.1.1.5
Netmask - - /29
Default gateway - - 47.1.1.1
Circuitless IP/ NE-IP:
IP address 47.1.1.128 47.1.1.129 -
Netmask /32 /32 -
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-75
DCN example 10 - Using single OME6500 GNE with iISIS to reach remote
OME6130 network elements in a SNCP ring configuration with generic
SDH equipment.
In this example (see Figure 10-21 on page 10-76, Figure 10-22 on page 10-77
and Figure 10-23 on page 10-78), a single OME6500 network element is used
as the GNE to establish communication between the external DCN and the
OME6130 within a SNCP ring with generic SDH equipment (such as OM4000
and TN-1C network elements).
The remote OME6130 NEs are provisioned as proxy ARP neighbours at the
OME6500 GNE.
DCN provisioning details
Table 10-27 on page 10-79 and Table 10-28 on page 10-80 detail the DCN
parameters for the DCN example 10 configuration.
Figure 10-21
DCN example 10 - Single OME6500 with iISIS to reach remote OME6130 NEs in SNCP with generic
SDH equipment
OSI and
OMEA R1 IP DCN
IP
R2
IP
OSI area
e.g. 0002
OME
OME 6500
61x0 H
A
XXX
F
OME
OME RS DCC 6500
61x0 G
B
XXX
C
Legend
= iIS-IS/OSI/LAPD/DCC
= iIS-IS/IP/PPP/DCC
= OSPF/IP/PPP/DCC
= IP/GRE/OSI
= OSI
= Static IP route/IP/PPP/DCC
OME61x0 = OME6110 or OME6130
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-77
Figure 10-22
DCN example 10 - IP logical view
OMEA
Legend
= IP connection
= OSPF routing between NEs/Router
= iISIS routing between NEs
= Static/Default routing
Figure 10-23
DCN example 10 - iIS-IS / IS-IS logical view
OMEA R1
OSI
OSI and R2
IP DCN
OSI area
e.g. 0002
OME
6500
H
OME
61x0
RS DCC A
XXX
F
OME
6500
OME G
61x0
B
XXX
C
Legend
= OSI connection
= iISIS/ISIS routing between NEs
OME61x0 = OME6110 or OME6130
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-79
Table 10-27
DCN example 10 - OME6130, OME6500, and OSI NE DCN provisioning details
2 Set up IP routing
Static routing 1
Address 0.0.0.0 0.0.0.0
Netmask /0 /0
Next hop IP address 0.0.0.0 0.0.0.0
Next hop interface AGRE AGRE
Advertise No No
Table 10-28
DCN example 10 - Router and OMEA DCN provisioning details
Interface: -
IP address 47.1.1.1 47.1.3.1 -
Netmask /29 /29 -
Interface: - - -
IP address - - 47.1.1.5
Netmask - - /29
Default gateway - - 47.1.1.1
Circuitless IP/ NE-IP:
IP address 47.1.1.128 47.1.1.129 -
Netmask /32 /32 -
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-81
Dual OM4000 network elements are connected to the external DCN via an OSI
only enabled port and act as the GNEs for the other OM4000 and legacy OSI
network elements.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-83
Figure 10-24
DCN example 11 - VC12 management channels to remote OME6130 NEs in SNCP ring with OM4K
and legacy OSI network elements
OMEA R1 IP
R3 R2
IP and
OSI DCN
OSI area OSI (4K)
e.g. 0002
OM
4000
OME G
61x0 OM
A 4000
OM H
4000
F
OME
61x0
B MS DCC
XXX
XXX E
D
OME
61x0
C
Legend
= iIS-IS/OSI/LAPD/DCC
= iIS-IS/IP/PPP/DCC
= OSPF/IP/PPP/DCC
= OSPF/IP/PPP/VC12 MGMT
= OSPF/IP/PPP/E1 MGMT
= IP/GRE/OSI
= OSI
= Transparent DCC (Overhead Tunnel)
= Static IP route/IP/PPP/DCC
OME 61x0 = OME6110 or OME6130
Figure 10-25
DCN example 11 - IP logical view
Legend
= IP connection
= OSPF routing between NEs
Table 10-29
DCN example 11 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 192.168.1.254 192.168.1.254 192.168.1.254
Netmask /24 /24 /24
Default gateway - - -
Router ID:
IP address 47.1.3.65 47.1.3.66 47.1.3.67
Netmask /32 /32 /32
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-85
MGMT-1:
Type VC12 VC12 VC12
MTU 1500 1500 1500
Layer 2 Protocol PPP, HDLC Framing PPP, HDLC Framing PPP, HDLC Framing
OSPF Enable Enable Enable
OSPF area 0.0.0.1 0.0.0.1 0.0.0.1
MGMT-2
Type VC12 VC12 VC12
MTU 1500 1500 1500
Layer 2 Protocol PPP, HDLC Framing PPP, HDLC Framing PPP, HDLC Framing
OSPF Enable Enable Enable
OSPF area 0.0.0.1 0.0.0.1 0.0.0.1
Table 10-30
DCN example 11 - OSI NE and OM4000 DCN provisioning details
Interface: - - - - -
IP address - - - - -
Netmask - - - - -
Interface: - - - - -
IP address - - - - -
Netmask - - - - -
Default gateway - - - - -
Circuitless IP/ NE-IP:
IP address - - - - -
Netmask - - - - -
2 Set up IP routing
4 E1 Connection
Table 10-31
DCN example 11 - Router and OMEA DCN provisioning details
IInterface:
IP address 47.1.1.1 47.1.3.1 47.1.3.17 47.1.1.5
Netmask /29 /29 /28 /29
Default gateway - - - 47.1.1.1
Circuitless IP/ loopback:
IP address 47.1.1.128 47.1.1.129 47.1.1.130
Netmask /32 /32 /32
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-87
The OM4000 network element is connected to the external DCN via two paths.
An OSI connection to the OSI router, and an E1 connection to the IP router.
The OM4000 acts as the GNE for the legacy OSI network element.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-89
Figure 10-26
DCN example 12 - E1 and VC12 management channels to remote OME6130 NEs in SNCP ring with
OM4K and legacy OSI network elements
OMEA R1 IP
R2 R3
IP and
OSI DCN
OSPF area
0.0.0.1 OSI (4K)
OME
61x0
A
OM
MS DCC 4000
XXX D
C
OME
61x0
B
Legend
= iIS-IS/OSI/LAPD/DCC
= iIS-IS/IP/PPP/DCC
= OSPF/IP/PPP/DCC
= OSPF/IP/PPP/VC12 MGMT
= OSPF/IP/PPP/E1 MGMT
= IP/GRE/OSI
= OSI
= Transparent DCC (Overhead Tunnel)
= Static IP route/IP/PPP/DCC
OME 61x0 = OME6110 or OME6130
Figure 10-27
DCN example 12 - IP logical view
OMEA
Legend
= IP connection
= OSPF routing between NEs
= iISIS routing between NEs
= Static/Default routing
Table 10-32
DCN example 12 - OME6130 DCN provisioning details
LAN-1-6 port:
IP address 192.168.1.254 192.168.1.254
Netmask /24 /24
Default gateway - -
Router ID:
IP address 47.1.3.65 47.1.3.66
Netmask /32 /32
2 Set up IP routing
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-91
MGMT-1:
Type E1 VC12
MTU 1500 1500
Layer 2 Protocol Standard PPP, RFC 1661 PPP, HDLC Framing
Magic Number Enable Disable
OSPF Enable Enable
OSPF area 0.0.0.1 0.0.0.1
MGMT-2
Type E1 VC12
MTU 1500 1500
Layer 2 Protocol Standard PPP, RFC 1661 PPP, HDLC Framing
Magic Number Enable Disable
OSPF Enable Enable
OSPF area 0.0.0.1 0.0.0.1
Table 10-33
DCN example 12 - OSI NE and OM4000 DCN provisioning details
Parameters NE C OM4000 D
1 Set up IP address
Interface: - -
IP address - -
Netmask - -
Interface: - -
IP address - -
Netmask - -
Default gateway - -
Circuitless IP/ NE-IP:
IP address - -
Netmask - -
2 Set up IP routing
Parameters NE C OM4000 D
3 Set up DCC
4 E1 Connection
Table 10-34
DCN example 12 - Router and OMEA DCN provisioning details
IInterface:
IP address 47.1.1.1 47.1.3.1 47.1.3.17 47.1.1.5
Netmask /29 /29 /28 /29
Default gateway - - - 47.1.1.1
Circuitless IP/ loopback:
IP address 47.1.1.128 47.1.1.129 47.1.1.130
Netmask /32 /32 /32
2 Set up IP routing
3 Set up E1 interface
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-93
The next section of this information shows the bit significance of the dotted
decimal notation.
• 00000001 is represented by 1
• 00000010 is represented by 2
• 00000100 is represented by 4
• 00001000 is represented by 8
• 00010000 is represented by 16
• 00100000 is represented by 32
• 01000000 is represented by 64
• 10000000 is represented by 128
Example: 10010001
• 10000000 is represented by 128
• 00010000 is represented by 16
• 00000001 is represented by 1
• Total 145
An IP address contains a 32-bit address field and a 32-bit subnet mask. The
mask defines which part of the address is a network address and which is a
device address. The mask thus allows a router to decide whether the address of
the packet is destined for one of the subnets to which it is connected. For
example:
An address of 47.9.64.172 has a mask of 255.255.240.0; the mask is
AND’ed with the address:
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-95
The last 12 bits are available to the user to use as subnet address and device
address.
Note: This notation is conventional for CIDR addresses. However, the
method in which an IP address is configured can vary according to the
router where it is performed. For example, the IP address notation
196.0.16.0/20 can be used to configure a Cisco router, whereas Nortel
Networks routers require the full notation 196.0.16.0 with the subnetwork
mask 255.255.240.0. There is no substantial difference between these two
methods.
Circuitless IP interface
A circuitless IP interface is a virtual interface that exists in software only. The
special property of this interface is that it always exists and is therefore always
included in the routing tables. Ethernet and serial interfaces cease to exist if a
connector falls out, or if the device at the other end of the cable fails for any
reason. The interface then shuts down and is removed from the routing tables.
Note that circuitless IP is a Bay term; Cisco uses the term ‘loopback’ for these
interfaces. Having an interface that always exists within a router is very useful
for the following reasons:
1 If a tunnel is set up between two router interfaces and one of the interfaces
fails, the tunnel fails. However, when the tunnel is set up between two
circuitless IP interfaces, if the normal route fails, the tunnel is re-routed if
another route exists and does not fail.
2 If during a Telnet session on a router the interface to which the session is
connected goes down, then the session is lost. Another connection via the
IP address of an alternative interface must be made. If Telnet sessions are
set up to connect to the router using the circuitless IP interface, then loss
of one interface is not a problem, providing the router has at least one
working IP interface.
3 Other interfaces can be referenced to the circuitless IP interface. This is
known as an unnumbered interface. This applies only to point-to-point
interfaces (that is, not an Ethernet port). This reduces the number of IP
addresses needed.
Note: It is more difficult to find faults in a network with an unnumbered
link, and topologies from some network management systems are easier to
follow with unnumbered serial links. The use of unnumbered links is still
permissible where sufficient IP addressing space is not available.
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
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-97
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.
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.
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.
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.
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.
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.
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-99
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.
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.
The designated router on a LAN in a network running OSPF has a very high
processor utilization. It may be that some routers are unsuitable for this role
and so should be allocated a priority of 0. If it is not possible to have an area
connected directly to area 0, a virtual route may be used as in Figure 10-28
(dashed line).
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-101
Figure 10-28
OSPF areas
Area 1
Area 2
Area 0
(Backbone)
Area 3
Area 6
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.
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-29
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
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Appendix A: Data communications planning 10-103
routing protocols (for example, RIP). A static route should be assigned a high
preference and a default route a low one.
Default routes are a form of static routes in that they provide a catch-all for
destinations not contained in routing tables. In effect they provide a static
route to a large network rather than a specific IP address or subnetwork. In the
case of the subnetwork attached to a corporate network, the intermediate
router on the border has a default route to the corporate network advertised
into the subnetwork.
Figure 10-30 shows an example of the way that static routes and default
routes are used.
Figure 10-30
Default and static routes
Optical Multiservice Edge 6130 NT6Q92MA Rel 1.0 Iss 1 Standard September 2006
Nortel
This information is provided “as is”, and Nortel Networks does not
make or provide any warranty of any kind, expressed or implied,
including any implied warranties of merchantability,
non-infringement of third party intellectual property rights, and
fitness for a particular purpose. Except as expressly authorized in
writing by Nortel Networks, the holder is granted no rights to use
the information contained herein.
NT6Q92MA
Standard Rel 1.0 Issue 1
September 2006
Printed in Canada