151 Standard

323-4061-151

SDH TRANSMISSION

Data CommunicationsNetworksProvisioning Guide

Release 2 Standard January 1998

RESTRICTED DOCUMENT

FOR INTERNAL NORTEL USE ONLY.

Data Communications Networks Provisioning Guide

SDH TRANSMISSION

Data Communications NetworksProvisioning Guide

Document Number: 323-4061-151Document Status: StandardRelease Number: 2Date: January 1998

Copyright 1998 Northern Telecom

Printed in England

The copyright of this document is the property of Northern Telecom. Without the written consent of Northern Telecom, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall keep the information contained herein confidential and shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation and maintenance purposes only.

So far as Northern Telecom is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Northern Telecom can give no warranty or undertaking and make no representation as to their accuracy. In particular, Northern Telecom hereby expressly excludes liability for any form of consequential, indirect or special loss, and for loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

v

Publication historyJanuary 1998

Release 2 Standard

December 1997Release 2 Draft A

October 1997Release 1 Standard

August 1997Release 1 Draft C

August 1997Release 1 Draft B

June 1997Release 1 Draft A


iii

ContentsContents iiiAbout this document ixAudience ixAssociated documents ixTechnical support and information xTelecommunications terminal equipment approval x

General 1-1Overview 1-1Scope 1-2

Network elements 1-2Network and element controllers 1-3

Document structure 1-3

Bid support 2-1Estimation rules 2-1

Initial estimation 2-1Sales stage 2-2

Detailed design 3-1General 3-1SDH network analysis 3-1Initial SDH DCN definition 3-2Detailed SDH management domain definition 3-5

Small SDH networks 3-5Large SDH networks 3-6

Power supply type 3-8Location definition 3-8Generate component list 3-9Configuration 3-9Installation information 3-10

Key network components 4-1General definitions 4-1

DCN 4-1End system 4-1Intermediate system 4-1Subnetworks 4-1Lower layer interoperability 4-2End-to-end interoperability 4-2DCN main component types 4-2


iv Contents

SDH network elements 4-3Network and element controllers 4-4Routers 4-4Terminal servers 4-4High-speed modems 4-4LAN components 4-5Dial-up low-speed voice modems 4-5Component tables 4-5

Topologies 5-1Overview 5-1Basic DCN component connectivity 5-1

External SDH DCN 5-1Internal SDH DCN 5-2Balancing the internal and external DCN 5-2

IP and OSI protocol co-existence 5-3SDH management domain architecture 5-3

Large domains 5-3SDH management area 5-4SDH NE area 5-6Isolated SDH NEs 5-8SDH NE location 5-8Small domains 5-9

Narrowband access support 5-12Non-interoperability 5-12

Management and security 6-1Management strategy 6-1Remote access 6-2Security strategy 6-2

Passwords 6-3Firewalls 6-3Remote access 6-4

Dependability 7-1Design 7-1

Availability 7-1Reliability 7-1

Maintenance 7-1In-country spares 7-1Supplier maintenance agreements 7-2“Hot” spares 7-2Configuration backup 7-2

Protocols 8-1Addressing 8-1

Overview 8-1IP networks, subnetworks, and subnetwork masks 8-2

IP addressing examples 8-2Loopback interface 8-8Tunnel interface 8-9OSI protocol addressing 8-10

Example 9-1

323-4061-151 Release 2 Standard

Contents v

Overview 9-1Introduction 9-1SDH network analysis 9-1SDH management domain definition 9-4

DCN topology 9-4Addressing 9-9

Power supply type 9-13Location definition 9-13Generate components list 9-14Installation information 9-15

Installation guidelines 10-1Guidelines for DCN equipment installation 10-1

Vented top cover with cable entry 10-2Castors 10-2Fan units 10-2Cantilever shelf 10-2Cable tray 10-3Doors 10-3Power distribution panels 10-3

Web sites 10-6Cisco 10-6Fourthtrack/Market Vision MicroMux 10-7Multi-Tech Systems 10-7Bay Networks 10-7

Useful information sources 11-1Web sites 11-1

Appendix A: SDN DCN deployment engineering limits 12-1Engineering limits 12-1

Appendix B: Protocol reference information 13-1Protocol interoperability 13-1

Overview 13-1Internet protocols 13-1IP addressing 13-2OSI protocols 13-2OSI protocol addressing 13-4

Appendix C: Tables 14-1

Appendix D: Router configuration diagrams and templates 15-1Topology diagrams 15-3Example 15-10

Addressing information 15-10

Appendix E: Bay Networks hubs 16-1

List of terms 17-1

References 18-1Standard texts 18-1


vi Contents

Nortel document references 18-1ITU recommendations 18-1ISO/IEC specifications 18-2Internet RFCs 18-3Regulatory requirements 18-3Cisco documentation 18-4

Index 19-1

List of figuresFigure 1-1 The scope of the SDH DCN design 1-2Figure 4-1 Indirect NE connections to DCN for communications with their

management systems 4-3Figure 5-1 Basic components of the external DCN 5-1Figure 5-2 Basic structures of the internal DCN 5-2Figure 5-3 Maximum size domain 5-4Figure 5-4 Example of an SDH management area 5-5Figure 5-5 Example of a large SDH management area 5-6Figure 5-6 Example of an SDH NE area 5-7Figure 5-7 Example of an SDH NE area with SDH radio systems 5-8Figure 5-8 Example of an SDH NE location with a router present 5-9Figure 5-9 Minimal SDH DCN 5-10Figure 5-10 Routers in a small domain 5-11Figure 5-11 Narrowband access multiplexer and the ATU 5-12Figure 5-12 Use of bridges in SDH networks 5-13Figure 6-1 Access using Telnet/TCP/IP over a LAN port from a UNIX

workstation 6-2Figure 8-1 Two routers within an SDH NE area 8-3Figure 8-2 Allocation of IP addresses 8-5Figure 8-3 Routers within a management area 8-5Figure 8-4 Allocation of IP addresses in a management location 8-8Figure 8-5 Tunnelling 8-9Figure 8-6 Two routers within an SDH NE area 8-15Figure 8-7 Two routers within an SDH NE area 8-16Figure 9-1 Network example 9-3Figure 9-2 Management domain 9-4Figure 9-3 SDH management area 9-5Figure 9-4 SDH NE area one 9-6Figure 9-5 SDH NE area three 9-7Figure 9-6 SDH NE area four 9-8Figure 9-7 System illustrating connectivity at location 9-13Figure 9-8 Generating a components list 9-14Figure 13-1 Domain/area structure 13-5Figure 13-2 OSI address structure as defined in ITU-T X.213 13-6Figure 15-1 Topology 1: Small network - point to point 2501/2505/2507s 15-3Figure 15-2 Topology 2: Small network - route IP, bridge OSI 15-4Figure 15-3 Topology 3: Small network - ring of 2501/2505/2507s 15-5Figure 15-4 Topology 4: Small network - ring of 2501/2505/2507s 15-5Figure 15-5 Topology 5: Large network - one 2501/2505/2507 in an NE area

15-6Figure 15-6 Topology 6: Three 2501/2505/2507s in an NE area 15-6Figure 15-7 Topology 7: Large network - management area with 1 site and 1-5

NE areas 15-7Figure 15-8 Topology 8: Large network - management area with 1 site and


Contents vii

6-10 NE areas 15-7Figure 15-9 Topology 9: Large network - management area with 1 site and

11-20 NE areas 15-8Figure 15-10 Topology 10: Large network - management area with 2 sites and

1-5 NE areas 15-8Figure 15-11 Topology 11: Large network - management area with 2 sites and

6-10 NE 15-9Figure 15-12 Topology 12: Large network - management area with 2 sites and

11-20 NE areas 15-9Figure 15-13 Example SDH NE area with two routers 15-10

List of tablesTable 8-1 Addresses that can be allocated 8-6Table 9-1 Needed DCN components 9-15Table 9-2 Example location and connectivity table 9-16Table 9-3 Example interface/configuration for area 1 9-17Table 9-4 Example interface/configuration for area 2 9-17Table 9-5 Example of addressing, area 1 9-18Table 10-1 Standard items supplied with equipment 10-4Table 12-1 Management sites 12-1Table 12-2 Large system 12-1Table 12-3 Small systems 12-2Table 12-4 LANs 12-2Table 12-5 TN-16X CNET 12-3Table 12-6 SDH DCC Bandwidth and limitations 12-3Table 12-7 TN-4X 12-3Table 12-8 TN-16X with low-order MUXs 12-4Table 12-9 TN-16X 12-4Table 12-10 TN-16X with low-order MUXs 12-4Table 12-11 Bandwidth requirements 12-5Table 12-12 DCC 12-5Table 12-13 EC-1 span of control 12-5Table 12-14 EC-4X span of control 12-5Table 12-15 EC-16X, EC-16X 4F, and EC-64X span of control 12-6Table 14-1 NEs and respective ECs that may be connected to SDH DCN

ports supporting OSI protocols 14-1Table 14-2 Main element controller types (OSI system) 14-2Table 14-3 Routers forming the main components of the SDH DCN 14-3Table 14-4 Components used to extend or construct LANs (Ethernet or

CNET) 14-4Table 14-5 Multi-Tech MT2834BL modem approvals with part numbers 14-5Table 14-6 SDH DCN components list, Release 2 14-7Table 14-7 Rack mounting kits and options available 14-11Table 14-8 Data country codes 14-13

List of proceduresProcedure 3-1 Pre-bid information collection and SDH network analysis 3-1Procedure 3-2 Pre-bid engineering 3-3Procedure 3-3 Post-contract re-engineering 3-5Procedure 3-4 Detailed DCN topology for small SDH networks 3-6Procedure 3-5 Detailed DCN topology for large SDH networks 3-6Procedure 3-6 Detailed DCN topology for the management area in large SDH

networks 3-7Procedure 8-1 Designing addressing scheme for large SDH networks 8-1


viii Contents

Procedure 8-2 Using ISO DCC format 8-12


ix

ns:

About this documentThis document supersedes the existing NTP DCN in SDH Systems Provisioning Guide, NTP 32H SC00 445 VEA, Issue 2 (May 1996) produced by Systems Engineering.

AudienceThe audience for this document includes the following Nortel organizatio

• Sales

• Marketing

• Product Line Management

• Customer Systems Engineering

• Customer Network Solutions

• Customer Technical Support

Associated documentsThe following documents are associated with this document:

• the SDN DCN Commissioning Guide, NTP 323-4061-210

• the Requirements for Interoperability within the SDH DCN Code 32DSS00001AND


x

ers.

d if a

pport

iated

.

12 here

ns

ect

Technical support and informationNortel provides a comprehensive technical support service for its customContact the Nortel Service Desk 8:30 am to 5 pm, Monday to Friday (UKlocal time), at the following FAX or telephone numbers:

United KingdomFreephone: 0800 626 881Telephone: 0181 361 4693FAX: 0181 945 3456

InternationalTelephone: +44 181 361 4693FAX: +44 181 945 3456

Access to Customer Service Desk 24-hour help line assistance is providesuitable Support Agreement is in place.

To discuss Technical Support services, please contact the Technical SuHotline on 0181 945 3525.

Telecommunications terminal equipment approvalThe following DCN components are approved for connection to the assocPublic Network interfaces:

• Cisco 2501, 2505, 2507, 2509, and 2514 are approved to I-CTR2 forconnection of X21 interfaces in countries where I-CTR2 is acceptable

• Fourthtrack/Market Vision SP-1RA G703 adaptor is approved to CTRfor connection to 2M unstructured 120-ohm leased lines in countries wCTR12 is acceptable.

Note: CTR12 is not relevant to 75-ohm leased lines.

• Multi-Tech Systems MT2834BLK modem is BABT-approved for connection to British Telecommunications or Kingston CommunicatioPublic Switched Telephone Network (PSTN).

Note: Other versions of this modem are available with approval to connto the PSTN of other countries. The network designer must confirm connection legality of a specific modem to a specific PSTN.

end of chapter


1-1

1

H nt

nt

General 1-Overview

This document provides sufficient material to allow Systems Engineeringgroups to design customer-specific SDH DCNs.

The SDH DCN provides management data communications between SDNetwork Elements (NEs) and their management systems. The DCN alsointerconnects the various physical platforms that support the managemesystems.

International Telecommunications Union Telecommunications Standardization Section (ITU-T) formally defines the DCN in recommendation M.3010 Principles for a Telecommunications ManagemeNetwork (TMN).

The DCN consists of an external part and an internal part.


1-2 General

by a the ing

Figure 1-1The scope of the SDH DCN design

The external part consists of local area networks (LANs) interconnected router network and associated components. The internal part consists ofSDH NEs themselves and their embedded communications links or datacommunications channels (DCCs). Consider both parts when implementan overall SDH DCN. ITU-T recommendation G.784 SDH Management defines the internal SDH DCN.

ScopeThis section indicates the type of Nortel-supplied equipment that the SDHDCN can be used to support.

Network elementsThe SDH DCN design is appropriate for use with the following Nortel equipment at the stated and subsequent release:

• TN-1P Release 2

• TN-1C Release 1

• TN-1X Release 6 (including TN-1X/S)

• Asynchronous Telemetry Unit (ATU) Release 1

External

4X 1X 1C 1PHCross

ElementControllers

Router

LAN

WAN

LAN

DCN

Router

Network Controllers Element Controllers

16X

16X

16X

Connect

1X

Internal DCN

SDH NEs


General 1-3

1

.

H

• TN-4XE Release 1

• TN-4X Release 2.4

• TN-16L Release 4

• TN-16X Release 5

• TN-40X/1 4/1 cross connect Release 4

• TN16 4F Release 1

• TN-X/40 SDH Radio

• Tellabs 532E 1/0 cross connect

• Primary Digital Multiplexer-Enhanced (PDMX-E)

All subsequent releases have the same or better levels of interoperability

Network and element controllersThe SDH DCN design is appropriate for use with the following Nortel management systems:

• Network Resource Manager (NRM). The equipment that the NRM manages is dependent on the NRM release.

• EC-1 which manages:

— TN-1C

— TN-1P

— TN-1X

— TN-1X/S

— TN-4XE

• EC-4X which manages:

— TN-4X

• EC-1.5L which manages:

— TN-16L

• MV-36 which manages:

— TN-40X 4/1

• EC-16X Operations Controller (OPC) which manages:

— TN-16X

• EC-16X 4F OPC which manages:

— TN-16 4F

• TN-X/40 OPC which manages:

— TN-X/40

Document structureThis document consists of two major parts. The first part provides information on the process associated with Nortel defining a customer SD


1-4 General

ter/

nd

s to

er

in

DCN. The second part provides SDH DCN tutorial information, which is reference material for the process-oriented part.

The detailed structure for the rest of the document is as follows:

• Process-oriented information:

— “Bid support”: Simple rules allowing quick estimation of the DCN order of magnitude needed at the sales or early bid stage of a customer-specific project.

— “Detailed Design”: Detailed rules to generate a network diagram, component list, and configuration information.

– Analyze SDH Network and identify management locations.

– SDH Management Domain: Define area architecture and DCNtopology.

– Choose power supply type: AC (100-260 V) or DC (-48 V).

– Select DCN components on a site-by-site basis.

– Generate list of actual DCN components, including spares.

– Define equipment (SDH NE and DCN) configuration and regisallocate specific IP/OSI addresses.

– Ensure all information required for installation is available.

• Tutorial information:

— “Key Network Components”: Definitions of the key network components

— “Topologies”: Detailed network structures:

– Component connection

– Transmission Control Protocol/Internet Protocol (TCP/IP) and Open Systems Interconnect (OSI) protocol co-existence

– Network set-up to allow future upgrade (in terms of capacity afunctionality)

– What to do when SDH NEs cannot interwork

— “Management”: How to provide DCN management and what needbe managed; remote access and security

— “Dependability”: Issues associated with providing a DCN the customcan depend on

— “Protocols”: Key protocols involved and their key parameters withtheir meanings

– Addressing scheme, TCP/IP, and OSI address allocation and registration

— “Example”: Illustrates how processes and tutorial information giventhis document should be applied


General 1-5

1et

,

nd

H

— “Installation”: Guidelines for DCN equipment installation and Internsites

— “Useful information sources”: Internet World Wide Web (WWW) sites

— Appendices: “Engineering limits”, “Protocol reference information”“Tables” and “Router Configurations and Templates”

For information on how to configure the SDH DCN equipment, see the SDH DCN Commissioning Guide NTP 323-4061-210.

Additional information about DCN and the DCN design group may be fouon the DCN Web page (http://47.217.33.140/DCN/).

When the available material is not adequate, consult members of the SDDCN design team.

end of chapter


2-12

f the

N

ting ill

an

Bid support 2-Estimation rules

This section contains SDH DCN cost estimation information. Use these estimates prior to the DCN final design.

Initial estimation

Historically, DCN costs have been consistently underestimated at the bidstage. An initial estimation of the DCN cost for a given bid, pending completion of a detailed DCN design, should be between 1% and 10% oSDH transmission equipment costs. The cost will vary within this range according to the complexity and size of the SDH traffic network.

Therefore, for a $10 million cost bid, the additional cost to Nortel for the DCN will be between $100K and $1 million. For example, the largest DCprovided to date has cost $9 million.

During this stage of a project, it is not possible to provide rules for estimathe true cost. All that can be given is the following list of risk factors that winfluence the total cost:

• lack of data communications interoperability between SDH NEs

• SDH network size of more than 150 SDH NEs

• SDH network size of more than 750 SDH NEs

• SDH network topology containing:

— Add-Drop Multiplexer (ADM) chains rather than rings

— high-capacity SDH NE type

— network segments that are physically disjoint

— non-Nortel-supplied SDH NEs

• multiple management locations

• separation of IP and OSI protocol required

ATTENTIONFailure to estimate the DCN correctly at the bid stage typically leads to under-performing network, customer dissatisfaction, and additional unbudgeted rectification costs.


2-2 Bid support

ve

r to

nt’s

he

he

mes

• high availability with limited single points of failure, provided by duplicating locations, paths, and equipment

• protection in excess of single point of failure avoidance

• larger than normal spares holding required due to:

— large geographical separation of the DCN components

— delays with importing equipment into a country

• connection to a customer general purpose Intranet

• DCN includes provision of a customer general-purpose Intranet

The more of the above factors that apply, the more the SDH DCN will mofrom 1% to 10%.

Sales stageBefore placing the final bid, carry out a design of the SDH network. RefeDetailed design on page 3-1. This design activity normally consists of trafficanalysis, SDH traffic network topology planning, and placement of management centers.

Additionally, the network design activity includes the SDH DCN topologyand equipment list. Carry out this activity in accordance with this documeguidelines (refer to Topologies on page 5-1and Appendix C: Tables on page 14-1). The application of the SDH DCN spares policy normally adds extraitems to the equipment list.

Once the first draft of the SDH DCN equipment list is available, provide tinformation to the Nortel Purchasing function. This allows for the timely delivery of components from the SDH DCN equipment suppliers.

When these activities are complete, a high level of confidence exists in tcost to Nortel of the SDH DCN, associated with a given bid.

The detailed design of the equipment configuration and addressing schefollows after the contract is awarded.

end of chapter


3-1

3ed

at ion

nal

H

Detailed design 3-General

This section contains a definition of the process required to do the detaildesign of a customer SDH DCN.

Extensive use is made of references to other sections of the document thdescribe the SDH DCN in more detail. Therefore, anyone using this sectshould be familiar with the material in those sections.

High network availability using redundancy is optional and should be included only where there is a clear requirement which justifies the additioDCN costs.

SDH network analysisThe first activity in the DCN detailed design process is to analyze the SDnetwork and collect information as outlined in Procedure 3-1.

Procedure 3-1Pre-bid information collection and SDH network analysis

Step Action

1 From the SDH traffic network, identify quantity, interfaces, and version for each NE type.

2 Collect topology and list of locations for the SDH traffic network.

3 Determine the power supply available at each site (AC or DC).

4 Project the SDH network expansion to ensure that the design can evolve to meet the future requirement.

5 Identify any pre-existing customer DCN equipment.

6 Determine the required location(s) for the management systems.

—continued—


3-2 Detailed design

but

s CN

ld ected

nt

of

nd

ed to s.

Procedure 3-1 Pre-bid information collection and SDH network analysis

Step Action

7 Establish the level of network availability required:

a. for the data communications path between the ECs and their SDH NEs (single path or multiple path for resilience).

b. for the element management systems, using replication (non, single stand-by platform, or total duplication of platforms at multiple sites).

c. for the network management systems, using replication (non, duplication, or federation).

—end—

SDH network analysis information will change during the design process,it should be maintained as accurately as possible.

Initial SDH DCN definitionUsing the SDH network analysis information gathered (as outlined in Procedure 3-1), the structure of the SDH management domain can be proposed.

The approach to the DCN depends on the number of SDH NEs. Networkwith more than 150 NEs are large and other networks are small (from a Dperspective).

The following steps provide a DCN topology or network diagram. It shoualso show which sites need LANs and what equipment needs to be connto the LAN.

Refer to Chapter 5 (“Topologies”) and Appendix A (“SDH DCN deploymeengineering limits”) of this document, which cover network structures andengineering limits, respectively.

The main objective of the pre-bid engineering stage is to quantify the listDCN components required.

This is accomplished by first designing the internal DCN (SDH NE DCC aSDH NE LAN links) and determining the quantity and placement of the management systems. The external DCN (routers, etc.) can then be addprovide connectivity between the management systems and the SDH NE


Detailed design 3-3

3

Procedure 3-2Pre-bid engineering

Step Action

1 Determine the number of SDH NE element controllers (ECs) required, in line with the engineering limits in Appendix A of this document.

a. For low capacity (STM-4 and STM-1) SDH NEs divide the number of NEs by the span of control of the EC for each NE type.

b. For high capacity (STM-64 and STM-16) SDH NEs divide the number of NEs by the span of control of the OPC for each NE type.

Note: This initial OPC figure may be increased by the DCN design.

2 Determine the number of network level management platforms, depending on the level of availability, numbers of element controllers, and NEs.

3 Determine the requirement for network level management data communications access.

4 Form the SDH NEs (including ATUs) that support OSI protocols into groups, in line with the engineering limits in Appendix A of this document. These groups form the basis of OSI Level-1 routing areas.

Note: The key limit is the number of NEs per OSI Level-1 routing area.

An NE group may contain one or more high capacity rings or line systems.

Note: More than one OPC span of control or high capacity NE type may be present as part of the group.

An NE group may contain one or more of the following:

a. high capacity SDH NEs

b. low capacity SDH NEs connected via DCC or LAN links to the high capacity NEs.

c. Other devices such as routers (IS), OPCs (ES), and ATU (ES).

Note: The total number of systems in the NE group must not exceed the values defined by the engineering limits in Appendix A of this document.

5 The numbers of low capacity SDH NEs could exceed the engineering limits for a group including the high capacity SDH NEs. Then separate groups will be needed for the backbone high capacity SDH NEs and low capacity SDH NEs.

6 SDH NEs that do not support OSI protocols should be connected to the IP DCN. This may involve using external DCN equipment such as a terminal server for NEs with no IP Ethernet port.

—continued—


3-4 Detailed design

Procedure 3-2 Pre-bid engineering (continued)

Step Action

7 Position the management systems.

All management systems should be connected to an IP DCN.

Group the management systems in order to minimize the external DCN equipment.

The main components of the management system have the following further considerations:

a. Network level management systems can be placed anywhere that can be accessed using the IP DCN.

b. Low capacity ECs may be located in an OSI level-1 routing area dedicated to management systems or in an SDH NE OSI level-1 routing area.

c. High capacity ECs (OPC) must be located in the same OSI level-1 routing area as their SDH NEs.

Management systems and locations may be duplicated to increase availability.

8 Perform the detailed DCN design in accordance with detailed DCN topology design procedures for either:

a. small SDH DCNs (see Procedure 3-4) or

b. large SDH DCNs, including separate SDH NE and management areas (see Procedure 3-5 and 3-6).

9 Ensure that all SDH NEs have a data communications path to their respective ECs. External DCN equipment may be added or paths may be duplicated to increase availability.

The engineering limits define the rules for these paths (DCC, LAN, CNET, and WAN).

First priority should be to connect SDH NEs using the DCC. LAN/CNETs and DCN equipment (WAN) may be used when DCC paths are not available or their capacity is exhausted.

10 Select the DC- or AC-powered variants of DCN equipment for each site.

If power information is not available, it can be assumed that management sites with workstations are AC powered and all other NE and OPC sites providing -48V DC power.

11 Identify pre-existing customer DCN equipment, bandwidth, and interfaces available.

This equipment can be used as part of the SDH DCN if it has the same functionality as the Nortel-supplied DCN equipment. Ensure that guaranteed bandwidth available meets the engineering limits defined in Appendix A of this document.

12 Select the rack mounting equipment for each site.

13 Produce list of all DCN equipment.

—end—


Detailed design 3-5

3

f the

ture

s.

The object of the post-contract re-engineering is to add all the aspects odesign that do not add to the list of DCN components.

Procedure 3-3Post-contract re-engineering

Step Action

1 Identify any pre-existing customer addressing scheme.

2 Obtain an IP address range for the SDH management domain.

3 Obtain an OSI address range for the SDH management domain.

For more information on addressing, see Chapter 8 (“Protocols”) of this document.

4 Allocate an IP network address and subnetwork mask for each IP subnetwork.

5 Give each host an IP host address.

6 Allocate an OSI area address for each separate OSI Level-1 routing area.

7 Identify the configuration templates needed for all the routers.

From Appendix D of this document, first select the most appropriate topologies and then select the relevant templates.

8 Combine the router configuration templates, addresses, and security information to produce actual router configurations for all routers.

9 Generate a table of IP addresses, OSI addresses, Serial/LAN port on/off status, and neighboring systems for all routers.

10 Generate a table of OSI addresses, DCC/LAN port on/off status, DCC mode (RSOH/MSOH usage,) and neighboring systems for all SDH NEs.

11 Establish the period of time during which the DCN has to be installed.

—end—

Detailed SDH management domain definitionSmall SDH networks

If there are less than 150 SDH NEs, even after allowing for all potential fuexpansion, separate NE and management areas will not be needed.

Procedure 3-4 outlines the detailed DCN topology for small SDH network


3-6 Detailed design

n

re

Procedure 3-4Detailed DCN topology for small SDH networks

Step Action

1 For the management location, connect the local management systems via an Ethernet LAN (IP).

2 Connect any routers to the local management systems via the Ethernet LAN (IP). Routers may be used to connect to management systems in different locations using IP.

3 Connect the management systems to their respective SDH NEs via separate LANs (OSI).

4 Ensure that SDH NE engineering limits are not exceeded by referring to Appendix A (“SDH DCN deployment engineering limits”).

5 Place primary OPCs at one location and backup OPCs at another location. Connect co-located SDH NEs with a LAN.

6 Use the routers to connect the previously defined remote OPC locations to form an IP WAN, connecting to the management centres IP LANs. This can be integrated with any WAN created for connection of multiple management sites.

7 Form WAN as a ring using both serial ports on the router, for resilience for single failures of the serial links.

—end—

Large SDH networksThe SDH management domain consists of two or more SDH NE areas, aSDH management area, and links between the areas.

The detailed DCN topology for large SDH networks is defined in Procedu3-5.

Procedure 3-5Detailed DCN topology for large SDH networks

Step Action

1 Group SDH NEs into separate NE areas. Refer to Appendix A (“SDH DCN deployment engineering limits”). An allowance should be made for SDH network expansion plans.

2 Group management locations into a management area. Refer to Appendix A (“SDH DCN deployment engineering limits”).

3 Refer to Appendix A (“SDH DCN deployment engineering limits”) to link SDH NE areas to each other and to management areas.

—continued—


Detailed design 3-7

3

rge

Procedure 3-5 Detailed DCN topology for large SDH networks

Step Action

4 Design each NE area in turn. Place one router at each of the two different NE locations.

Note: Routers should support IP and OSI protocols.

5 Connect each router to the next area with an E1 link using a high-speed modem. The router port connected to the link should support IP and OSI (IS-IS L2 only).

6 Connect the two routers within the area with an E1 link using a high-speed modem.

Note: The router port connected to the link should support IP and OSI (IS-IS L1/L2).

7 Connect each router to the local NEs that are in its NE area via an Ethernet LAN.

Note: The router LAN port should support IP and OSI (IS-IS L1/L2).

8 Disable all SDH DCC links on STM-N links between NE areas.

9 Ensure that SDH NE engineering limits are not exceeded. Refer to Appendix A (“SDH DCN deployment engineering limits”).

10 Connect SDH NEs located at the same site together with a LAN.

11 Place primary OPCs at one router location and backup OPCs at the other router location.

12 Form WAN as a ring using both serial ports on the router, for resilience for single failures of the serial links.

—end—

Procedure 3-6 gives the detailed DCN topology for the management in laSDH networks.

Procedure 3-6Detailed DCN topology for the management area in large SDH networks

Step Action

1 Connect management locations together with routers.


Note: The link between the locations should have a total capacity of N or 2 Mbit/s, whichever is the greatest.

Note: [N = (number of NE area chains) * 1 Mbit/s]

Note: The router port connected to the link should support IP and OSI (IS-IS L1/L2).

—continued—


3-8 Detailed design

V).

n.

and h

er ch

n be

Procedure 3-6 Detailed DCN topology for the management area in large SDH networks

Step Action

2 Connect to the NE areas with routers.


3 Connect each router serial port to the next NE area with an E1 link using a high-speed modem.

The router port connected to the link should support IP and OSI (IS-IS L2 only).

4 Connect each router to the local management systems via an Ethernet LAN.

The router LAN port should support IP and OSI (IS-IS L1/L2).

—end—

Power supply typeBased on the analysis of the SDH network, determine the power supply available at each location with DCN equipment present.

Observe the following recommendations, where possible:

• DCN equipment co-located with SDH NEs should use DC power (-48

• DCN equipment co-located with management systems should use ACpower (100 V-260 V).

• Use only one type of power supply for DCN equipment at one locatio

Note that these are recommendations and are not mandatory.

Location definitionOnce the basic router network, Ethernet LAN connectivity requirements, power supply types are known, produce a DCN network diagram for eaclocation, showing how all the DCN components and other equipment areinterconnected.

Refer to Chapter 5 (“Topologies”) of this document, which covers DCN topology at a site.

Choose components from the approved list of coded DCN components, which are listed in Appendix C, Table 14-6, of this document.

Additional components may be added as spares, depending upon customrequirements. Refer to Chapter 7 (“Dependability”) of this document, whicovers spares issues.

The list in this document is not exclusive and other DCN components caused if desired. When other non-approved components are used, Nortelsuggest consulting the SDH DCN design group.


Detailed design 3-9

3

t they atter

h has

d res.

n.

tion r

ion)

as

H/

ent

in

n tion also

Non-coded parts may be used if customers already have DCN equipmenwish to use or a new Nortel-supplied DCN component is needed. In the lcase, “25Z...” codes will be needed.

Note: “25Z...” codes should be avoided if at all possible.

Generate component listThe total DCN equipment requirement, its location, and its rollout througtime should be available if the process outlined in the preceding section been followed.

The DCN equipment should be captured in a total list for DCN costing anDCN equipment ordering purposes. This list should include the DCN spa

A site-by-site equipment list should be drawn up for equipment installatio

Refer to Chapter 4 (“Key network components”) of this document.

ConfigurationSome of the equipment in the DCN needs to be configured. The configuracan vary from a dual in-line package (DIP) switch setting to a list of routeconfiguration statements. The items that may require configuration are:

• routers (IP address, OSI address and topology dependent configurat

• terminal servers (IP address and general configuration)

• management systems (IP address and for some EC’s OSI addresseswell)

• SDH NEs (OSI address, LAN/DCC port on/off status and DCC (RSOMSOH usage)

• high-speed modems (clock master/slave)

To derive the configuration information required for each network compon

• Determine the basic configuration for each component based on the equipment type and its position in the DCN. Refer to the DCN Commissioning Guide NTP 323-4061-210 for more information.

— With most SDH NEs, no configuration information will be needed because the equipment default configuration will be adequate.

— Router configuration templates can be selected from the list givenAppendix D of this document.

• Add addressing information where appropriate.

• Add access list information for firewall where appropriate.

• Add passwords as required.

Ensure that configuration information is generally available for the persoresponsible for the equipment configuration. Nortel maintains the informafor future reference and also provides it to the customer. The information enables DCN spares configuration for future installation.


3-10 Detailed design

on

A.

e

g

ess

Consult the DCN Commissioning Guide NTP 323-4061-210 for detailed information.

Installation information Define the physical location of the DCN equipment, including informationthe type of equipment racking to be used. SDH DCN Release 2 offers a variety of racking configurations based on two rack heights, 36U and 42UBasic rack in each size is available preassembled from the supplier. For further information about ancillary racking equipment, see Appendix C.

Prior to the installation of all the equipment that requires configuration, ensure that either

• the equipment is pre-configured and allocated to a specific place in thDCN topology

• the configuration information is available to the Installation staff

Finally, ensure availability of all required installation information, includin

• DCN topology diagrams

• site plans

• equipment list

• equipment configuration information

— SDH NE OSI addresses and DCC/LAN port on/off status

— SDH management systems IP and OSI addresses

— DCN completed configuration templates, including addresses, acclists and passwords

• the DCN Commissioning Guide NTP 323-4061-210

Refer to Chapter 10 (“Installation guidelines”) of this document, which covers installation issues.

end of chapter


4-1

4

, . The e EC/

Ss

ey ks, s and

they st

Key network components 4-General definitions

This section contains a definition of some terms commonly used in description of DCNs.

DCNThe DCN provides data communications between SDH NEs and their management systems. The ITU-T recommendation M.3010 Principles for a Telecommunications Management Network (TMN) formally defines the DCN.

The DCN consists of communicating entities such as operations systemsmediation devices, and NEs and the links or subnetworks between themDCN represents an implementation of the OSI layers 1 to 3. Formally, thDCN provides no functionality at layers 4 to 7, but layer 4 is covered for NE interoperability. Refer to SDH network elements on page 4-3 and Network and element controllers on page 4-4.

The DCN is an arbitrary network of two types of communicating entities: Eand ISs, which are connected by links or subnetworks.

End systemESs provide a source and destination for data communications traffic. Thcan be attached to one or more data communications links or subnetworbut they cannot pass data communications traffic between them. The ECsome NEs are ESs.

ISO 8648 Internal Organization of the Network Layer provides formal definitions of the terms “end systems”, “intermediate systems”, and “subnetworks”.

Intermediate systemISs can pass data communications traffic between subnetworks to whichare connected. This functionality is sometimes referred to as routing. MoSDH NEs and third-party OSI routers are ISs. ISs are either Level 1 or Level 2.

SubnetworksTwo types of subnetworks are considered in this document:

• broadcast


4-2 Key network components

DH

ork ing

/IP ther

• general topology point to point

For a further definition of these subnetworks, see ISO/IEC 10589 IS-IS Protocol, Section 6.2 (“Subnetwork types”).

The SDH DCN uses two types of broadcast subnetwork:

• Ethernet LAN

— ISO 8802-3, IEEE 802.3, or DIX Ethernet CSMA/CD 10 Mbit/s

• Communications network (CNET)

— IEEE 802.4 Token Bus 2 Mbit/s

Two types of general topology point-to-point subnetworks are used in the SDCN:

• SDH DCC

— regenerator section overhead (RSOH) 192 kbit/s (D1-D3)

— multiplex section overhead (MSOH) 576 kbit/s (D4-D12)

• high-speed serial wide-area network (WAN)

— E1 or ITU-T G.703 2 Mbit/s

— ITU-T X.21 64kbit/s or 2 Mbit/s

Lower layer interoperabilityThis interoperability layer enables one IP or OSI implementation to interwwith another at the physical, data link, and network layers. This interworkforwards information between communicating network layer users.

End-to-end interoperabilityThis level of interoperability is required when an application on one TCPor OSI entity needs to communicate information to an application on anoTCP/IP or OSI entity. This involves the operation of the transport layer inaddition to the three lowest layers.

DCN main component typesThe main component types in the DCN are:

• SDH NEs

• network and element controllers

• routers

• terminal servers

• high-speed modems

• low-speed modems

• LAN components


Key network components 4-3

4

SDH

NE re e

.

ns

port

SDH network elementsThe NEs and their respective ECs may be connected to the parts of the DCN that support OSI protocols. Refer to NEs and respective ECs that maybe connected to SDH DCN ports supporting OSI protocols on page 14-1.

In general, Nortel NEs have lower-layer interoperability. However, not all types can be freely interconnected at the present time. Any restrictions adescribed in Appendix A: SDN DCN deployment engineering limits on pag12-1.

All subsequent releases have the same or better levels of interoperability

The following NEs are indirectly connected to the DCN for communicatiowith their management systems, as illustrated in Figure 4-1:

• Tellabs 532E 1/0 cross connect via a Cisco 2509 terminal server V.24

• PDMX-E via an ATU, TN-1P, or TN-1C V.24 port

Figure 4-1Indirect NE connections to DCN for communications with their management systems

OA

NRM

MOA Router

LAN

Terminal server

V. 24

532

WAN

LAN

Router


4-4 Key network components

/IP

efer

-3

iate

d via

s

Network and element controllersThe Nortel NRM and all ECs may be connected to the SDH DCN.

The NRM communicates to its ECs via the DCN using conventional TCPprotocols. The ECs communicate to their NEs via the DCN using OSI protocols. Therefore, the DCN must support both IP and OSI protocols. Rto Main element controller types (OSI system) on page 14-2.

RoutersSee Routers forming the main components of the SDH DCN on page 14.

OSI capable routers can be configured to function as L1 and L2 intermedsystems, on a port-by-port basis.

Terminal servers

The terminal servers listed above only support TCP/IP and cannot be useOSI-only systems.

The terminal servers have an associated Octal cable for connection to terminals or modems, etc.:

• Octal male DB25 modem cable

• Octal male RJ45 cable

• Octal female DB25 terminal cable

• Octal male DB25 cable

High-speed modemsUse the following high-speed serial modems to connect the ITU-T X.21 interface on the routers to ITU-T G.703 2 Mbit/s leased lines (E1):

• Fourthtrack/Market Vision MicroMux SP-1-RA

— X.21 to E1 (selectable 120 ohm or 75 ohm) and AC power

• Fourthtrack/Market Vision MicroMux SP-1-RA DC

— X.21 to E1 (selectable 120 ohm or 75 ohm) and -48 V DC power

Terminal servers that provide access to remote asynchronous serial portacross SDH DCN are:

Server model Specifics

Cisco 2509 One LAN port (AUI), two high-speed serial ports (X.21), eight low-speed asynchronous serial ports (V.24) and AC power

Cisco 2509 DC One LAN port (AUI), two high-speed serial ports (X.21), eight low-speed asynchronous serial ports (V.24) and -48 V DC power


Key network components 4-5

4

m) .

rt).

ntry

T)

These devices are supplied with a Cisco X.21 DTE male router cable (3 for connection to a Cisco router high-speed synchronous serial interface

LAN componentsEthernet ports are RJ45, DCE, and AUI. Refer to Components used to extendor construct LANs (Ethernet or CNET) on page 14-4.

Dial-up low-speed voice modemsUse the Multi-Tech Systems External dial-up low-speed voice modems (MT2834BL) to provide remote access to workstations or routers (aux poThese modem links are used for remote access to Nortel’s staff.

Note that different versions of this modem exist for different countries. Consult the manufacturer to determine the correct part for a particular cou(for example, MT2834BLK for the UK).

Release 2 requires 64 kbit/s modems.

Refer to Components used to extend or construct LANs (Ethernet or CNEon page 14-4.

Component tablesRefer to SDH DCN components list, Release 2 on page 14-7 for information on all the approved parts for use with the SDH DCN.

end of chapter


5-1

5

s

of

Topologies 5-Overview

This section provides information on the network topologies to be used apart of a SDH DCN design. Refer to “Appendix A: SDN DCN deployment engineering limits” on page 12-1 for size limitations of the network’s variousparts.

Basic DCN component connectivityExternal SDH DCN

Figure 5-1 shows the basic unit of the external SDH DCN. It consists of a10BaseT LAN hub and a router with two serial WAN ports connected viahigh-speed modems to 2 Mbit/s leased lines. The router supports routingboth TCP/IP and OSI.

Figure 5-1Basic components of the external DCN

The following devices may be connected to the external DCN:

• Network Controllers (NCs): NRM and support devices

• ECs: OPC,EC-1,EC-1.5L, EC-4X, MV36, and support device.

• SDH NEs: STM-16 4F, TN-16X, TN-16L, TN-4X, TN-1X, TN-1C, TN-1P, and cross connects

Router

Modem

G.7032 Mbit/s

Modem

G.7032 Mbit/s

10BaseTLAN Hub

X.21Serial

X.21Serial

LAN

WAN

WAN

10BaseTUTP x

10BaseTUTP

SDHNE

SDHNE

G.7032 Mbit/s

OPC

LAN cablesand transceivers

X = cross connectE = straight

= transceiver


5-2 Topologies

es

ks.

,

een is ion

• Other: TN-1/0, TN-1X, ATU, terminal servers, and other ancillary devic

Internal SDH DCNThe internal SDH DCN is the network of SDH NEs connected by DCC linThe internal SDH DCN components are as follows:

• Low-rate SDH NEs: TN-4X, TN-1X, TN-1C, and TN-1P/PH

• High-rate SDH NEs: TN-16L, TN-16X, and STM-16 4F

The topologies of the internal SDH DCN are a subset of the SDH traffic topologies.

Figure 5-2 show the structure of the internal DCN consists of rings, loopsand chains of DCC links. The internal DCN in a real network can be verylarge and complex.

Figure 5-2Basic structures of the internal DCN

Balancing the internal and external DCNThe process of generating the SDH DCN design involves a balance betwthe internal and external parts of the SDH DCN. The optimum SDH DCNdesign minimizes the external DCN and maximizes the internal DCN. Threcommended design reduces to a minimum the SDH DCN implementatcosts for Nortel customers.

16X 16X

16X

16X

4X

DCC

DCC

DCC

CNET CNET

DCC

DCC

1X

4X

16X

16X

1XOPC

4X

DCC

1X

No DCC

16X

DCC

16X

DCC

1X 1X

DCC

DCCDCC

DCC

1C 1C 1C

DCC

DCCDCC

DCC

4X

DCC

DCCDCC DCC

DCC

1P

DCC

DCC

DCC

No DCC

10BaseTLAN Hub

10BaseTLAN Hub

1X

OPC

1P 1P

4X

DCC

DCC

DCC

DCC

DCC

No DCC

16X1X

XC40X 4/1

CNET

16X

DCC


Topologies 5-3

5

hese ffect

ide t, it

y to

at

In

ts

ems,

DH the

IP and OSI protocol co-existenceRelease 2 of the SDH DCN supports IP and OSI protocol co-existence. Tprotocols are considered “ships that pass in the night” and thus have no eon each other’s operation.

Therefore, if a router network is present, it is no longer necessary to provECs with two Ethernet LAN ports. When an OSI router network is presenis possible to have a single Ethernet LAN port configured for Internet Protocol (IP) and OSI on the workstations.

Connect SDH NE LAN ports only to the SDH DCN and not directly to a general-purpose customer TCP/IP network.

Another aspect of protocol co-existence provided by the DCN is the abilitcarry OSI protocol traffic over an IP-only DCN. This is accomplished by encapsulating the OSI packets inside IP packets.

The technique is known as tunnelling. It requires an OSI-capable router each end of the “tunnel” to perform the encapsulation. Use this approachwhen the EC is separate from its SDH NEs by an existing IP-only DCN. this circumstance, the “tunnel” is also be an OSI IS-IS routing protocol Level-2 only link. Refer to Loopback interface on page 8-8 and Tunnel interface on page 8-9 for additional information on tunnelling.

SDH DCN Release 2 does not provide a technique for carrying IP packeover an OSI-only network, such as the DCC links between SDH NEs.

SDH management domain architectureThe SDH management domain is the network of SDH management systSDH NEs, and the SDH DCN. It forms an OSI routing domain and an IP autonomous system (from a data communications perspective).

Large domainsFigure 5-3 shows the structure of the domain is built up from chains of SNE areas. Each chain links up to five SDH NE areas. The links between areas are E1 (2 Mbit/s) leased lines.


5-4 Topologies

n, but

ns

Figure 5-3Maximum size domain

The SDH NE area chains are linked back to two separate locations in themanagement area. The management area can have only a single locatiothis reduces the availability of the management system.

The fundamental structure of the domain supports any number of NEs. However, higher capacity routers are required in the management locatiothan are available in this release.

SDH management areaFigure 5-4 shows the structure of an SDH management area.

SDH ManagementLocation

SDH Management Area

SDH NEArea 1

SDH NEArea 2

SDH NEArea 3

SDH NEArea 4

SDH NEArea 5

An SDH NE area can contain up to 150 NEs.All inter- or intra-area links are E1 (2 Mbit/s).

SDH NE Area 6-10


SDH NE Area 16-20

SDH NE Area 11-15

SDH Management Domain


Topologies 5-5

5

high ot

and

Figure 5-4Example of an SDH management area

The recommended SDH management area has two locations to provide alevel of availability. A single SDH management location is possible but nrecommended.

The LAN connecting the router to the management systems supports IPOSI protocols. This means the ECs need only a single LAN port, which supports IP and OSI.

Use 10BaseT LAN hubs to extend the LAN.

Nortel recommends you use AC-powered DCN equipment in SDH management locations.

Future releases will cover use of network printers.

ManagementSystem

ManagementSystem

ManagementSystem

ManagementSystem

ManagementSystem

ManagementSystem

E1

OSI (L1/L2) and IP

Router Router

SDH Management Area

OSI (L2 only) and IP

SDH Management Location SDH Management Location

OSI and IP OSI and IP

E1


M M M

Router (2501/5/7) (2501) (2501/5/7)

M M

Router (2501)

M MM

E1E1

to NE Areas 1-5 to NE Areas 1-5

denotes option to increasemanagement availability.

E1


5-6 Topologies

Figure 5-5 shows the structure of an SDH management location for a maximum-size domain.

Figure 5-5Example of a large SDH management area

SDH NE areaFigure 5-6 illustrates the structure of an SDH NE area. This is a commonstructure. An STM-16 ring forms the backbone of the area.

10BaseTLAN Hub

Router (2514)

M M

10BaseTLAN Hub

Router (2514)

M

Rou

ter

(251

4)

MM

to other ManagementLocation


E1


E1

E1

SDH Management Location

ManagementSystem

ManagementSystem

M


Topologies 5-7

5

t. A t

le to

stem.

Figure 5-6Example of an SDH NE area

An optimum SDH NE area has two SDH NE locations with routers presensingle-location area with a router present is not recommended because ireduces network availability.

An SDH NE area contains up to 150 OSI ISs. See Appendix A: SDN DCN deployment engineering limits on page 12-1 for more detail on the topology restrictions. These topology restrictions mean that it is not always possibreach the 150-NE limit for the area.

When an STM-N link crosses the boundary of an SDH NE area, the DCCmust be disabled.

Another common SDH network structure is an SDH radio line system, asshown in Figure 5-7. In this case, place a router at each end of the line sy This approach applies to any type of SDH line system.

4X

SDH NE Area

RouterRouter

4X

16X 16X

16X

16X

4X

1X

OSI (L1/L2) and IP

E1

E1 E1OSI (L2 only) and IP OSI (L2 only) and IP

DCC

DCC

DCC

DCCDCC

OPC

OPC

CNET CNET

LAN LAN

DCC disabled

SDH NE Location SDH NE Location

1X

DCC

OSIand IPOSI

and IP

OSI


5-8 Topologies

se ork

a

Figure 5-7Example of an SDH NE area with SDH radio systems

Large numbers of potential SDH NE topologies exist. This document does not show them all. The operation of the OSI routing protocols (ES-IS andIS-IS protocols) means that however complex the SDH DCC network, it works with the external SDH DCN.

Isolated SDH NEsWhen small numbers of low-rate SDH NEs are isolated from their ECs, uleased lines of only 64 kbit/s to reach them. Reach an isolated SDH netwof up to 32 low-rate SDH NEs in this manner.

A router is needed at each end of the 64 kbit/s leased line. Configure therouter to bridge or route the OSI protocols.

SDH NE locationFigure 5-8 shows in more detail the structure of an SDH NE location withrouter present.

4X

SDH NE Area

RouterRouter

4X

4X

OSI (L1/L2) and IP

E1

E1 E1OSI (L2 only) and IP OSI (L2 only) and IP

DCC

OPC OPC

CNETCNET

LAN LAN

DCC

CNETDCCDCC

SDH Radio SDH Radio

DCCDCC

ClearChannel

ClearChannel


Topologies 5-9

5

Es

l

seT

Figure 5-8Example of an SDH NE location with a router present

The routers at the NE locations support routing for IP and OSI protocols.

The LAN connecting the router to the NEs will be 10BaseT. Therefore, Nwith attachment unit interface (AUI) ports need a 10BaseT transceiver.

The LAN connecting the router to the SDH NEs supports IP and OSI protocols.

When less than eight items require connection to the router, Nortel recommends you use a router with an integral hub (Cisco 2505).

When more than eight items require connection to the router, an externa10BaseT LAN hub is needed.

Nortel recommends you use DC-powered DCN equipment in SDH NE locations.

Small domainsFigure 5-9 shows that the minimum SDH DCN consists of a simple 10BaLAN hub and DCC links to support simple SDH rings.

SDH NE Location

Router (2505)

4X 1X

XC40X 4/1

TerminalServer

XC1/0

E1 OSI (L2 only) and IP E1 OSI (L1/L2) and IP

OPC

CNET DCC

DCC

V24

1P 1P

1PH shelf

1 12

STM-1DCC

1X

DCC

M

LAN

(OSI and IP)

16X

M


5-10 Topologies

ment DH

t

.

ll e IP

Figure 5-9Minimal SDH DCN

The DCN type shown in Figure 5-9 can be used in a small SDH managedomain when a smaller number of SDH NEs (<150) are present in the Snetwork.

In this case, provide the ECs with two LAN ports. Configure one LAN porfor OSI protocol support and the other for IP support.

The main DCN equipment in this type of network is a 10BaseT LAN hub

Small domains can have router networks. Use the routers to access smagroups of remote NEs or link OPCs back to the NRM. In this situation, throuters do not support OSI routing protocols; they are configured to routeand bridge OSI protocols.

EC-1X

OSI LAN

ST

M-1

Rin

gE

CC

1X1X

1X

1X

1X1X

1X

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

1X

10BaseTLAN Hub

10BaseTLAN Hub

NRM

To other ECs

IP LAN


Topologies 5-11

5

Figure 5-10Routers in a small domain

1X

EC-1

OSI LAN

ST

M-1

Rin

gE

CC

1X1X

1X

1X

1X1X

1X

1X

NRM

IP LAN

10BaseTLAN Hub

Router (2514)

M M

10BaseTLAN Hub

Router (2505)

M M M M

4X 1XOPC

Router (2505)

OPC

EC-4X

Bridged OSI and routed IP

Bridged OSI and routed IP Bridged OSI and routed IP

Bridged OSI Routed IP

16X 16X

DCCDCC

DCCCNETCNET


5-12 Topologies

and s on

, it is

/

03

Narrowband access supportThe SDH DCN provides a path for the PDMX-E EC to access its narrowbNEs. The ATU function accomplishes this. The ATU encapsulates frameits serial V.24 ports in OSI packets. A separate card in the TN-1X or an internal function in the TN-1C or TN-1P provides the ATU function.

When the ATU is implemented as a separate card (TN-1X or standalone)an OSI ES.

Figure 5-11Narrowband access multiplexer and the ATU

Refer to the Provisioning Guide for Asynchronous Telemetry Phase 1 (25DQT00750ABW) for more detailed information.

Non-interoperabilityFor network topologies not supported by the LAN/DCC alone, use G.7032 Mbit/s WAN links and third-party bridge functionality (Cisco 250x bridgerouter plus X.21/G.703 modem).

Figure 5-12 illustrates the usage of a pair of LAN bridges linked via a G.72 Mbit/s circuit or 64 kbit/s leased lines.

ATU

EC-1

LANECATU

ATU

16 x V.24

ATU

ATU

LAN LAN

ATU

ATU

ATU

BaydelBox

TN-1XShelf

ATU

ATU

PDMX-E

ST

M-1

Rin

gE

CC

1X1X

1X

1X

1X1X

1X

1X

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

TN

-1X

Rin

gE

CC

10BaseTLAN Hub

PDMX-E

PDMX-E

PDMX-E

PDMX-E

V.24

LAN

ATU


Topologies 5-13

5

due

Figure 5-12Use of bridges in SDH networks

The main purpose of this bridge link is to link parts of the OSI data communications network that cannot be linked by the DCC. This may beto

• a lack of interoperability

• a total lack of a DCC path or

• a lack of capacity in the DCC path

Release 2 guidelines rule out support for other WAN links such as ISDN(128 kbit/s) or X.25 PVCs because of

• the throughput/delay restrictions and

• lack of availability of such services in all SDH deployment scenarios. end of chapter

EC-1

LAN

10BaseTLAN Hub 1X

1X1X1X

No DCC

Modem 1X10BaseTLAN Hub

Router

Modem

Non OSI

No DCCLAN

G.7032Mbit/s G.703

2Mbit/s

LAN

LAN

STM-1 RingDCC

1X 1X 1X

1X

1X 1X 1X

SDH DCN

No DCC

No DCC

No DCC

No DCC

OSI communications path

X.21 X.21

Router


6-1

6

for ely n

tion g le

his

the in

a

s the

Management and security 6-Management strategy

Use the Cisco router command line interface as a management strategythis release. Accessed this command locally by a local terminal or remotusing Telnet. However, a later release will contain recommendations for aSNMP based management system.

The local terminal can be a VT100 terminal or a PC with a terminal emulasoftware package (for example, Windows 95, Hyperterm). Use the cablinsupplied with the router to connect the terminal or PC to the router consoport (V.24). Nortel recommends no particular terminal for this function in trelease.

Refer to the SDH DCN Commissioning Guide NTP 323-4061-210 for the detailed configuration for the local terminal characteristics.

In an established SDH DCN, use Telnet to connect to remote routers fromlocal router command line interface. This requires set-up of IP addressesthe router network.

Access can also be obtained using Telnet/TCP/IP over a LAN port from UNIX workstation. Nortel recommends an Xterm window operating in VT100 mode for Telnet connection to remote routers. This type of accesrequires the IP addresses to have been set up correctly in the router andworkstation. Therefore, use this approach only after the DCN has been installed.


6-2 Management and security

may

r

e

sco

34

to

t) g

Figure 6-1Access using Telnet/TCP/IP over a LAN port from a UNIX workstation

Management capability is provided only for status light emitting diodes (LEDs) and dual in-line (DIL) switches for configuration.

This release supports only configuration and diagnostics. Future releasessupport network-wide fault monitoring using SNMP.

Remote accessRemote access to the SDH DCN may be provided to a customer DCN fogeneral maintenance and diagnostics by Nortel staff. Note that it must bedone in a secure fashion.

Connection of a 9600 baud dial-up modem provides remote access to thSDH DCN. This is accessible only from a remote conventional PC and modem in a predefined and secure location. Connect the modem to a Cirouter AUX port or a UNIX workstation asynchronous serial port.

Note that asynchronous modems are generally country specific. Nortel recommends you use a product from the Multi-Tech Systems, Inc. MT28range of external modems. The MT2834BLK is appropriate for use in theUnited Kingdom. Refer to “Multi-Tech MT2834BL modem approvals with part numbers” on page 14-5 for a list of country-specific asynchronous modems.

Within the router network or from a UNIX workstation, use Telnet/TCP/IPconnect to remote equipment.

Security strategy DCN Release 2 offers improved security features:

• Cisco’s router password scheme is explained in more depth. Detailedrecommendations on its implementation are made.

• Firewall functionality within routers is introduced. When the DCN is connected to an external network, (for example, a customer’s Intraneaccess across the boundary of the two networks is controlled by usinaccess lists.

Router

Modem

G.7032 Mbit/s

ModemG.7032 Mbit/s

10BaseTLAN Hub

X.21Serial

X.21Serial

LAN

WAN

WANLAN cables and transceivers

PC

Console

UNIX WS


Management and security 6-3

6

ss.

at rk in

y.

n rnal rnet.

IP lowed

ub/

s is , ass rt

be

PasswordsThe Cisco router’s password scheme provides security. Use either of twolevels of password on the Cisco routers. The first level provides access to view the configuration, while the second level “enable” provides full acce

Most routers are supplied with Cisco default passwords. It is essential ththese are changed for something unique to the device or part of the netwowhich it resides. Change passwords on a regular basis.

Allocate different passwords for each type of user access (for example, “telnet” [vty], “console port” [console], and “modem” [aux]).

For a full description of passwords, see the “Security controls” section ofSDH DCN Commissioning Guide 323-4061-210. It gives recommendations for implementation and procedures for encryption and password recoverAlso refer to Example on page 9-1 of this manual.

FirewallsProtection must be provided for the DCN network at every point where aexternal connection exists. The firewall offers control over access by exteusers to the DCN and if necessary restricts DCN users access to the Inte

Using the “access-list” command from the IOS on a Cisco router, lists of packets defined by source or destination address and packet type are alor denied passage across the firewall.

Refer to the Security Controls section of SDH DCN Commissioning Guide 323-4061-210, which includes some examples. More examples of configurations are available from Cisco via FTP from ftp://ftp.cisco.com/pacl-examples.

Determining requirementsDetermine whether the DCN needs external access. If no external accesrequired, the most effective firewall known is already in place. Otherwiseascertain from the network designer (and customer) what packets must pout of and into the DCN network and why such traffic is justified to suppothe administration of the DCN.

For each instance of allowable access, the following parameters need toavailable:

• source IP address and mask (mask is optional)

• destination IP address and mask (mask is optional)

• packet direction

• protocol (IP, TCP, etc.)


6-4 Management and security

fer f

list). kets

ess

cept the

y ter.

the of

Configuring The Cisco IOSTM has a number of commands for firewall construction. (Reto the Cisco IOSTM software documentation on CD ROM for the full range ocommands.) The following are a basic selection:

access-list access-list-number, deny/permit, source, source-mask

In its standard form this command adds an entry to a table (accessEach entry matches or compares the source IP address of all pacentering the router and either permit or deny passage.

access-list access-list-number, deny/permit, protocol, source, source-mask, destination, destination-mask

The extended form of this command allows you to make decisionsbased on a particular protocol or service.

Note 1: The standard form of the access-list command constructs accesslists with numbers from 1 to 99 and the extended form constructs acclists with numbers from 100 to 199.

Note 2: Subsequent entries in an access list override earlier entries. For example, to bar all packets coming from an IP address and mask (expackets from a specific address within that mask), write an entry withexception as a permit followed by the bar as a deny.

Thus a series of access lists may be constructed which completeldefine the criteria for allowing passage of packets through the rou

show access-lists

All access lists will be listed. This is not a privilege command and lists are available to anyone who can log on to the router. A rangeCisco IOSTM privilege commands prevents this.

IP access-group access-list-number, in/out

This command assigns an access list to an interface.

Remote accessNortel recommends remote access via dial-back modems for security purposes.

end of chapter


7-1

7

ingle

t two

ss

an

.

of a for a

ur

Dependability 7-Design

AvailabilityDesign the SDH DCN to be dependable. It should be proof against any slink or equipment failure preventing the operation of the DCN.

To achieve dependability, duplicate network functions and ensure at leaspaths exist for any route in the network.

Note that there is a cost penalty associated with high dependability. Unlethere is a clear requirement for full dependability which justifies the additional DCN costs, maintain duplicated links but omit duplicate equipment.

To ensure reliable operation, balance the performance of the DCN components and the links between them against the demand. Follow thisdocument’s guidelines to ensure that this is the case.

ReliabilityIn general, DCN components have a good level of reliability with high MeTime Between Failure (MTBF) figures.

Cisco 2500 series routers have an MTBF of approximately 90 years. TheMTBF figures for the other DCN components tend to be higher.

MaintenanceIn-country spares

Use the “in-country spares” policy to minimize the time to repair the DCN

Maintain a duplicate of each component type in each geographical regioncustomer network. Include these spare components in the component listcustomer DCN.

The target Mean Time To Repair (MTTR) for the DCN is approximately fohours. Particular customers specify MTTR requirements for their SDH networks and even their DCNs.


7-2 Dependability

ance ance

m f

the t as ey

heir

is

is mer than ters

Supplier maintenance agreementsEnsure that all key DCN components have a component supplier maintenagreement that operates in a back-to-back manner with Nortel’s maintenagreements with its customers.

Ship failed components back to Nortel in exchange for a replacement frothe DCN component supplier. This process takes a significant number odays, dependent upon the customer’s location.

“Hot” sparesWhere DCN components contain software, connect them permanently tonetwork. They perform no useful function within the DCN but are presen“hot” spares. This ensures that their functionality is monitored and that thare included in any software upgrades that take place.

Manage the “hot” spares like any other active DCN component in the customer network. When the spares are needed, disconnect them from tparking position and move them to the part of the network that they are needed in. Update the access lists and password information.

Configuration backupDCN components often require configuration to provide their function. Thconfiguration ranges from some DIL switch settings to a Cisco router configuration.

Record and back up all DCN component configurations. This informationvital when installing a replacement part for a failed one. Provide the custowith a system to save this information, which often proves more valuable the equipment hardware that is being configured. Note that the Cisco rouuse terminal file transfer protocol (TFTP) to upload and download their configuration.

end of chapter


8-1

8

ng.

ded

es

Protocols 8-Addressing

OverviewNote: Subsequent sections are Nortel’s preferred method of addressi

This section provides tutorial information.

An understanding of the information in this part of the chapter will be needuring the process described in Chapter 3 (“Detailed design”) of this document. Review information in this chapter before attempting processdescribed in Detailed design on page 3-1. Refer to Appendix B: Protocol reference information on page 13-1 for more detailed protocol information.

Procedure 8-1 outlines large SDH network addressing schemes.

Procedure 8-1Designing addressing scheme for large SDH networks

Step Action

1 Obtain an IP address range for the SDH management domain from the customer or an appropriate IP address allocation authority.

The Classless Inter-Domain Routing (CIDR) strategy means that only class C addresses are allocated to Nortel customers.

Alternatively, use the class C private network address scheme (192.168.0.0 - 192.168.255.255).

2 Allocate a network address and subnetwork mask for each IP subnetwork in the DCN.

3 Give each host an IP host address.

4 Obtain an OSI address range for SDH management domain from the customer or an appropriate OSI address allocation authority.

Nortel recommends the use of ISO data country code (ISO 3166) format OSI addresses.

—continued—


8-2 Protocols

ples

our

hat

nd

ted

h is e three

ere rks

it he e

ined.

Procedure 8-1 Designing addressing scheme for large SDH networks (continued)

Step Action

5 Allocate an OSI area address for each separate area in the domain.

6 Establish the period of time during which the DCN has to be installed.

This may involve more than one phase of deployment.

—end—

IP networks, subnetworks, and subnetwork masksThis section briefly explains the concepts of IP addressing and uses examfrom DCN to illustrate.

• Every interface within an IP system must have a unique IP address (fbytes expressed in decimal and separated by dots [for example, 192.168.12.43]).

• Interfaces for point-to-point links (that is, serial interfaces) can be unnumbered. Unnumbered interfaces are referenced to an interface thas an address.

• The IP addresses available for the system are divided into networks afurther subdivided into subnetworks.

• Devices must be grouped together such that they are directly conneconly to other devices with IP addresses conforming to the same subnetwork addresses.

• The address range available for private networks is 192.168.x.y (x = 0 to 255, y = 0 to 255, where “x” is the part of the IP address whicavailable for the network address; therefore up to 254 networks can bdefined). For example 192.168.1.0, 192.168.2.0, and 192.168.3.0 are different network addresses. Every device or interface connected to network 192.168.1.0 must have an IP address that is 192.168.1.y (wh“y” is the part of the IP address which is available for both the subnetwoand the host identifier [ID]).

• “y” is a decimal representation of an 8-bit binary number (which is whyis within the range 0-255 in decimal). How many of the 8 bits define tsubnetwork and how many define the host ID is the free decision of thnetwork designer.

• The subnetwork mask is the mechanism by which the number of bitsallocated to the host ID and the number allocated to subnetwork is def

IP addressing examplesThe following examples illustrate how this system works.


Protocols 8-3

8ted to

erial

or up

.

Figure 8-1Two routers within an SDH NE area

Between them, the two routers shown in Figure 8-1 have the following interfaces:

— router 1, serial 0: unnumbered and referenced to loopback 0


— router 1, Ethernet 0

— router 1, loopback 0



— router 2, Ethernet 0

— router 2, loopback 0

Four separate subnetworks are required. These are the networks connecR1 Ethernet 0, R1 loopback 0, R2 Ethernet 0, and R2 loopback 0. The sports are unnumbered and thus do not require subnetworks. In order to provide four subnetworks, two bits are required.

If three bits are used for the subnetwork addresses, this gives provision fto eight subnetworks. This is advisable in case it is required to add an interface later. This leaves five bits that are used for the host ID.

Five bits gives 32 combinations. The host IDs of 00000 and 11111 are reserved. The Ethernet port of the router will usually have host ID 00001Therefore 00010 to 11110 are available for up to 29 other devices.

The subnetwork mask will therefore be:

in binary:

in decimal: 255.255.255.224

Serial link Serial link

LAN LAN

Serial link

Loopback 0Loopback 0

Ethernet 0 Ethernet 0

11111111 11111111 11111111 111 00000

Subnetwork Host ID


8-4 Protocols

to

6 to

ork as.

Therefore, the following addresses can be allocated:

• R1 Ethernet 0

— subnetwork 192.168.7.0

— IP address 192.168.7.1, subnetwork mask 255.255.255.224

— host ID for other devices connected to R1 Ethernet 0: 192.168.1.2192.168.1. 30

• R1 loopback 0



• R2 Ethernet 0



— host ID for other devices connected to R2 Ethernet 0: 192.168.7.6192.168.7.94

• R2 loopback 0



• Subnetworks 192.168.7.128, 192.168.7.160, 192.168.7.192, and 192.168.7.224 are available for future expansion.

• Note that network address 192.168.7.0 is used in order to leave netwaddresses 192.168.1.0 through 192.168.6.0 for the management are

Figure 8-2 illustrates IP address allocation.


Protocols 8-5

8

Figure 8-2Allocation of IP addresses

Figure 8-3Routers within a management area

Between them, the three routers in Figure 8-3 require the following subnetworks:

— router 1 - Ethernet 0

— router 2 - Ethernet 0

— router 1 - loopback 0




LAN LANSubnet:

192.168.7.97

Subnet:

Serial link

Network: 192.168.7.0

Loopback 0:

192.168.7.33

Loopback 0:

192.168.7.64192.168.7.0

Ethernet 0:192.168.7.1

Ethernet 0:192.168.7.65

R1 R2

LAN

Loopback 0Ethernet 0

Loopback 0Eth 1

Seriallinks

Eth 0Loopback 0

Eth 1

Seriallinks

Eth 0

LANLAN

Seriallinks

R3

R2R1


8-6 Protocols

ent ement he

rnet

The

n of the

— routers 1 and 2 - Ethernet 1, router 3 - Ethernet 0

Six subnetworks are listed. To allow for expansion, use four bits of subnetwork mask. This leaves only 4 bits for the host ID, which is 13 workstations per Ethernet port.

• Each serial loop supports up to 750 NEs. Each LAN in the managemarea must therefore be capable of supporting enough workstations tomanage 750 NEs. Thirteen host IDs are not adequate, thus the managareas will require multiple IP network addresses. This is achieved in tfollowing way:

• network address 192.168.1.0 for router 1 - Ethernet 1, router 2 - Ethe1, router 3 - Ethernet 0, and all of the loopback interfaces

• network address 192.168.2.0 for router 1 - Ethernet 0

• network address 192.168.3.0 for router 2 - Ethernet 0

• network address 192.168.2.0 and 192.168.3.0 have no subnetworks.subnetwork mask for these two networks is 255.255.255.0. Up to 253workstations or other devices can be connected to Ethernet 0.

Network address 192.168.1.0 has four subnetworks. To allow for additioextra serial loops and routers, use four bits for subnetwork address and remaining four bits for host IDs. The subnetwork mask is therefore

in binary:

in decimal: 255.255.255.240

Table 8-1 shows possible address allocations.

Table 8-1Addresses that can be allocated

R3 Ethernet 0 network 192.168.1.0subnetwork 192.168.1.0IP address 192.168.1.1, subnetwork mask 255.255.255.240

R3 loopback 0 network 192.168.1.0subnetwork 192.168.1.16IP address 192.168.1.17, subnetwork mask 255.255.255.240

R1 Ethernet 0 network 192.168.2.0IP address 192.168.2.1, subnetwork mask 255.255.255.0host ID for other devices connected to R1 Ethernet 0:192.168.2.2 to192.168.2.254

—continued—

11111111 11111111 11111111 1111 0000

Subnetwork Host ID


Protocols 8-7

8
Figure 8-4 illustrates IP address allocation in a management location.


R2 Ethernet 0 Network 192.168.3.0IP address 192.168.3.1, subnetwork mask 255.255.255.0host ID for other devices connected to R1 Ethernet 0: 192.168.3.2 to192.168.3.254



Subnetworks available for future expansion, though each has only four bits available for the host ID

192.168.1.64192.168.1.80192.168.1.96192.168.1.112192.168.1.128192.168.1.144192.168.1.160192.168.1.176192.168.1.192192.168.1.208192.168.1.224192.168.1.240

—end—

Table 8-1Addresses that can be allocated


8-8 Protocols

st if a ny bles. e

aces wo d if

own ll not ve s er, ia the

his is t IP rather

Figure 8-4Allocation of IP addresses in a management location

Loopback interfaceA loopback 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 exiconnector falls out, or if the device at the other end of the cable fails for areason. The interface then shuts down and is removed from the routing taHaving an interface that always exists within a router is very useful for thfollowing reasons:

1 If a tunnel is set up between two router interfaces and one of the interffails, the tunnel will fail. However, when the tunnel is set up between tloopback interfaces, if the normal route fails the tunnel will be re-routeanother route exists and will not fail.

2 If a Telnet session is used to configure a router, if the interface goes dthat has the IP address to which the Telnet session is referenced, it wibe possible to access the router unless the IP address of an alternatiinterface is known. As the loss of an interface or part of the network iexactly the kind of eventuality which requires reconfiguration of a routthis is undesirable. If Telnet sessions are set up to access the router vloopback interface and any connection is up, the session will work.

3 Other interfaces can safely be referenced to the loopback interface. Tknown as an unnumbered interface. This applies only to point-to-poininterfaces (that is, not an Ethernet port). This reduces the number of addresses needed and starts make router appear to have an address

LAN

Loopback 0:

Ethernet 0:

Loopback 0:

Eth 1

Seriallinks

Eth 0

Loopback 0:

Eth 1

Seriallinks

Eth 0

LANLAN

Seriallinks

R3

R2R1

192.168.2.0 192.168.3.0

Network 192.168.1.0Subnetwork 192.168.1.0

192.168.1.33 192.168.1.49

192.168.1.17

192.168.1.1

Network: Network:

192.168.1.2

192.168.1.3

192.168.1.2.1 192.168.1.3192.168.1.3.1


Protocols 8-9

8

ore r to

ed o ross can the

ar the

OSI the route e

than each interface. This starts to make the IP addressing structure msimilar to the OSI addressing structure and makes the network easievisualize.

Tunnel interfaceTunnelling is a method by which non-IP traffic (such as OSI) can be routacross networks that support only IP. A tunnel can be set up between twrouters, whereby non-IP traffic is encapsulated into an IP format, sent acthe tunnel, and decoded at the other end. In this way, two OSI networks be linked together across an IP-only network. The two routers advertise connection to the OSI networks as if they are directly connected. The IP packets which are used to transport the OSI through the IP network appesame as any other IP packet to the IP network. Figure 8-5 illustrates the concept.

Figure 8-5Tunnelling

An OSI-over-IP tunnel can also be used to provide extra protection to anlink within a network which does support OSI. Two routers can be linkedtogether both by a normal OSI link and an OSI tunnel. If the link betweenrouters fails and an alternative OSI route cannot be established but an IPcan, the OSI will be routed through the IP tunnel. This is dependent on thtunnel being configured correctly as advised here. Refer to the following

OSI

OSI

OSI

IP

OSIIP

Router (OSI & IP)

Router (OSI & IP)

IP only network

OSI packet encapsulatedwithin IP packet

OSI packet encapsulatedwithin IP packet

OSI packet

OSI packet

OSI network

OSI network

Tunnel (virtual

path visible to OSI)


8-10 Protocols

s in I

hich ured

n IP ce the

this

the is

he

it nd

s

s

ple A is

te

notes and the DCN Commissioning Guide NTP323-4061-210 for more details. This is a standard DCN configuration, as a single failure of a linkbetween two routers in the same OSI area compromises communicationthat area. A correctly configured OSI tunnel successfully protects the OSarea against failure of this link. Refer to OSI protocol addressing on page 13-4.

Note: The router at each end of the tunnel must support the protocol wis being sent across the tunnel. It must have a tunnel interface configand referenced to the router at the other end of the tunnel.

Note: The tunnel is configured between two IP addresses. Normally aaddress is the address of a specific interface. Therefore, if the interfagoes down, the tunnel will fail even if another path still exists betweentwo routers that form the tunnel. For this reason, Nortel strongly recommends that tunnels are set up between loopback interfaces, astype of interface never goes down. See Loopback interface on page 8-8.

Note: A tunnel can be configured as an unnumbered interface, reducingnumber of IP addresses required. Nortel strongly recommends that itunnumbered and referenced to the loopback interface.

Note: Each router can be anywhere within its respective OSI networkwhere there is an IP path to the other router which forms the tunnel. Trouters do not need to be at the edge of the part of the network whichsupports OSI.

OSI protocol addressingThis section briefly explains some of the concepts of OSI addressing as relates to Nortel SDH DCN. Many features of OSI are not used in DCN aare not discussed here.

AddressingAn IP address points to an interface or network, whereas an OSI addrespoints to a device such as a router or SDH NE. OSI addressing is more structured and controlled than IP addressing. The IP addressing schemerecommended in this document are more structured than many, as the schemes attempt to mimic the structures used for OSI addressing. The recommended IP addressing method splits the DCN into areas; the examused in Chapter 9 uses one management area and four SDH NE areas. different IP network address is used for each area. This type of approachnot absolutely necessary to make IP function correctly, but it cannot be avoided when designing OSI networks.

Every device which supports ISO has a unique OSI address.

OSI addresses have many different components, including IDP and DSP(further subdivided into AFI, IDI, HO-DSP, SID, and SEL). Refer to OSI protocol addressing on page 13-4 for explanation of these terms. The comple


Protocols 8-11

8

. To

:

med

nes P is sers

. Do e

rtel

rks

e

way:

C

as

sing his

OSI address is called an NSAP or NET, depending on the values in SELunderstand OSI addressing well enough to design SDH DCN, it is only necessary to consider the OSI address as consisting of three main parts

• area address

— This is the only part the network designer needs to consider.

• system ID

— In the case of Nortel DCN, the system ID for any device is the hardware address or MAC address. The MAC address is programinto the device in the factory and either cannot or should not be changed.

• selector (SEL)

— Nortel equipment usually uses the selector “01”. The selector defiwhether the complete OSI address is an NSAP or a NET. An NSAan OSI address used for the purpose of communicating between uor applications. A NET is an OSI address used for routing purposesnot change the selector. The network designer does not need to bconcerned with it.

OSI supports many different schemes for assigning the area address. Norecommends only two schemes or formats:

1 the “data country code” (ISO DCC) format, which is to be used in netwothat contain more than one area and

2 the “local” format, which can be used only in smaller networks with onarea. #

One area can contain no more than 150 SDH NEs.

An OSI address that uses ISO DCC format is expressed in the following

39.076F.8012.3456.0000.dddd.aaaa.eeee.eeee.eeee.ss

This address has the following components:

• 39

— This is called the AFI and specifies that the address uses ISO DCformat.

• 076F

— This is called the IDI and specifies that the country is Brazil (usedan example). See Data country codes on page 14-13 for a complete list of country codes.

• 80

— This is called the DFI and specifies that DSP format of OSI addresis used. No other ISO DCC format is recommended by Nortel so tis always set to “80”.

• 123456


8-12 Protocols

for ay

sed

02”,

is

ter seen is is

There in he

— This is called the organization field. The correct code must be usedthe organization that owns the network. Use of the incorrect code mwell have legal implications. The code is allocated by a relevant authority in each country.

• 0000

— This is reserved for interdomain routing and is always “0000”.

• dddd

— This is the routing domain (RD). Use an RD which is not already uby the owners of the network.

• aaaa

— This is the area (for example, “0001” for the management area, “00“0003”, “0004”, and “0005” for SDH NE areas).

• eeee.eeee.eeee

— This is the MAC address or hardware address. Leave this address unchanged.

• ss

— This is the selector. Usually it is “01” for Nortel equipment. Leave thaddress unchanged.

Often a shortened version of this format is seen. This is three bytes shorand has the two reserved bytes and one of the RD bytes removed. This isin some management areas as it is a format used by EC-1 Release 6. Thbecause EC-1 Release 6 supports area addresses up to only 10 bytes.

To use ISO DCC format, the network designer follows Procedure 8-2.

Procedure 8-2Using ISO DCC format

Step Action

1 Obtain the correct country code.

2 Obtain the correct organization code. If the network owners do not already have one, approach the relevant authority.

3 Approach the network owners for a unused RD.

4 Analyze the network and split it into areas. Allocate area codes to each part of the network.

—end—

Nortel recommends that OSI areas correspond to IP network addresses. is no technical necessity for this, as IP and OSI protocols do not interactany way. However, this scheme makes the network design quicker and tnetwork easier to understand.


Protocols 8-13

8

of orks

host

ers).

le of ting

vel-2

hich el-2

t to his

y

st be

ity

the ss:

ess to as

An OSI address which uses the local format is expressed as

49.0000.eeee.eeee.eeee.ss

The network designer cannot change any part of this address. This type address does not have an area selector and thus is suitable only for netwof less than 150 SDH NEs. Local format addresses can be used without approaching any higher authority.

ProtocolsOSI supports two types of systems, ESs and ISs. An ES is equivalent to ain IP, and an IS is equivalent to a router.

Two OSI protocols exist:

• IS-IS. This protocol is used between two ISs (that is, between two routMost SDH NEs support IS-IS.

• ES-IS. This protocol is used (1) to connect between an IS that is capabrouting and an ES (such as a TN-1P or ATU) that is not capable of rouor (2) for communication between two ESs.

Two ISs connected together and running IS-IS can use Level-1 and/or Lerouting.

• Level-1 routing is used by devices to route within an OSI area.

• Level-2 routing is used to route packets between OSI areas. Routers ware connected together but in different OSI areas should have only Levrouting enabled on the interfaces which connect them together.

• Every interface on a router can be configured to run Level-1 and/or Level-2 routing. Generally interfaces within an area are configured tosupport both Level-1 and Level-2 routing, and interfaces which connecrouters in other areas are configured to support only Level-2 routing. Tmust be specified by the network designer for every interface of everrouter which supports OSI routing.

• SDH NEs which are connected together but in different OSI areas muprevented from exchanging routing information. This is achieved by switching off or disabling the DCC between them. It is the responsibilof the network designer to ensure that this is carried out.

Device configurationsDevices which require OSI configurations include EC workstations, SDHNEs, and routers which support OSI.

• Devices which require no configuration

— Most Nortel SDH NEs require no configuration, provided that the routers are correctly configured. The SDH NEs automatically learncorrect ISO DCC address from the routers via the following proce

– Nortel SDH NEs are shipped configured with an OSI local addrof the form 49.0000.eeee.eeee.eeee.ss which is often referredthe default address.


8-14 Protocols

es. a

as.

and

:

d to

he

e of is edge vices e the s e the

nt ich

essing

– DCN routers in SDH NE areas are configured with two addressOne is the ISO DCC (that is, 39.xxxx.....) address, the other is local address (that is, 49.0000.eeee....).

– Due to a feature of the IS-IS protocol, ISs which are connectedtogether and have one area address in common will pool all oftheir area addresses. In this way the SDH NEs will learn the correct area address from the routers.

— Manual configuration of SDH NEs will be required to switch off theDCC of interfaces which connect to NEs which are in different are

• Devices which require address entry

— Certain devices (including most of the element controllers, TN-1P, ATU) must have the OSI area address manually entered.

• Devices which require detailed configuration

— The routers in the network will require the following configurations

– Local address of 49.0000.eeee.eeee.eeee.00

– ISO DCC address of 39.xxxx.xxxx.xxxx.0000.dddd.aaaa.eeee.eeee.eeee.00, whereaaaa defines the OSI area. This is not necessary with small networks with only one OSI area.

– Level-2 routing only enabled on interfaces which are connecterouters in other OSI areas.

– Level-1 and Level-2 routing enabled on interfaces which are connected to routers and NEs in the same OSI area.

– OSI over IP tunnels configured between routers which are in tsame OSI area.

— OSI tunnels are used to protect the OSI network in the specific casthe link breaking between two routers in the same OSI area. This necessary because in the event of the link breaking, a router on theof the area advertises to the other areas that it has a route to all dewith the same area address (using Level-2 routing). However, if throuter receives a packet destined for a device on the other side ofbreak, it has no route for it and the OSI packet is lost. The router iadvertising routes to devices which it cannot reach. This is becausCisco routers do not support the IS-IS protocol Partition Repair function. In the event of such a break, the IP protocol will re-routecorrectly. Therefore, if a properly configured OSI over IP tunnel ispresent, the routers will reach each other through the tunnel.

— OSI tunnels can also be used where the customer requires differeparts of the DCN to be connected via an existing data network, whoften will not support OSI.

Example configurationThe same examples as those used earlier in Chapter 8 to explain IP addrare now used to explain OSI addressing.


Protocols 8-15

8

:

l-2

ging

01

ith.

ter, h nd


For each router the following is required to write the router configurations

— an OSI area address

— circuit-type for each interface (that is, Level-1 and Level-2, or Leveonly)

— metric for each interface

For the purposes of this example, the area will be part of a network belonto an imaginary organization in Brazil.

— The country code for Brazil is 076F.

— The organization code for our imaginary company is 123456.

— The reserved field is fixed at 0000.

— This is the first OSI network installed into this company, so RD 00can be used.

— This is area 0002. Area 0001 will be the management area.

The OSI address for the two routers will therefore be

39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.00

where eeee.eeee.eeee is the MAC address which the router is shipped w

The default configuration for all interfaces is to allow Level-1 and Level-2routing. Enter the commands into the serial port configuration of each rouwhich leaves the area to allow Level-2 routing only. The serial ports whicconnect the two routers within the area must be left as default (Level-1 aLevel-2 enabled).

Considerations due to SDH NE configuration:

• The routers must be configured with a Level-1 priority of 65.


LAN LAN

Serial link

Loopback0Loopback0

Ethernet0 Ethernet0

Tunnel


8-16 Protocols

with

uter, h

ted etric

een

uter

this,

and

SI

ddress

— This is because the SDH NEs have a priority of 64. In accordance the IS-IS protocol, whichever IS has the priority set numerically highest is the “designated router”. Setting the routers to a Level-1priority of 65 guarantees that one of the routers is the designated ronot one of the SDH NEs. The designated router is the router whicadvertises the LAN connectivity to all of the other routers and SDHNEs in the OSI area.

• The Ethernet ports must be configured with a Level-1 metric of 63.

• The serial ports must be configured with a Level-1 metric of 20.

— The maximum that the metric can be set to is 63. Packets are routhrough the path that has the lowest total metric. Set the router’s m

– high enough to be unattractive to packets which are sent betwOPC pairs in a TN-16X ring

– low enough to encourage traffic to a cross connect near to a roto follow a direct path through the router, rather than using theSDH network.

Setting 63 on the Ethernet ports and 20 on the serial ports achievesprovided that OPCs are on opposite sides of the TN-16X ring.

• Configure the OSI-over-IP tunnel with a Level-1 metric of 21.

— The tunnel is a backup for the serial link between the two routers must have a higher metric than the serial link.

• The routers must also be configured with the Nortel SDH NE default Oaddress

49.0000.eeee.eeee.eeee.00, where eeee.eeee.eeee is the MAC awhich the router is shipped with.

Figure 8-7 shows the area as configured for OSI.


.


LAN LAN

Serial link

Loopback0Loopback0

Ethernet0 Ethernet0

Tunnel

L1/L2

L1/L2

L1/L2

L2 onlyL2 only

R1: 39.076F.8012.3456.0001.0001.0002.1C3F.2B95.780E.00

R2: 39.076F.8012.3456.0001.0001.0002.34A0.8C45.98F4.00

R1 R2

49.0000.1C3F.2B95.780E.00

49.0000.134A0.8C45.98F4.00


Protocols 8-17

8

t that

NE

NE

NE

NE

econd

The routers in all of the other areas are configured in the same way, excepthe area addresses vary as follows:

— 39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.ss for the management area

— 39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.ss for SDHarea one

— 39.076F.8012.3456.0000.0001.0003.eeee.eeee.eeee.ss for SDHarea two

— 39.076F.8012.3456.0000.0001.0004.eeee.eeee.eeee.ss for SDHarea three

— 39.076F.8012.3456.0000.0001.0005.eeee.eeee.eeee.ss for SDHarea four

Configure the routers with a second address as follows:

— Router in management area connected to EC-1 Release 6 has a sOSI address of 39.076F.8012.3456.0100.01ee.eeee.eeee.ee00.

— Routers in SDH NE areas have a second address of 49.0000.eeee.eeee.eeee.00.

end of chapter


9-1

9

ates nt.

n o and on

Example 9-Overview

This section contains a worked example of an SDH DCN design. It illustrhow to apply the processes and tutorial information given in this docume

IntroductionUse the process defined in Chapter 3 to design an SDH DCN. The following stages are listed in Chapter 3:

1 SDH network analysis

2 SDH management domain definition

3 Power supply type

4 Location definition

5 Generate component list

6 Configuration

7 Installation information

No information on firewalls is included in this example, as implementatiocould be achieved in a number of ways. As a general rule, make access tfrom an external network either via a serial interface or from a dedicatedEthernet port, but never from an Ethernet hub port. For further informationfirewalls, see Firewalls on page 6-3 or SDH DCN Commissioning Guide, NTP 323-4061-210, Section 6.

SDH network analysisA network is provided for the purposes of this example in Figure 9-1.

The following information is collected in accordance with Chapter 3:

• quantities

— TN-16X NEs: 33

— STM-16 regenerators: 13

— TN-4Xs: 11

— TN-1Xs: 193

• interfaces


9-2 Example

ces s l .

— The six rings are composed of optical interfaces. Most of the interfabetween TN-1X and TN-16X are electrical interfaces. Connectionbetween TN-4X and TN-16X are a mixture of electrical and opticainterfaces. An SDH radio line system forms some of the interfaces

• topology

— The northwest ring contains 68 NEs.

— The northeast ring contains 70 NEs.

— The central ring contains 27 NEs.

— The southeast ring contains 14 NEs.

— The southwest ring contains 51 NEs.

— The radio system contains 23 NEs.

— Additional NEs link the rings together.


Exam

ple 9-3

Figure

9-1N

etwork exam

ple

TN-16X

TN-4X

TN-1X/1C

SDH

Radio

STM-16

TN-16-4FR

Regenerator

Northeast ring

Data C

omm

unications Netw

orksP

rovisioning Guide

9

Northwest ring

Centralring

Southwest ring

Southeast ring

9-4 Example

rge

rs.

arate for y is the al of d in

g

SDH management domain definitionUsing the guidelines from Chapter 3, this SDH network is defined as a laSDH network (from a DCN perspective), as it contains 250 NEs.

DCN topologyThe first action is to group the SDH NEs into areas and allocate the routeBase the areas around STM-16 rings and include a management area. The large sizes of the northwest and northeast rings make them obvious separeas. The remainder of the system will be 112 NEs. Given that the limit an area is 150 NEs, it is prudent to have two areas. The best connectivitbetween southwest and southeast as one area, and the central ring and radio system as another. The addition of a management area gives a totfive areas. The TN-4X NEs used to connect STM-16 rings are all includethe central/radio area.

Arrange the four areas in a chain. Connect each end of the chain to a management area.

Figure 9-2Management domain

Management areaThe following network managers are needed:

• TN-1X EC: 4, each of which can control up to 64 NEs

• TN-4X EC: 2, each of which can control from 10 to 30 NEs (dependinupon platform). One is provided in each management location.

• NRM: 2, 1 in each management location

• OPC: 10, 2 per STM-16 ring/radio system


SDH Management Area

SDH NEArea 1

SDH NEArea 2

SDH NEArea 3

SDH NEArea 4

All inter- or intra-area links are E1 (2 Mbit/s).


SDH Management Domain


Example 9-5

9

is

be ork.

n the

re

The link between the management locations is:

Number of NE area chains * 1 Mbit/s = 1Mbit/s, or 2 Mbit/s, whichevergreater.

Therefore, a single 2 Mbit/s link is used. The management locations cananywhere where there are two 2 Mbit/s links available into the SDH netw

Figure 9-3 SDH management area

Notes:

• One TN-1X EC is capable of controlling 64 NEs.

• One TN-4X EC is capable of controlling 10 to 30 NEs (depending upoplatform); two are used in this network to protect the network againstfailure of one management location.

• OPCs are deployed in pairs. One pair can control up to 18 STM-16 regenerators and 16 TN-16X NEs in a ring (24 NEs otherwise).

• NRM is scalable to control an extremely large number of NEs. Two aused in this network to protect the network against the failure of one management location.

SDH NE areasSDH NE area one consists of the northwest STM-16 ring. It requires tworouter locations. Each router location contains an OPC, a router, and two2 Mbit/s connections.

TN-1X EC TN-1X EC

TN-4X EC

TN-1X EC TN-1X EC

TN-4X EC

E1

OSI (L1/L2) and IP

Router (2501/5/7) Router (2501/5/7)


SDH Management Location SDH Management Location

OSI and IP OSI and IP

E1


M

NRMNRM

MM M

to SDH NE area 1 to SDH NE area 4


9-6 Example

tors.

sent

ta

ve

t be

hed

H direct

Figure 9-4SDH NE area one

Notes:

• An OPC pair controls up to 16 TN-16X NEs and 18 STM-16 regenera

• Place OPCs on opposite sides of the ring. This ensures that packets between the OPC use the DCN rather than the ring.

• Connect every OPC directly to a router.

• Nortel recommends that DCN equipment be DC powered.

• Management packets are communicated to the TN-1X NEs via the dacommunications channel (DCC) between TN-16X and TN-1X. This channel exists for both STM-1 electrical and optical interfaces.

• No more than two TN-1Xs can be connected to the same LAN and hathe DCC link to a shared TN-16X. The first two may have the DCC to theTN-16X active and be connected to a LAN; after that, the others musconnected via either the DCC or the LAN but not both.

• The DCC of the TN-16X that connects to the next area must be switcoff.

SDH NE area two consists of the northeast STM-16 ring. The DCN is identical to that of area one.

SDH NE area three includes an STM-16 ring, an STM-1 ring, and an SDradio system. Three router locations are required, as each OPC requires connection to a router.

Northwest ring

Router 1

OPC

LAN

Router 2

DCC

OPC

LAN

M

M

E1 to area 2

CNET

E1 to Router 1

M

M E1 to management area

E1 to Router 2

CNET

No DCC


Example 9-7

9

tors.

sent

ve the t be

hed

, r

Figure 9-5SDH NE area three

Notes:


• Place OPCs on opposite sides of the ring. This ensures that packets between the OPC use the DCN rather than the ring.



• Management packets are communicated to TN-1X NE via the DCC between TN-16X and TN-1X. This channel exists for both STM-1 electrical and optical interfaces.

• No more than two TN-1Xs can be connected to the same LAN and hathe DCC link to a shared TN-16X. The first two may have the DCC to TN-16X active and be connected to a LAN; after that, the others musconnected via either the DCC or the LAN, but not both.

• The DCC of the TN-4Xs that connect to the other areas must be switcoff.

• If TN-4X electrical interfaces are used to connect to TN-16X or TN-1Xthere is no DCC. The NEs must be connected using a LAN (except foconnections to other areas when DCC is not wanted in any case).

• Connections between routers are as follows:

— area 2 to router 1: level 2 only

— router 1 to router 2: level 1/level 2

— router 2 to router 3: level 1/level 2

— router 3 to area 4: level 2 only

Central

ring

MM

E1toR1

E1toR3

LAN

OPC

OPC

M

M

E1 to Router 2

E1 to area 2

LAN

CNETCNETCNET

No DCC No DCC

No DCC

No DCC

Router 3

OPC

LAN

MME1 to area 4

CNETE1 to Router 2

Router 2

Router 1

OPC


9-8 Example

uter

ring; east link DH

loss

tors.

sent

C

ve the t be

hed

SDH NE area four includes an STM-16 ring and an STM-4 ring. Three rolocations are required.

Figure 9-6SDH NE area four

Notes:

• Router 3 is required to provide a second path for DCN to the southeastotherwise the failure of the SDH link between the southwest and southlink would result in loss of management of the southeast link. The E1 from router 3 to the management area must be implemented via the Slink to the central ring; the E1 link from router 3 to router 2 must be implemented via the SDH link to the southwest ring. This prevents the of any one SDH link from isolating router 3.


• Place OPCs on opposite sides of the ring. This ensures that packets between the OPCs use the DCN rather than the ring.



• Management packets can be communicated to TN-1X NE via the DCbetween TN-16X and TN-1X. This channel exists for both STM-1 electrical and optical interfaces.

• No more than two TN-1Xs can be connected to the same LAN and hathe DCC link to a shared TN-16X. The first two may have the DCC to TN-16X active and be connected to a LAN; after that, the others musconnected via either the DCC or the LAN but not both.

• The DCC of the TN-16X that connects to the next area must be switcoff.

Southwest ring

Southeastring

Router 1

OPC

LAN

M

M E1 to area 3

E1 to Router 2

CNET

Router 2

OPC

LAN

M

M

E1 to management area

CNET

E1 to Router 1

No DCC No DCC

Router 3M

M

LAN

E1 to Router 3

E1 toRouter 2


Example 9-9

9

ings

no s to

12

sing

s not

rmat

area ee.00

area ee.00

area

area ee.00

local

• In this example, an optical interface must be used to connect the two rbetween TN-16X and TN-4X. The TN-4X electrical interface does notsupport a DCC channel, and the TN-16X does not have a LAN port.

• If TN-4X electrical interfaces are used to connect to TN-16X, there isDCC. The NEs must be connected using a LAN (except for connectionother areas when DCC is not wanted in any case).

• E1 channels should travel by different routes to protect the DCN. VC-paths need to be diverse to carry E1s.

AddressingThe second action is to assign addresses to the DCN.

OSI addressesFor the purpose of this example, the ANSI country code format is used, uan imaginary organization in Brazil. The OSI address is of the form

39.076F.8012.3456.0000.dddd.aaaa.eeee.eeee.eeee.00

where

• dddd is the domain, 0001 is used

• aaaa is the area, 0001 through 0005 is used

• eeee is the MAC address of any given device in the network. This doeneed to be specified, as it usually cannot be changed.

Refer to OSI protocol addressing on page 13-4 for additional information on address components.

Allocating the OSI address is now simple. It is:

• 39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00 for the management area. No local format OSI address is needed. Use local foOSI addresses for TN-1X Release 6.

• 39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.00 for SDH NEone, with a second local format OSI address of 49.0000.eeee.eeee.eefor the routers only.

• 39.076F.8012.3456.0000.0001.0003.eeee.eeee.eeee.00 for SDH NEtwo, with a second local format OSI address of 49.0000.eeee.eeee.eefor the routers only.

• 39.076F.8012.3456.0000.0001.0004.eeee.eeee.eeee.00 for SDH NEthree, with a second local format OSI address of 49.0000.eeee.eeee.eeee.00 for the routers only.

• 39.076F.8012.3456.0000.0001.0005.eeee.eeee.eeee.00 for SDH NEfour, with a second local format OSI address of 49.0000.eeee.eeee.eefor the routers only.

Notes:

1 Routers in SDH NE areas are configured with two OSI addresses: a format OSI address and an ISO DCC OSI address.

2 The local format OSI address is always 49.000.eeee.eeee.eeee.00.


9-10 Example

only

te in ame

two

cess.

ation

rivate

IP

, and

r the

ions n

3 Routers in an area with no SDH NEs (that is, management areas) needthe ISO DCC OSI address.

4 Send the installation engineer instructions for each serial interface. Stathe instructions whether the port is connected to another router in the sOSI area (L1/L2) or to a router in a different OSI area (L2 only).

5 Provide an IP tunnel between the routers to protect the link between routers in the same OSI area. See IP addresses for more details.

IP addressesAssigning the IP addresses and subnetwork masks is a more involved proFor a detailed description of IP networking and subnetworking, see IP networks, subnetworks, and subnetwork masks on page 8-2.

To assign the IP addresses and subnetwork masks, the following informis required:

• the number of routers in each area

• the number of IP devices that are connected to each router (that is, workstations, NRM, element controller, OPC)

This example uses the IANA class C addresses, which are reserved for pnetworks. These are addresses 192.168.0.0 to 192.168.255.255.

Network addresses are chosen to align with the OSI areas; therefore, theaddresses are:

• 192.168.1.0 for management area network address

• 192.168.2.0 for SDH NE area one network address

• 192.168.3.0 for SDH NE area two network address

• 192.168.4.0 for SDH NE area three network address

• 192.168.5.0 for SDH NE area four network address

The management area in this example contains two routers and eight workstations. Each router has a loopback interface, an Ethernet interfacetwo serial interfaces. The serial interfaces are unnumbered; therefore, subnetworks are required for the loopback interfaces and the Ethernet interfaces. To allow for expansion, three bits of the last eight are used fosubnetwork mask.

• The subnetwork mask is 255.255.255.224 for all routers and workstatin the management area. In decimal, 224 is equivalent to 11100000 ibinary (that is, the three most significant bits of the last byte of the address).

• The eight available subnetworks are

— 192.168.1.0 (last byte 00000000)

— 192.168.1.32 (last byte 00100000)

— 192.168.1.64 (last byte 01000000)

— 192.168.1.96 (last byte 01100000)


Example 9-11

9

(ID).

s of 24.

ress

24

ress

ress

24

o o not of at

er

— 192.168.1.128 (last byte 10000000)

— 192.168.1.160 (last byte 10100000)

— 192.168.1.192 (last byte 11000000)

— 192.168.1.224 (last byte 11100000)

• For each subnetwork, this leaves five bits to assign the host identifier

• Four of the eight subnetworks are used as follows:

— subnetwork 192.168.1.0 for router 1 loopback interface. The addresthe interface is 192.168.1.1 with subnetwork mask 255.255.255.2

— subnetwork 192.168.1.32 for router 1 Ethernet interface. The addof the interface is 192.168.1.33 with subnetwork mask 255.255.255.224. The addresses of the hosts are

– NRM: 192.168.1.34 with subnetwork mask 255.255.255.224

– TN-4X EC: 192.168.1.35 with subnetwork mask 255.255.255.2

– TN-1X EC1: 192.168.1.36 with subnetwork mask 255.255.255.224


— subnetwork 192.168.1.64 for router 2 loopback interface. The addof the interface is 192.168.1.65 with subnetwork mask 255.255.255.224.

— subnetwork 192.168.1.96 for router 2 Ethernet interface. The addof the interface is 192.168.1.97 with subnetwork mask 255.255.255.224. The address of the hosts is

– NRM: 192.168.1.98 with subnetwork mask 255.255.255.224

– TN-4X EC: 192.168.1.99 with subnetwork mask 255.255.255.2



• SDH NE areas tend to have more routers, but very few host IDs are required. Generally each Ethernet port is connected to only one or twOPCs. Most of the devices connected to a router in an SDH NE area dsupport IP. In the case of this particular example, a subnetwork mask least four bits from the last byte is recommended. This will make the subnetwork mask 255.255.255.240, allowing up to 16 subnetworks pnetwork address, which is generally sufficient for 8 routers. The 16 available subnetworks for SDH NE area one are

— 192.168.2.0 (last byte 00000000)

— 192.168.2.16 (last byte 00010000


9-12 Example

t or

ay

k

unnel link

uter

sts

— 192.168.2.32 (last byte 00100000)

— 192.168.2.48 (last byte 001100000

— 192.168.2.64 (last byte 01000000)

— 192.168.2.80 (last byte 01010000)

— 192.168.2.96 (last byte 01100000)

— 192.168.2.112 (last byte 01110000)

— 192.168.2.128 (last byte 10000000)

— 192.168.2.144 (last byte 10010000)

— 192.168.2.160 (last byte 10100000)

— 192.168.2.176 (last byte 10110000)

— 192.168.2.192 (last byte 11000000)

— 192.168.2.208 (last byte 11010000)

— 192.168.2.224 (last byte 11100000)

— 192.168.2.240 (last byte 11110000)

For each subnetwork, this leaves four bits to assign host IDs. For each subnetwork, the last four bytes are 0001 for the interface (either Etherneloopback), then 0010 for the first OPC, and so forth.

Notes:

1 Large management areas for systems containing thousands of NEs mwell require multiple network addresses. Refer to Designing addressing scheme for large SDH networks on page 8-1 for such a scenario.

2 Provide large amounts of room for expansion of the network with IP networks.

3 All serial ports should be unnumbered and referenced to the loopbacinterface.

4 Links between routers that are in the same OSI area should have a tinterface configured between them in order to protect the OSI againstfailure. See Tunnel interface on page 8-9 for further information.

5 The tunnel should be unnumbered and referenced to the loopback interface.

6 The destination of the tunnel should be the loopback interface of the roat the other end of the tunnel.

7 Enable the tunnel for level 1 and level 2 OSI routing.

8 Do not use the host ID of all zeros or all ones.

9 Choose suitably descriptive host names for the routers. Nortel suggelinking the name to the physical location of the router.


Example 9-13

9

are ce

e to

Power supply typeAll DCN devices (routers, modems, and so forth) are DC powered if theylocated with SDH NEs. They are mains AC powered if they are in an offienvironment (that is, with workstations in the management area).

Consider power supply for each location so that the correct part can be purchased.

Location definitionOne of the router locations from the northwest ring is used as an examplillustrate the connectivity at the location. This location consists of one TN-16X, four TN-1Xs, an OPC, a router, and two G703 modems. The following are required:

• LAN to connect all the TN-1Xs, the router, and the OPC

• two E1 connections (75Ω or 120Ω).

• power for all DCN components

This is achieved by using a system as shown in Figure 9-7.

Figure 9-7System illustrating connectivity at location

Router

OPC

M

CNET

STM-1E ports

withDCC

withDCC

noDCC

noDCC

TN-16X

TN-1X

TN-1X

TN-1X

TN-1X

M Serial 0 Serial 1

Ethernet portsE1E1

Transceiver10base-T

straight cable

straight cable

straight cable

straight cable

X 21


9-14 Example

ct

ther two

inal Cs.

AN

the

Notes:

1 TN-1Xs and TN-4Xs require an AUI to 10base-T transceiver to connetheir NE LAN ports to the router LAN port.

2 48 V hub is not coded. Use a router with a built-in hub (Cisco 2505).

3 G703 modems are switchable between 75Ω or 120Ω. For the purposes of this example, 75Ω will be used.

4 If a hub is available at the site, connect the LAN ports of the NEs togeusing the hub instead of using the DCCs. Switch on the DCCs of only of the NEs connected to the hub.

5 Leave one hub port free for plugging in diagnostic equipment or termin the future. If there are not enough hub ports for all the NEs, use DC

6 On sites with no hubs, switch on the DCC of all NEs.

7 Use two transceivers and a crossover LAN cable to connect two AUI Lports.

Generate components listA components list is generated in Figure 9-8 based on the equipment at location described in the preceding section.

Figure 9-8Generating a components list

Cisco 2505 DC OSI

OPC

M

CNETTN-16X

TN-1X

TN-1X

TN-1X

TN-1X

M Serial 0 Serial 1

Ethernet ports

Transceiver

OPC Ethernet cable

LAN cable

LAN

LAN cable

LAN cable

Transceiver

Transceiver

Transceiver

G703 modem DC

75Ω BNC

straight cable

straight cable

straight cable

straight cable

cablestraight cable


Example 9-15

9

d so

t,

Complete a site survey to ascertain mechanical details, cable lengths, anforth. Equipment at SDH NE locations are normally mounted in shelves. The installation team selects mechanical parts after the site survey.

Table 9-1 details all the DCN components needed for this site.

Other required parts include:

• four 75Ω BNC cables to connect G703 modems to TN-1X

• suitable cable for 48 V DC power connections

• mechanical fixings and brackets

See SDH DCN components list, Release 2 on page 14-7 for a complete components list.

Installation informationThis section describes an example of the format for the exchange of information from the DCN designer to the installation team. For each parinformation needs to include

• location

• addressing

• interfaces

• configuration

• connectivity

Table 9-1Needed DCN components

Description Part number Quantity

Cisco 2505 OSI DC router NTJM01HA 1

G703 modem DC and serial cable NTJM01TA 2

AUI to 10base-T transceiver NTJM01VA 4

20 metre LAN cable 32YCN00727CAA 4

20 metre OPC LAN cable NT7E44JE 1

—end—


9-16 Example

Table 9-2Example location and connectivity table

Location Name Part Power supply

Serial Ethernet Leased lines to locations

NW07 Router 1 2505 OSI DC DC 2 x G703 modem 75Ω

4 x TN-1X LAN1 x OPC LAN

NW13ML01

NW13 Router 2 2505 OSI DC DC 2 x G703 modem 75Ω


NW07NE02

NE02 Router 1 2505 OSI DC DC 2 x G703 modem 75Ω


NW13NE08

NE08 Router 2 2505 OSI DC DC 2 x G703 modem 75Ω


NE02CR12

CR05 Router 3 2505 OSI DC DC 2 x G703 modem 75Ω

4 x TN-4X LAN1 x TN-1X LAN 1 x OPC LAN

CR09SW10



CR12CR05



CR09NE08

SW03 Router 2 2505 OSI DC DC 2 x G703 modem 75Ω


SW10SE02

SW10 Router 1 2505 OSI DC DC 2 x G703 modem 75Ω


SW03CR05

SE02 Router 3 2505 OSI DC DC 2 x G703 modem 75Ω

4 x TN-1X LAN1 x TN-4X LAN

ML02SW03

ML01 Router 1 2501 OSI DC AC 2 x G703 modem 75Ω

Hub 1 NW07ML02

ML01 Hub 1 AT-MR820TR AC NA Router 1NRMTN-4X EC2 x TN-1X EC

ML02 Router 2 2501 OSI DC AC 2 x G703 modem 75Ω

Hub 2 SE02ML01

ML02 Hub 2 AT-MR820TR AC NA Router 1NRMTN-4X EC2 x TN-1XEC

—end—


Example 9-17

9

Table 9-3Example interface/configuration for area 1

Router 1 Router 2

Location ML01 ML02

Hostname ML01A1R1 ML02A1R2

Enable secret password sdhdcn sdhdcn

Telnet password cisco cisco

OSI address 39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00

39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00

IP Network Address 192.168.1.0 192.168.1.0

Loopback 0 192.168.1.1 255.255.255.224 192.168.1.65 255.255.255.224

Ethernet 0 192.168.1.33 255.255.255.224 192.168.1.97 255.255.255.224

Serial 0 Unnumbered loopback 0ML02 L1/L2

Unnumbered loopback 0ML01 L1/L2

Serial 1 Unnumbered loopback 0NW07 L2

Unnumbered loopback 0SE02 L2

Tunnel Unnumbered loopback 0Source loopback 0Destination 192.168.1.65

Unnumbered loopback 0Source loopback 0Destination 192.168.1.1

—end—


Router 1 Router 2

Location NW07 NW13

Hostname NW07A2R1 NW13A2R2

Enable secret password sdhdcn sdhdcn

Telnet password cisco cisco

OSI address 39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.0049.0000.eeee.eeee.eeee.00

39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.0049.0000.eeee.eeee.eeee.00

IP Network Address 192.168.2.0 192.168.2.0

—continued—


9-18 Example

Loopback 0 192.168.2.1 255.255.255.240 192.168.2.33 255.255.255.240

Ethernet 0 192.168.2.17 255.255.255.240 192.168.2.49 255.255.255.240

Serial 0 Unnumbered loopback 0NW13 L1/L2

Unnumbered loopback 0NW07 L1/L2

Serial 1 Unnumbered loopback 0ML01 L2

Unnumbered loopback 0NE02 L2

Tunnel Unnumbered loopback 0Source loopback 0Destination 192.168.2.33

Unnumbered loopback 0Source loopback 0Destination 192.168.2.1

—end—

Table 9-5Example of addressing, area 1

Hostname Location IP Address OSI Address

NRM1ML01 ML01 192.168.1.34 255.255.255.224

NRM2ML02 ML02 192.168.1.98 255.255.255.224

4XEC1ML01 ML01 192.168.1.35 255.255.255.224

39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00

4XEC2ML02 ML02 192.168.1.99 255.255.255.224

39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00

1XEC1ML01 ML01 192.168.1.36255.255.255.224

39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00

1XEC2ML01 ML01 192.168.1.37255.255.255.224

39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00

1XEC3ML02 ML02 192.168.1.100 255.255.255.224

39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00

1XEC4ML02 ML02 192.168.1.101 255.255.255.224

39.076F.8012.3456.0000.0001.0001.eeee.eeee.eeee.00

—end—


Router 1 Router 2


Example 9-19

9

o a
Note: The values shown for passwords in “Example interface/configuration” for area 1 and area 2 are for example only. Set these tunique value for the router or network as soon as possible during configuration.
end of chapter


10-1

10

d a

,

DC le

led.

ack ount ser

that for

two bled

Installation guidelines 10-Guidelines for DCN equipment installation

The guidelines within this handbook are for more general information anguide to other sources for detailed information. Hardware installation handbooks are supplied with each item of equipment (except for Cisco, whose documentation is supplied on CD ROM). Within these handbooksgeneral safety-related information is available, along with more detailed physical installation for wall and rack mounted equipment, mains AC andinput (local safety requirements to take precedent), data connection, cabpinouts, mounting bracket fixing, and so forth.

Prior to installation, Nortel advise a site survey to review the type of environment and racking available in which the equipment is to be instal

Where the quantity of DCN equipment does not justify using a rack, the rmounting brackets supplied with hubs and routers may be used to wall minstead. The use of these brackets is fully described in the appropriate udocumentation.

If a separate rack is required for DCN equipment, the following gives information on Eurocraft racking suitable to house DCN equipment. Note although ETSI racks are used for SDH equipment, they are not suitable Cisco equipment, which must be mounted in a 19 inch rack.

SDH DCN Release 2 offers a variety of racking configurations based on rack heights, 36U and 42U. A basic rack in each size is available preassemfrom the supplier and consists of

• a frame

• horizontal mounts

• panel mounts

• a ventilated top cover with cable entry

• side panels (lockable option available)

• back panel, lockable and removable

• acrylic door

• adjustable feet and castors

• earthing kit

• cable tray


10-2 Installation guidelines

ed eed ndard

gy.

ree

p vers

g e unit

this ft

Items not included in the standard kit and must be specified are

• power distribution blocks

• cantilever trays for modems

For most installations where a normal office environment may be expect(00C- +400C) and the maximum number of DCN components does not exc15, there is a standard list of components which can be added to the stasupplied rack.

If a harsher environment is expected or the number of DCN componentsexceeds 15 or may exceed 15 in the future, consult Installation Technolo

Routers and hubs are “1U” high (a “U” is 44.5 mm). These should be separately front-panel mounted and not stacked on a shelf. There are thmounting positions for each “U” height. It is recommended that a spare mounting position be left between front-panel mounted equipment for ventilation.

Vented top cover with cable entryThis is fitted as standard to the top of both sizes of rack and allows for tocable entry and some ventilation.It is the recommended cover, but top cowithout ventilation and without cable entries are available and coded.

CastorsCastors and feet are supplied with the standard unit. The unit may be manipulated into position with the castors and then made firm by lowerinthe feet. As cables are attached to the unit, it is not recommended that this allowed to remain on castors

Fan unitsNo ventilation should be necessary for most installations. However, if fanassistance is recommended by installation technology three fan units areavailable and coded:

• a top-mounted fan tray

• a withdrawable fan tray

• a front-mounted fan tray

Cantilever shelfThis is the recommended shelf for holding non-front-panel mounted equipment (in Release 2, Fourthtrack/Market Vision modems). An emptyshelf may be left available to hold a laptop or terminal used for fault diagnosis. The height of a Fourthtrack/Market Vision modems is 1U. As is less than the height of a cantilever shelf itself, no space needs to be leabove the shelf for ventilation.

The shelf is 2U high.

Place no more than two modems on one shelf.


Installation guidelines 10-3

10

el-

rt of nt to

ich

ilable

rear panel

ls ft ower

.

Plain shelves are also available in two depths. As it is not possible to panmount a plain shelf (as the height is minimal), a pair of chassis rails are required to give front-to-back support.

Cable trayCables travelling vertically are held by this cable tray, which comes as pathe standard rack. There is a cable tray for each rack height. It is importaattach each cable individually to the tray. If cables are bundled and then attached, the weight of the cable assembly may fall on one connector whwould be unable to take the strain.

DoorsAn acrylic door is supplied as standard, as it would be required by most customers to view equipment indicators. Plain and vented doors are avaas alternatives.

There is also a rear door option as an alternative to the standard panel ifcable access is required. The door is 5U shorter than the standard back and the mounting kit includes a blank 5U panel.

Power distribution panelsThese panels are available for AC- and DC-powered racks.

An AC panel will supply power for a maximum of 8 units with outlets on standard UK 13-amp sockets, which are not fused individually. The paneare mounted vertically at the back of the unit with variants for right and lecable entry. It is recommended that each unit shall have a right and left pblock, which will give a total of 16 outlets

A DC panel will supply power for a maximum of 16 units with outlets protected individually with fuses. It is front-panel mounted and is 3U high

For list of racking options available, see Appendix C.



Table 10-1 lists standard items supplied with equipment.

Table 10-1Standard items supplied with equipment

Manufacturer/ Model

Description

Cisco 2501 (Router)

Power cord, 19” Rack Mtg. Kit, Wall Mt.g Kit, Console cable Kit:- RJ45 to RJ45 Roll Over console cable, RJ45 to DB25 male DCE adaptor, RJ45 to DB25 female DTE adaptor, RJ45 to DB9 female DTE adaptor

Cisco 2505 (Router)

Power cord, 19” Rack Mtg. Kit, Wall Mtg. Kit, Console cable Kit:- RJ45 to RJ45 Roll Over console cable, RJ45 to DB25 male DCE adaptor, RJ45 to DB25 female DTE adaptor, RJ45 to DB9 female DTE adaptor.

Cisco 2507 (Router)

Power cord, 19” Rack Mtg. Kit, Wall Mtg. Kit, Console cable Kit:- RJ45 to RJ45 Roll Over console cable, RJ45 to DB25 male DCE adaptor, RJ45 to DB25 female DTE adaptor, RJ45 to DB9 female DTE adaptor.

Cisco 2509 (Router)

Power cord, 19” Rack Mtg. Kit, Wall Mtg. Kit, Console cable Kit:- RJ45 to RJ45 Roll Over console cable, RJ45 to DB25 male DCE adaptor, RJ45 to DB25 female DTE adaptor, RJ45 to DB9 female DTE adaptor

Cisco 2514 (Router)

Power cord, 19” Rack Mtg. Kit, Wall Mtg. Kit, Console cable Kit:- RJ45 to RJ45 Roll Over console cable, RJ45 to DB25 male DCE adaptor, RJ45 to DB25 female DTE adaptor, RJ45 to DB9 female DTE adaptor

Fourthtrack/Market Vision Micromux SP-1-RA

Internal Power cord, Conversion lead X21 to V35

Allied Telesyn International CentreCOM 208Transceiver

Allied Telesyn International CentreCOM 210Transceiver

Free standing

—continued—



10

Baystack 106 10Base-T Hub with 12 port RJ45 Connectors and -48V DC Power;Hub Order No. CG1001A06

19” Rack Mtg. Kit, Wall Mtg. Kit and documentation

Baystack 107 10Base-T Hub with 24 port RJ45 Connectors and -48V DC Power; Hub Order No. CG1001A07

19” Rack Mtg. Kit, Wall Mtg. Kit and documentation

—continued—


Manufacturer/ Model

Description



Web sitesWeb sites for various DCN equipment manufacturers follow.

Cisco• Cisco Systems home page:

http://www.cisco.com/

Baystack 101 10Base-T Hub with 12 port RJ45 Connectors and 240V AC Power; Hub Order No. CG1001x01*

Power cord, 19” Rack Mtg. Kit, Wall Mtg. Kit and documentation

*The seventh character (x) of the hub order number must be replaced with the proper code to indicate desired product nationalization, as indicated below:

“A” No power cord included.“B” Includes European “Schuko” power cord common in Austria, Belgium, Finland, France, Germany, The Netherlands, Norway, and Sweden.“C” Includes power cord commonly used in the United Kingdom and Ireland.“D” Includes power cord commonly used in Japan.“E” Includes North American power cord.“F” Includes Australian power cord, also commonly used in New Zealand and the People’s Republic of China.

Baystack 102 10Base-T Hub with 24 port RJ45 Connectors and 240V AC Power;Hub Order No. CG1001x02*

Power cord, 19” Rack Mtg. Kit, Wall Mtg. Kit and documentation

*The seventh character (x) of the hub order number must be replaced with the proper code to indicate desired product nationalization, as indicated below:

“A” No power cord included.“B” Includes European “Schuko” power cord common in Austria, Belgium, Finland, France, Germany, The Netherlands, Norway, and Sweden.“C” Includes power cord commonly used in the United Kingdom and Ireland.“D” Includes power cord commonly used in Japan.“E” Includes North American power cord.“F” Includes Australian power cord, also commonly used in New Zealand and the People’s Republic of China.

—end—


Manufacturer/ Model

Description



10

tm

• Cisco Systems site listing 2500 series routers:http://www.cisco.com/univercd/data/doc/cintrnet/prod_cat/80936.htm

• Cisco Systems site for 2500 installation documentation:http://www.cisco.com/univercd/data/doc/cis2500.htm

• Cisco Systems software update documents:http://www.cisco.com/univercd/data/doc/software/11_0/rpcg/csysim.h

Fourthtrack/Market Vision MicroMuxhttp://www.fourthtrack.com/

Multi-Tech Systemshttp://www.multitech.com/

Bay Networkshttp://www.baynetworks.com/Products/

end of chapter


11-1

11

Useful information sources 11-Web sites

The following Web sites provide useful information:

• SDH DCN Home Page:http://47.217.33.140/DCN/

• International Telecommunication Union: http://www.itu.ch/

• International Standards Organization: http://www.iso.ch/

• IEEE Home Page: http://www.ieee.org/

• Cisco Systems Home Page: http://www.cisco.com/

• Cisco Web site listing 2500 series routers Nortel uses:http://www.cisco.com/univercd/data/doc/cintrnet/prod_cat/80936.htm

• Allied Telesyn International Home Page (for the LAN hubs and transceivers): http://www.alliedtelesyn.com/

• Chernikeeff Home Page (Nortel’s main data comms supplier):http://www.chernikeeff.co.uk/

• Multi-Tech Systems Home Page (Nortel’s modem supplier):http://www.multitech.com/

• Bay Networks Home Page:http://www.baynetworks.com/Products/

• Eurocraft Home Page (supplier of racking equipment):http://www.eurocraft.co.uk/

• Fourthtrack/Market Vision MicroMux Home Page:http://www.fourthtrack.com/

end of chapter


12-1

12

ks.

Appendix A: SDN DCN deployment engineering limits 12-Engineering limits

Observe the engineering limits set forth in the following tables in all circumstances. This includes the failure of individual communications linIf this is not observed, data communications failures may result.

Table 12-1Management sites

Domain/component

Recommended engineering limits

SDH managementdomain

Only one is required.

Table 12-2Large system

Domain/component


large domain General design rule: Whenever possible, use at least two alternative paths between an EC and all the NEs in its span of control. This involves adding external DCN overlay equipment.

large domain No more than 20 SDH NE areas

large domain No practical limit on the number of areas. Only the routers available with this release limit the capacity of the network.

large domain A minimum of two E1 paths into each area (L2 only).

large domain A minimum of two routers in separate locations in each area. Routers connected by an E1 link (L1/L2) within the area.

large domain No more than four intervening areas between any two areas.

large domain No more than 150 ISs may reside within an SDH NE area (Level-1 IS-IS routing area).


12-2 Appendix A: SDN DCN deployment engineering limits

Table 12-3Small systems

Domain/component


small domain No more than 150 ISs

small domain Separate SDH NEs from general IP LANs. This is achieved by two LAN port ECs and by using routers configured to route IP and bridge OSI protocols.

small domain No more than three data link layer bridge pair links between any two LANs.

small domain An OPC can be deployed on the same LAN as SDH NEs.

Table 12-4LANs

Domain/component


Ethernet LANs

Both IP and OSI protocols may be present. Only a single protocol is available if no router is present.

Ethernet LANs

TN-1Xs should not be on IP LANs with ECs (with the exception of the OPC).

Ethernet LANs

A single LAN may have no more than 32 ISs attached. Include remote ISs connected by a bridge link in the total.

Ethernet LANs

A single LAN may have no more than 64 ESs attached. Include remote ESs connected by a bridge link in the total.

Ethernet LANs

A 10Base5 LAN segment can be a maximum of 500 m.

Ethernet LANs

A 10BaseT LAN segment can be a maximum of 100 m.

Ethernet LANs

An AUI drop cable can be a maximum of 50 m.

Ethernet LANs

Install no more than four physical layer repeaters between any two DTEs connected via a LAN.


Appendix A: SDN DCN deployment engineering limits 12-3

12

Table 12-5

TN-16X CNET

Domain/component


CNET A maximum of 10 OPCs and TN-16Xs may be physically connected by CNET cables.

CNET All SDH NEs can use a CNET link as part of the path to their ECs.

Table 12-6SDH DCC Bandwidth and limitations

Domain/component


SDH NE related

The largest number of SDH NEs supported within a single domain in Release 2 is 3000 NEs (150 NEs/area * 20 areas). The DCN contains at least 46 routers. If a higher number of NEs is required, consult the SDH DCN design group.

SDH NE related

A maximum of 63 ISs between an SDH NE and its EC.

SDH NE related

No more than 63 remote low rate SDH NEs may be managed via a single low rate SDH NE gateway. The remote NEs may be in the span of control of several ECs.

Table 12-7TN-4X

Domain/component


SDH NE related

The TN-4X STM-1e tributary does not support a DCC.



Table 12-8TN-16X with low-order MUXs

Domain/component


SDH NE related

No more than 128 remote low rate SDH NEs may be managed via a TN-16X.

Table 12-9TN-16X

Domain/component


SDH NE related

A TN-16X can be directly connected to a maximum of eight SDH NEs by eight tributary RSOH DCCs.

SDH NE related

The management path between the OPC and TN-16X should only use TN16X DCC and CNET links. Under fault conditions, the management path may be through a loop of SDH NEs connected to TN-16X tributaries. This will prevent a software download but allows other management functions.

Table 12-10TN-16X with low-order MUXs

Domain/component


SDH NE related

When more than one SDH NE is connected to a TN-16X’s tributaries and the SDH NEs are connected by a LAN, enable no more than two DCCs.

SDH NE related

When an SDH NE is connected to a TN-16X by more than one STM-N tributary, enable only one DCC link between the TN-16X and the SDH NE.


Appendix A: SDN DCN deployment engineering limits 12-5

12

Table 12-11Bandwidth requirements

Domain/component


SDH NE related

An average of 1 kbit/s of link bandwidth is required for each SDH NE managed via a given link (DCC, LAN or WAN). Therefore, approximately 2000 NEs can be managed through an E1 link.

SDH NE related

The minimum link bandwidth to manage SDH NEs is 64 kbit/s.

Table 12-12DCC

Domain/component


SDH NE related

The RSOH DCC (D1-D3) data rate is 192 kbit/s.

SDH NE related

The MSOH DCC (D4-D12) data rate is 576 kbit/s.

Table 12-13EC-1 span of control

Domain/component


span of control related

The span of control of a single EC-1 is 64 TN-1Xs Release 6, 100 TN-1C Release 1 or TN-1P/PH Release 2. 128 NEs Release 7.

Table 12-14EC-4X span of control

Domain/component


EC-4X span of control related

With 715/100 platform, span of control is 10 NEs; with G60 server, span of control is 30 NEs.



end of chapter

Table 12-15EC-16X, EC-16X 4F, and EC-64X span of control

Domain/component


span of control related

The span of control of a main/standby pair of OPCs is 34 TN-16Xs (a maximum of 24 ADMs, with the rest being regenerators). The maximum size TN-16X ring contains 16 ADMs and 18 regenerators. Refer to NRM product bulletin.


13-1

13

er

g

r

and

d to

to

Appendix B: Protocol reference information 13-Protocol interoperability

Overview The information in this section is reference material, provided to (1) answmore detailed customer questions on protocols and (2) supply tutorial information.

Both OSI and TCP/IP protocols are in the SDH DCN. Interoperability usinstandard protocols is a key feature of the SDH DCN. This enhances the chance of interoperability with new SDH equipment and existing customeLAN/WANs.

OSI protocols are used mainly for communication between the SDH NEstheir ECs. This may be command-line-based remote management.

Note: The OSI (Q3) interface is no longer supported. The OSI (Q3) Interface Description (NTP 323-1211-191) has been removed from the NTP document set.

IPs are used for communication between the various platforms used to support the SDH network management function. In addition, IPs are useprovide management access to the external SDH DCN components.

The SDH DCN project supports data communications interoperability of SDH NEs in two ways: (1) by specifying the interoperability requirementsand (2) by providing integration of the external SDH DCN components inthe SDH NE test networks.

Internet protocolsThe following Internet protocols are supported in the SDH DCN, allowinginteroperability between the various systems within the network.

• Transmission Control Protocol (TCP-RFC 793)

• Internet Protocol (IP-RFC 791)

• Internet Control Message Protocol (ICMP-RFC 792)

• Ethernet Address Resolution Protocol (ARP-RFC 826)

• User Datagram Protocol (UDP-RFC 768)

• Point to Point Protocol (PPP-RFC1331)


13-2 Appendix B: Protocol reference information

l

ter

to

ate

. the

55)

5.0.

in

• Trivial File Transfer Protocol (TFTP-RFC 783/1350)

• File Transfer Protocol (FTP-RFC 414)

• Telnet Protocol (RFC 854)

• Bootstrap loading using TFTP (Boot FTP-RFC 906)

• Routing Information Protocol (RIP-RFC 1058)

• Open Shortest Path First Protocol, version 2 (OSPF- RFC 1247)

• Interior Gateway Routing Protocol (IGRP - Cisco proprietary)

IP addressingThe information in this section covers various aspects of Internet protocoaddressing as it relates to the SDH DCN.

TCP/IP address strategy:

• The central authority for IP addressing is the Network Information Cen(NIC). The Internet Address Numbering Authority (IANA) delegates address assignment to regional bodies.

• The CIDR strategy means that only class C addresses are allocated Nortel customers.

• IANA has reserved the following three blocks of address space for privnetworks:

— 10.0.0.0-10.255.255.255 (class A)

— 172.16.0.0-172.31.255.255 (class B)

— 192.168.0.0-192.168.255.255 (class C)

• Nortel recommends that customers use a customer specific class C allocation from the appropriate regional authority (to align with CIDR)This allows the customer to more easily integrate the SDH DCN into customers’s existing Intranet.

• Customer networks can use an address allocation from the blocks of addresses reserved for private networks.

— Nortel recommends that the class C (192.168.0.0 - 192.168.255.2block for private networks is used (to align with CIDR).

— The old ARPANET address 10.0.0.0 may also be used for privatenetworks but is not recommended.

– For class A, the recommended subnetwork mask is 255.255.25This provides a 16-bit subnet, with 250 hosts on each one.

• RIP routing protocols in the SDH DCN make use of the addressing information.

OSI protocolsThe communications services and protocols described in this section areaccordance with the OSI Reference Model, International TelecommunicationUnion-Telecommunications Standardization (ITU-T) X.200. Three key documents in this area are ITU-T Q.811, ITU-T Q.812, and ITU-T G.784.


Appendix B: Protocol reference information 13-3

13 this

e

, :

res s

d in

d in

in

In addition to protocol standards, two standard profiles are referenced indocument: International Standardization Organization/International Electrotechnical Commission (ISO/IEC) International Standardized Profil(ISP) 10608-1 and ISO/IEC ISP 10608-2.

The following OSI services and protocols are supported in the SDH DCNallowing interoperability between the various systems within the network

• connection-mode transport service, as defined in ITU-T X.214

• connection-mode transport protocol class 4 (TP4) mandatory procedufor operating over the connectionless-mode network server (CLNS), adefined in ITU-T X. 224

• the transport layer profile for use over connectionless-mode network services, as defined in ITU-T Q.812, section 3.2

• mandatory procedures, as defined in ITU-T X. 234 Connectionless-mode Transport Protocol (CLTP)

• connectionless-mode network service (CLNS) defined in ITU-T X.213

• connectionless-mode network protocol with full protocol subset of category “type 1” functions defined in ITU-T X.233 Connectionless-modeNetwork Layer Protocol (CLNP)

• ESs only ES-IS routing information exchange protocol as an ES defineISO/IEC 9542 (ES-IS)

• ISs only ES-IS routing information exchange protocol as an IS defineISO/IEC 9542 (ES-IS)

• ISs only IS-IS routing information exchange protocol as a Level-1 IS (SDH NEs) defined in ISO/IEC 10589 (IS-IS)

• ISs only IS-IS routing information exchange protocol as a Level-2 IS (routers) defined in ISO/IEC 10589 (IS-IS)

• SDH embedded communications channel (ECC)

— data link layer service and link access protocol on the D-channel (LAPD) defined in ITU-T Q.920 and ITU-T Q.921 (LAPD)

— mapping between the OSI connection-mode data link service primitives defined in ITU-T X.212 and the LAPD service primitives defined in ITU-T Q.920 defined in ITU-T G.784

— profile for the data link layer defined in ITU-T G.784

— physical layer to support one or more of the following interfaces:

– regenerator section overhead (RSOH) Data Communications Channel (DCC) termination defined in ITU-T G.784 (D1-D3). Serial channel bit rate 192 kbit/s

– multiplex section overhead (MSOH) DCC termination defined ITU-T G.784 (D4-D12). Serial channel bit rate 576 kbit/s

• SDH OSI LAN:



er

ome

ffic.

en Ss.

hich ost

evel

DH

— data link layer service and protocol defined in ISO 8802-2 (LLC1) and ISO 8802-3 (MAC)

— profile for the data link layer defined in ITU-T Q.811, section 5.3.2

— physical layer to support one or more of the following interfaces defined in ISO 8802-3:

– 10BaseT DTE (RJ45) NE, workstation, and 10BaseT transceiv

– 10BaseT DCE (RJ45) LAN hub

– (AUI (15-way female D-type) router, NE, and workstation

• WAN (routers and modems):

— physical layer to support an ITU-T X.21 DTE serial interface. Serial interface up to 2 Mbit/s. Modems provide for X.21 to G703 conversion.

• asynchronous serial

— character set based on ITU-T T.50 (American Standard Code for Information Interchange [ASCII]) and a physical interface based onITU-T V.24 as a DTE or DCE

For more information on the detail of the OSI protocols used in the SDH DCN, refer to Requirements for Interoperability within the SDH DCN (Code - 32DSS00001AND).

OSI protocol addressingThe information in this section covers various aspects of OSI protocol addressing as it relates to the SDH DCN.

OSI addressing is considerably different from IP addressing. Therefore, sterminology are defined before proceeding further:

• End System

An ES provides a source and destination for data communications traESs can be attached to one or more data communications links or subnetworks, but they cannot pass data communications traffic betwethem. The Element Controllers and some NEs (TN-1P and ATU) are E

• Intermediate System

An IS can pass data communications traffic between subnetworks to wit is connected. This functionality is sometimes referred to as routing. MSDH NEs and third-party OSI routers are ISs. ISs may be Level 1 or L2.

• SDH management domain

This is the set of all ESs, ISs, and the links between them involved in Smanagement for a particular customer network. All OSI addresses associated with these systems will have the same structure.

• Area



13a,

l the

ISs

o

s.

el-2

.

ode

This is a sub-domain of the SDH management domain. Within an areIS-IS protocol Level-1 routing is used. Between areas IS-IS Protocol Level- 2 routing is used.

An area in a Nortel supplied network contains up to 150 ISs.

Each area has an area address that uniquely defines the area and alsystems it contains within a domain. Refer to Figure 13-1.

Figure 13-1 Domain/area structure

• ES-IS protocol (ISO 9542)

This is the protocol used by ESs to communicate routing information toand each other.

• IS-IS protocol (ISO 10589)

This is the protocol used by ISs to communicate routing information teach other. There are two levels to the operation of the protocol:

— Level 1: An exchange of link state information between Level-1 ISThe link state information is essentially a list of neighboring OSI systems system identifiers (Ethernet addresses).

— Level 2: An exchange of a list of area addresses supported by LevISs.

• Network Service Access Point (NSAP)

The NSAP or OSI network address identifies a particular OSI system

Structure of an OSI network address:

— Area (3-13 bytes; Nortel default 49.0000)

Nortel recommend the use of NSAPs using the ISO data country cformat 39.****.<MAC address>.01

IS

ES

ES

IS

IS

IS

SDH Management Area A

Area B Area C

L2 L2

L2L1/L2

L1

L1

L1

L1L1/L2

Domain

IS

ES

IS

IS

ES



ed

an

Country codes are defined in ISO 3166; further definition is by the ISO member body within each country (for example, ANSI for the UnitStates and BSI for the United Kingdom).

— System Identifier (6 bytes; Ethernet or ISO 8802-3 MAC address)

— Selector (1 byte; 01-FF)

• Network Entity Title (NET)

The NET is used to unambiguously identify a network entity for the purpose of performing routing functions. It has the same structure asNSAP, but the Selector Field is always 00.

• OSI address structure as defined in ITU-T X.213 is shown in Figure 13-2.Figure 13-2OSI address structure as defined in ITU-T X.213

For more information on the structure of the OSI addresses, see ITU-T X.213 Network Service Definition.

The fields in the figure have the following meaning:

• IDP - Initial Domain Part

— AFI - Authority and Format Identifier

— IDI - Initial Domain Identifier

• DSP - Domain Specific Part

— HO-DSP - High Order Domain Specific Part

— SID - System Identifier (Ethernet address)

— SEL - Selector (NET - 00 and NSAP 01-FF)

OSI address strategy:

• Default NSAP/NET uses local format 49.0000.<MAC address>.00

OSI NSAP/NET Address Structure

Area Address (3-13)

IDP DSP

AFI IDI HO-DSP SID SEL

System ID (6) SEL (1)



13C

d

ses

ry

be

001

• Recommend NSAP/NET ISO Data Country Code format 39.****.<MAaddress>.00

— Country codes are defined in ISO 3166; further definition is by the ISO member body within each country (for example, ANSI in the UniteStates and BSI in the United Kingdom).

• Routing protocols - ES-IS and IS-IS protocols

— Cisco routers provide support for Level-2 routing.

In the United Kingdom, the following document defines the OSI address allocation process:

BS 7306: British Standard Procedures for the Operation of the UKScheme for the Allocation of ISO-DCC Format OSI NSAP Addres(Including the Operation of the UK Registration Authority), with reference ISO 8348/AD2.

Within North America, ANSI defines the structure of the ISO Data CountCode format OSI NSAP address. This is described in ITU-T Q.811, ANSI T1.204-1993, and ANSI X3.216-1992. This is the 20-byte NSAP format usedby Avantel.

A formal definition of the terms mentioned in the list above are given in ISO 8648 Internal Organization of the Network Layer. For more information, see ITU-T X.213 Network Service Definition.

An example of a Brazilian OSI network layer ISO DCC format address structure using the ANSI structure and binary abstract syntax is

39.076F.80xx.xxxx.0000.dddd.aaaa.eeee.eeee.eeee.00

IDP (Initial Domain Part):

AFI - 39 indicates ISO DCC format see ITU-T X.213.

IDI - 076F indicates that the country is Brazil; see ISO 3166.

— 484F is for Mexico.

— 032F is for Argentina.

— 840F is for the USA.

— 826F is for the UK.

DSP (Domain Specific Part):

— DFI - 80 is the DSP Format Identifier.

— ORG - xx.xxxx is the organization field (for example, Telesp, Telebar).

— RES - 0000 is a reserved field.

— RD - dddd is the Routing Domain for SDH management and can any value.

— AREA - aaaa is the Area, which can be any value (for example, 0or 0002).



r

s

ity. e

an ts

.

— SID - eeee.eeee.eeee is the System Identifier field. The physical address of the NE, normally an IEEE 802.3 MAC address.

— SEL - 00 is the Selector field for a Network Entity Title or 01-FF foan NSAP.

The AFI and the IDI are defined in the international standards. An addresallocation authority in Brazil would define a structure for the DSP.

The Brazilian Address Allocation Authority would allocate values for the various fields. When an organization (for example, Telesp) applies for anORG field value, it is allocated one from the list maintained by the authorThe organization (for example, Telesp) is then responsible for defining thvalues used in the RD and AREA fields.

The SID field is the physical address of the equipment, which is normallyIEEE 802.3 MAC address administered by the IEEE. The first three octeindicate the manufacturer (000075 for Nortel).

The SEL field is 00 for a NET or 01-FF for an NSAP. This is covered by international standards. Nortel SDH equipment tends to use the value 01

end of chapter


14-1 14
Appendix C: Tables 14-
Table 14-1NEs and respective ECs that may be connected to SDH DCN ports supporting OSI protocols

Product/Release Specifics

TN-1P Release 2 (1) TN-1P - one RSOH DCC port or two in protected mode (ES)

(2) TN-1PH - one Ethernet LAN port (10BaseT DTE RJ45) (ES) and one RSOH DCC port or two in protected mode which may only be connected to a TN-1P and nothing else

TN-1C Release 1 Two RSOH DCC ports and an Ethernet LAN port (10BaseT DTE RJ45) (IS)

TN-1C Release 2 Now available and supported

TN-1X/S Release 6 One RSOH or MSOH DCC port per STM-N port. An Ethernet LAN port (10BaseT DTE RJ45) is provided by the ATU interface module which is installed in the TN-1X/S subrack.

TN-1X Release 6 One RSOH or MSOH DCC port per STN-N port and one Ethernet LAN port (AUI) (IS)

TN-1X Release 7 One RSOH or MSOH DCC port per STN-N port and one Ethernet LAN port (AUI) (IS)

ATU Release 1 One Ethernet LAN port (10BaseT DTE RJ45) (ES) and four V.24 ports

TN-4X Release 2.4 One RSOH DCC port per optical STM-N port and one Ethernet LAN port (AUI) (IS)

TN-16L Release 4 One RSOH DCC port per STM-16 aggregate port and one Ethernet LAN port (AUI) (IS)

TN-16X Release 5 One RSOH DCC port per STM-16 aggregate, maximum eight RSOH DCC ports associated with tributary STM-N ports and one CNET port (IS)

TN-40X 4/1 cross connect Release 4

One Ethernet LAN port (AUI) (IS). The DCC ports are functional, but they are not currently used in Nortel networks.

—continued—


14-2 Appendix C: Tables

STM-16 4F One RSOH DCC port and one MSOH DCC port per STM-16 aggregate port, one RSOH DCC port per STM-1 port, and one Ethernet LAN port (10BaseT DCE three x 9-way female D-types) (IS)

X/40 SDH Radio Internal communications channel in the STM-4 aggregate ports and CNET (IS). In addition, an SDH overhead clear channel facility able to link RSOH DCC ports on tributaries at either end of a radio link.

—end—

Table 14-2Main element controller types (OSI system)

Controller type

Specifics

EC-1 (ES) Managed NEs - TN-1P, TN-1C, and TN-1X (TNMS - TN-16L), a single Ethernet LAN port (AUI) (TCP/IP and OSI), OR one LAN port (10BaseT DTE RJ45) (TCP/IP) and another LAN port (AUI) (OSI). B1320 has 2 ports, 10BaseT as standard.

EC-4X (ES) Managed NE - TN-4X, a single Ethernet LAN port (AUI) (TCP/IP and OSI), OR one LAN port (10BaseT DTE RJ45) (TCP/IP) and another LAN port (AUI) (OSI)

EC-1.5L Managed NEs - TN-16L, a single Ethernet LAN port (AUI) (TCP/IP and OSI), OR one LAN port (10BaseT DTE RJ45) (TCP/IP) and another LAN port (AUI) (OSI)

MV36 (ES) (1) Managed NE - TN-40X 4/1

(2) A single Ethernet LAN port (AUI) (TCP/IP and OSI)

EC-16XWX-‘5X 4F(IS or ES)

(1) Managed NEs - TN-16X, STM-16 4F, and X/40 SDH Radio

(2) An Ethernet LAN port (10BaseT DTE DUPONT) (TCP/IP) and a CNET port (OSI)

EC-1 (ES) Managed NEs - TN-1P, TN-1C, and TN-1X (TNMS - TN-16L), a single Ethernet LAN port (AUI) (TCP/IP and OSI), OR one LAN port (10BaseT DTE RJ45) (TCP/IP) and another LAN port (AUI) (OSI)

EC-4X (ES) Managed NE - TN-4X, a single Ethernet LAN port (AUI) (TCP/IP and OSI), OR one LAN port (10BaseT DTE RJ45) (TCP/IP) and another LAN port (AUI) (OSI)

EC-1.5L Managed NEs - TN-16L, a single Ethernet LAN port (AUI) (TCP/IP and OSI), OR one LAN port (10BaseT DTE RJ45) (TCP/IP) and another LAN port (AUI) (OSI)

—continued—

Table 14-1NEs and respective ECs that may be connected to SDH DCN ports supporting OSI protocols (continued)

Product/Release Specifics



14
MV36 (ES) (1) Managed NE - TN-40X 4/1
(2) A single Ethernet LAN port (AUI) (TCP/IP and OSI)

OPC (IS or ES) (1) Managed NEs - TN-16X, STM-16 4FR, and X/40 SDH Radio

(2) An Ethernet LAN port (10BaseT DTE DUPONT) (TCP/IP) and a CNET port (OSI)

—end—

Table 14-3Routers forming the main components of the SDH DCN

Router model Description

Cisco 2501 One LAN port (AUI), two high-speed serial ports (X.21), IP only, and AC power

Cisco 2501 OSI one LAN port (AUI), two high-speed serial ports (X.21), IP, OSI, and AC power

Cisco 2501 DC one LAN port (AUI), two high-speed serial ports (X.21), IP only, and DC power

Cisco 2501 OSI DC

one LAN port (AUI), two high-speed serial ports (X.21), IP, OSI, and DC power

Cisco 2505 8-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports (X.21), IP only, and AC power

Cisco 2505 OSI 8-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports (X.21), IP, OSI, and AC power

Cisco 2505 DC 8-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports (X.21), IP only, and DC power

Cisco 2505 OSI DC

8-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports (X.21), IP, OSI, and DC power

Cisco 2507 16-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports (X.21), IP only, and AC power

Cisco 2507 OSI 15-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports (X.21), IP, OSI, and AC power

Cisco 2507 DC 16-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports (X.21), IP only, and DC power

Cisco 2507 OSI DC

16-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports (X.21), IP, OSI, and DC power

—continued—

Table 14-2Main element controller types (OSI system)

Controller type

Specifics



Cisco 2514 two LAN ports (AUI), two high-speed serial ports (X.21), IP only and AC power

Cisco 2514 OSI two LAN ports (AUI), two high-speed serial ports (X.21), IP, OSI, and AC power

Cisco 2514 DC two LAN ports (AUI), two high-speed serial ports (X.21), IP only, and DC power

Cisco 2514 OSI DC

two LAN ports (AUI), two high-speed serial ports (X.21), IP, OSI, and DC power

—end—

Table 14-4Components used to extend or construct LANs (Ethernet or CNET)

Component name Specifics

Ethernet LAN hubs (1) Allied Telesyn CentreCOM 8-port 10BaseT hub (RJ45), AC power

(2) Allied Telesyn CentreCOM 16-port 10BaseT hub, AC power

(3) Baystack 101 10BaseT hub with 12 RJ-45 ports

(4) Baystack 102 10BaseT hub with 24 RJ-45 ports

(5) Baystack 106 10BaseT hub with 12 RJ-45 ports and -48 volt DC power supply

(6) Baystack 107 10BaseT hub with 24 RJ-45 ports and -48 volt DC power supply

Ethernet transceivers (1) Allied Telesyn CentreCOM 10Base5 N-type transceiver (DCE)

(2) Allied Telesyn CentreCOM 10BaseT slim transceiver, used to connect all systems with AUI ports to 10BaseT LAN hubs (DTE)

Cables (1) Ethernet 10BaseT UTP straight cable (RJ45 - RJ45)

(2) Ethernet 10BaseT UTP cross-over cable (RJ45 - RJ45)

(3) OPC Ethernet 10BaseT UTP straight cable (Dupont - RJ45)

(4) STM-16 4FR Ethernet 10BaseT UTP straight cable (9-way D-type - RJ45)

(5) Ethernet AUI drop cable (15-way D-type)

(6) CNET cable

—end—

Table 14-3 (continued)Routers forming the main components of the SDH DCN (continued)

Router model Description



14

Table 14-5Multi-Tech MT2834BL modem approvals with part numbers

Country Part number

Australia MT2834BLI-AUSTRALIA

Austria MT2834BLG-AUSTRIA

Belgium MT2834BLI-BELGIUM

Canada MT2834BL-DOC

Czech Republic MT2834BLI-CZECH

Denmark MT2834BLI-DENMARK

Finland MT2834BLI-FINLAND

France MT2834BLF

Germany MT2834BLG

Greece MT2834BLI-GREECE

Hong Kong MT2834BLI

Hungary MT2834BLI-HUNGARY

Iceland MT2834BLI-ICELAND

Ireland MT2834BLI-IRELAND

Italy MT2834BLI-ITALY

Japan MT2834BLI-JAPAN

Luxembourg MT2834BLI-LUXEMBOURG

Malaysia MT2834BLI-MALAYSIA

Mexico MT2834BL-MEXICO

Morocco MT2834BLF-MOROCCO

Netherlands MT2834BLI-HOLLAND

New Zealand MT2834BLI-NEW ZEALAND

Norway MT2834BLI-NORWAY

Poland MT2834BLI-POLAND

Portugal MT2834BLI-PORTUGAL

Russia MT2834BLI

Singapore MT2834BLI-SINGAPORE

South Africa MT2834BLI-RSA

Spain MT2834BLI-SPAIN

—continued—



For countries with no part number listed, the use of MT2834BLI is recommended with the following considerations:

• Local phone plug, lead, or adaptor may be required.

• Legal implications of connecting to the PSTN must be considered

Sweden MT2834BLI-SWEDEN

Switzerland MT2834BLI-SWISS

Turkey MT2834BLI-TURKEY

Ukraine MT2834BLI

United Kingdom MT2834BLK

—end—

Table 14-5Multi-Tech MT2834BL modem approvals with part numbers (continued)

Country Part number



14

Table 14-6SDH DCN components list, Release 2

Model Interfaces Protocols/IOS IP/ Enterprisesoftware

Power/consump- tion

Hardware MTBFPredicted (P)/actual (A)

Nortel CPC

Nortel PEC

Routers

Cisco 2501

2 serial and 1 LAN

IP only;[SF25C-11.0.13 (IP)

85 to 264 VAC, 47 to 63 Hz; 40 W

[CISCO2501] minimum dual 4 MB Flash banks and 4 MB DRAM

P: 23 yrsA: 122 yrs

A0678094 NTJM01AA

Cisco 2501 OSI

2 serial and1 LAN

IP and OSI;[SF25A-11.0.13](Enterprise)

85 to 264 VAC, 47 to 63 Hz; 40 W


P: 23 yrsA: 122 yrs

A0680001 NTJM01BA

Cisco 2501 DC

2 serial and 1 LAN

IP only;[SF25C-11.0.13] (IP)

-48V DC; 40 W

[CISCO2501-DC] minimum dual 4 MB Flash banks and 4 MB DRAM

P: 23 yrsA: 122 yrs

A0680010 NTJM01CA

Cisco 2501 OSI DC

2 serial and 1 LAN

IP and OSI; [SF25A-11.0.13] (Enterprise)

-48V DC; 40 W


P: 23 yrsA: 122 yrs

A0680011 NTJM01DA

Cisco 2505

2 serial and 8-port LAN hub

IP only;[SF25C-11.0.13] (IP)

85 to 264 VAC, 47 to 63 Hz; 40 W

[CISCO2505] minimum dual 4 MB Flash banks and 4MB DRAM

P: 17 yrsA: 94 yrs

A0680014 NTJM01EA

Cisco 2505 OSI


IP and OSI;[SF25A-11.0.13] (Enterprise)

85 to 264 VAC, 47 to 63 Hz; 40 W


P: 17 yrsA: 94 yrs

A0680018 NTJM01FA

Cisco 2505 DC


IP only;[SF25C-11.0.13] (IP)

-48V DC; 40 W


P: 17 yrsA: 94 yrs

A0680020 NTJM01GA

Cisco 2505 OSI DC



-48V DC; 40 W


P: 17 yrsA: 94 yrs

A0680167 NTJM01HA

Cisco 2507


IP only;[SF25C-11.0.13] (IP)

85 to 264 VAC, 47 to 63 Hz; 40 W


P: 17 yrsA: 94 yrs

A0724751 NTJM02EA

Cisco 2507 OSI



85 to 264 VAC, 47 to 63 Hz; 40 W


P: 17 yrsA: 94 yrs

A0724752 NTJM02FA

Cisco 2507 DC


IP only;[SF25C-11.0.13] (IP)

-48V DC; 40 W


P: 17 yrsA: 94 yrs

A0724753 NTJM02GA

Cisco 2507 OSI DC



-48V DC; 40 W


P: 17 yrsA: 94 yrs

A0724754 NTJM02HA

—continued—



Cisco 2514

2 serial and 2 LAN

IP only;[SF25C-11.0.13] (IP)

85 to 264 VAC, 47 to 63 Hz; 40 W


P: 17 yrsA: 126 yrs

A0680171 NTJM01JA

Cisco 2514 OSI

2 serial and 2 LAN


85 to 264 VAC, 47 to 63 Hz; 40 W


P: 17 yrsA: 126 yrs

A0680172 NTJM01KA

Cisco 2514 DC

2 serial and 2 LAN

IP only;[SF25C-11.0.13] (IP)

-48V DC;40 W

[CISCO2514-DC] minimum dual 4 MB Flash banks and4 MB DRAM

P: 17 yrsA: 126 yrs

A0680174 NTJM01LA

Cisco 2514 OSI DC

2 serial and 2 LAN


-48V DC;40 W


P: 17 yrsA: 126 yrs

A0680180 NTJM01MA

Terminal Servers

Cisco 2509

2 serial, 8 low-speed asynchronous and 1 LAN

IP only;[SF25C-11.0.13] (IP)

85 to 264 VAC, 47 to 63 Hz; 40 W


P: 16 yrsA: 79 yrs

A0680185 NTJM01NA

Cisco 2509 DC

2 serial, 8 low-speed asynchronous and 1 LAN

IP only; [SF25C-11.0.13] (IP)

-48V DC; 40 W


P: 16 yrsA: 79 yrs

A0680310 NTJM01QA

Octal male DB25 modem cable

[CAB-OCTAL-KIT] A0681539 NTJM01ZA

Octal male RJ45 Cable

[CAB-OCTAL-ASYNC] A0681540 NTJM02AA

Octal female DB25 terminal Cable

[CAB-OCTAL-FDTE] A0681541 NTJM02BA

Octal male DB25 Cable

[CAB-OCTAL-MODEM] A0681542 NTJM02CA

Cisco Router Serial Interface Local Link

Cisco Router Serial Interface Local Link Cable

Cisco X.21 DTE male router cable (3m) [CAB-X21MT]; Cisco X.21 DCE female router cable (3m) [CAB-X21FC]

A0681544 NTJM02DA

—continued—

Table 14-6SDH DCN components list, Release 2 (continued)


Power/consump- tion


Nortel CPC

Nortel PEC



14
High-speed modem
Fourth-track/Market Vision MicroMuxSP-1-RAHigh-speed modem and router cable

X.21 and G.703(E1) 120 ohm (or 75 ohm)

100/240V -50/60 Hz; 2.5 W

[SP-1-RA], [T-120], [PSU-INT] and [CAB-X21MT]

P: 17 yrsA: 160 yrs

A0680486 NTJM01SA

Fourth-track Market Vision MicroMuxSP-1-RA High- speed modem and router cable

X.21 and G.703(E1) 120 ohm (or 75 ohm

-48V DC;2.5 W

[SP-1-RA], [T-120], [PSU-DC] and [CAB-X21MT]

P: 17 yrsA: 160 yrs

A0680499 NTJM01TA

Low speed modem

External Modem 2834BL

12 W [MT2834BLK] A0680758 NTJM01YA

Ethernet transceivers

Allied Tel-esyn Interna-tionalCentreCOM 20810Base5(N-type) Trans-ceiver

400 mA [AT-208] A0680754 NTJM01UA

Allied Telesyn Interna-tional CentreCOM 210TS 10BaseT Slim Trans-ceiver

300 mA [AT-210TS] A0680755 NTJM01VA

—continued—



Power/consump- tion


Nortel CPC

Nortel PEC



Ethernet LAN Hub

Baystack 106 10Base-T Hub with 12 port RJ45 Connectors and -48VDC Power

-48VDC40W

P: 12.7 A0728025 NTJM02JA

Baystack 107 10Base-T Hub with 24 port RJ45 Connectors and -48VDC Power

-48VDC40W

P: 11.4 A0728027 NTJM02KA

Baystack 101 10Base-T Hub with 12 port RJ45 Connectors and -240VAC Power

100/240V 50/60 Hz; 40W

P: 12.7 A0729007 NTJM02PA

Baystack 102 10Base-T Hub with 24 port RJ45 Connectors and -240VAC Power

100/240V 50/60 Hz; 40W

P: 11.4 A0729006 NTJM02NA

LAN cables

Ethernet AUI drop cable (5m)

15 way D-type

32YCN00100AWY

Ethernet 10BaseT straight cable (1m - 25m)

RJ45-RJ45 (NE-Hub)

32YCN00727***

Ethernet 10BaseT crossover cable (1.25m)

RJ45-RJ45 (NE-NE)

25YCN00021AAK

—continued—



Power/consump- tion


Nortel CPC

Nortel PEC



14

Variable length cable assembly 2x RJ45 with crossover

32YCN01094***

(specify code +

required cable

length)

Ethernet 10BaseT straight cable (20m)

Dupont - RJ45(OPC-Hub)

NT7E44JE

Ethernet 10BaseT crossover cable (40m)

Dupont - RJ45(OPC -XTERM))

NT7E44JS

Ethernet 10BaseT straight cable

9 way D-type - RJ45 (TN16 4F -Hub)

NTCC90BA

CNET (1m)

(TN16X -TN16X)

NT7E44JB

CNET (5m)

(TN16X -TN16X)

NT7e44JC

—end—

Table 14-7Rack mounting kits and options available

Equipment (Please refer to Chapter 10, “Installation guidelines” for a full description of these items.)

Manufacturer Part No.

Nortel Code No.

Notes NPS Comcode CCSC 501521

Eurocraft 19” rack kits:

Basic Rack Kit 37 U 95376060/004 A0726261 NPS50520 ACAKAC

Basic Rack Kit 42 U 95426060/004 A0726263 NPS50520 ACAKAC

The following items are included in the basic kits:

Vented top cover with cable entry 600x600

95006060/425 P0878637 NPS50520 ACBTAA

100mm Cable Tray 37 U 75370010/710 P0878673 NPS50520 ACAKAC

100mm Cable Tray 42 U 75420010/710 P0878679 NPS50520 ACAKAC

—continued—



Power/consump- tion


Nortel CPC

Nortel PEC



Castors, set of 4 95000000/600 P0878638 NPS50088 AHACAC

The following items must be specified:

Cantilever shelf 445x470D 75024343/230 P0878672 NPS50520 ACBSAH

Vertical 250V AC distribution block 8-way left-hand cable entry

75080000/700 A0729317

Vertical 250V AC distribution block 8-way right-hand cable entry

75080000/001 A0729318

Panel mounted -48V DC fused distribution block

95030060/003 A0729324

The following items are in addition to the basic kits:

Door Plain 37U 95370060/310 P0878682 NPS50408 ACBRAX

Door Plain 42U 95420060/310 P0878687 NPS50408 ACBRAX

Door Vented 37U 95370060/320 P0878708 NPS50408 ACBRAX

Door vented 42U 95420060/320 P0878709 NPS50408 ACBRAX

Top covers Plain 600x600 95006060/410 P0878635

Plain top cover + cable entry 600x600

95006060/415 P0878636 NPS50520 ACBTAA

Top mounted Fan tray 600x600 95006060/820 AO726342 NSP52044 FAACAA

1U withdrawable fan tray 95006060/822 AO726344 NPS52044 FAACAA

3U front mounted fan panel 95006060/077 AO726345 NPS52044 FAACAA

Fixed shelf 445x380D 75003844/230 P0878668 NPS50520 ACBSAH

Fixed shelf 445x470D 75004744/230 P0878669 NPS50520 ACBSAH

Chassis rails 75005300/255 P0878670 NPS50520 ACAW**

Cantilever shelf 445x380D. 75023843/230 P0878671 NPS50520 ACBSAH

Side panel locking kit 95476000/300 P0878711 NPS08028 AHACAM

Rear door mtg. kit 95010000/345 A0728453 NPS52034 KAAMAA

Allied Telesyn

Mtg. Bracket 208 Transceiver AT-BRKT-0A P0878722 NPS50091 ACAEAE

—end—

Table 14-7Rack mounting kits and options available



14

Data country codes are defined in ISO 3166 and are listed in Table 14-8 (for information only).

Table 14-8Data country codes

Country name Country code

AFGHANISTAN 004

ALBANIA 008

ALGERIA 012

AMERICAN SAMOA 016

ANDORRA 020

ANGOLA 024

ANGUILLA 660

ANTARCTICA 010

ANTIGUA AND BARBUDA 028

ARGENTINA 032

ARMENIA 051

ARUBA 533

AUSTRALIA 036

AUSTRIA 040

AZERBAIJAN 031

BAHAMAS 044

BAHRAIN 048

BANGLADESH 050

BARBADOS 052

BELARUS 112

BELGIUM 056

BELIZE 084

BENIN 204

BERMUDA 060

BHUTAN 064

BOLIVIA 068

—continued—



BOSNIA AND HERZEGOVINA 070

BOTSWANA 072

BOUVET ISLAND 074

BRAZIL 076

BRITISH INDIAN OCEAN TERRITORY 086

BRUNEI DARUSSALAM 096

BULGARIA 100

BURKINA FASO 854

BURUNDI 108

CAMBODIA 116

CAMEROON

CANADA 124

CAPE VERDE 132

CAYMAN ISLANDS 136

CENTRAL AFRICAN REPUBLIC 140

CHAD 148

CHILE 152

CHINA 156

CHRISTMAS ISLAND 162

COCOS (KEELING) ISLANDS 166

COLOMBIA 170

COMOROS 174

CONGO 178

COOK ISLANDS 184

COSTA RICA 188

COTE D'IVOIRE 384

CROATIA (local name: Hrvatska) 191

CUBA 192

CYPRUS 196

—continued—

Table 14-8Data country codes (continued)




14
CZECH REPUBLIC 203
DENMARK 208

DJIBOUTI 262

DOMINICA 212

DOMINICAN REPUBLIC 214

EAST TIMOR 626

ECUADOR 218

EGYPT 818

EL SALVADOR 222

EQUATORIAL GUINEA 226

ERITREA 232

ESTONIA 233

ETHIOPIA 231

FALKLAND ISLANDS (MALVINAS) 238

FAROE ISLANDS 234

FIJI 242

FINLAND 246

FRANCE 250

FRANCE, METROPOLITAN 249

FRENCH GUIANA 254

FRENCH POLYNESIA 258

FRENCH SOUTHERN TERRITORIES 260

GABON 266

GAMBIA 270

GEORGIA 268

GERMANY 276

GHANA 288

GIBRALTAR 292

GREECE 300

—continued—





GREENLAND 304

GRENADA 308

GUADELOUPE 312

GUAM 316

GUATEMALA 320

GUINEA 324

GUINEA-BISSAU 624

GUYANA 328

HAITI 332

HEARD AND MC DONALD ISLANDS 334

HONDURAS 340

HONG KONG 344

HUNGARY 348

ICELAND 352

INDIA 356

INDONESIA 360

IRAN (ISLAMIC REPUBLIC OF) 364

IRAQ 368

IRELAND 372

ISRAEL 376

ITALY 380

JAMAICA 388

JAPAN 392

JORDAN 400

KAZAKHSTAN 398

KENYA 404

KIRIBATI 296

KOREA, DEMOCRATIC PEOPLE'S REPUBLIC OF 408

KOREA, REPUBLIC OF 410

—continued—





14
KUWAIT 414
KYRGYZSTAN 417

LAO PEOPLE'S DEMOCRATIC REPUBLIC 418

LATVIA 428

LEBANON 422

LESOTHO 426

LIBERIA 430

LIBYAN ARAB JAMAHIRIYA 434

LIECHTENSTEIN 438

LITHUANIA 440

LUXEMBOURG 442

MACAU 446

MACEDONIA, THE FORMER YUGOSLAV REPUBLIC OF 807

MADAGASCAR 450

MALAWI 454

MALAYSIA 458

MALDIVES 462

MALI 466

MALTA 470

MARSHALL ISLANDS 584

MARTINIQUE 474

MAURITANIA 478

MAURITIUS 480

MAYOTTE 175

MEXICO 484

MICRONESIA, FEDERATED STATES OF 583

MOLDOVA, REPUBLIC OF 498

MONACO 492

MONGOLIA 496

—continued—





MONTSERRAT 500

MOROCCO 504

MOZAMBIQUE 508

MYANMAR 104

NAMIBIA 516

NAURU 520

NEPAL 524

NETHERLANDS 528

NETHERLANDS ANTILLES 530

NEW CALEDONIA 540

NEW ZEALAND 554

NICARAGUA 558

NIGER 562

NIGERIA 566

NIUE 570

NORFOLK ISLAND 574

NORTHERN MARIANA ISLANDS 580

NORWAY 578

OMAN 512

PAKISTAN 586

PALAU 585

PANAMA 591

PAPUA NEW GUINEA 598

PARAGUAY 600

PERU 604

PHILIPPINES 608

PITCAIRN 612

POLAND 616

PORTUGAL 620

—continued—





14
PUERTO RICO 630
QATAR 634

REUNION 638

ROMANIA 642

RUSSIAN FEDERATION 643

RWANDA 646

SAINT KITTS AND NEVIS 659

SAINT LUCIA 662

SAINT VINCENT AND THE GRENADINES 670

SAMOA 882

SAN MARINO 674

SAO TOME AND PRINCIPE 678

SAUDI ARABIA 682

SENEGAL 686

SEYCHELLES 690

SIERRA LEONE 694

SINGAPORE 702

SLOVAKIA (Slovak Republic) 703

SLOVENIA 705

SOLOMON ISLANDS 090

SOMALIA 706

SOUTH AFRICA 710

SOUTH GEORGIA AND THE SOUTH SANDWICH ISLANDS 239

SPAIN 724

SRI LANKA 144

ST. HELENA 654

ST. PIERRE AND MIQUELON 666

SUDAN 736

SURINAME 740

—continued—





SVALBARD AND JAN MAYEN ISLANDS 744

SWAZILAND 748

SWEDEN 752

SWITZERLAND 756

SYRIAN ARAB REPUBLIC 760

TAIWAN, PROVINCE OF CHINA 158

TAJIKISTAN 762

TANZANIA, UNITED REPUBLIC OF 834

THAILAND 764

TOGO 768

TOKELAU 772

TONGA 776

TRINIDAD AND TOBAGO 780

TUNISIA 788

TURKEY 792

TURKMENISTAN 795

TURKS AND CAICOS ISLANDS 796

TUVALU 798

UGANDA 800

UKRAINE 804

UNITED ARAB EMIRATES 784

UNITED KINGDOM 826

UNITED STATES 840

UNITED STATES MINOR OUTLYING ISLANDS 581

URUGUAY 858

UZBEKISTAN 860

VANUATU 548

VATICAN CITY STATE (HOLY SEE) 336

VENEZUELA 862

—continued—





14

end of chapter

VIETNAM 704

VIRGIN ISLANDS (BRITISH) 092

VIRGIN ISLANDS (U.S.) 850

WALLIS AND FUTUNA ISLANDS 876

WESTERN SAHARA 732

YEMEN 887

YUGOSLAVIA 891

ZAIRE 180

ZAMBIA 894

ZIMBABWE 716

—end—




15-1

15

er of ns.

s

E

NE

NE

NE

NE

in the

Appendix D: Router configuration diagrams and templates 15-

To ease the work content of system design and implementation, a numbstandard topologies have been devised that should cover most applicatioFor every router in each topology, a template exists for its configuration.

The following router configuration diagrams are available:

• Topology 1: Small network - point to point 2501/2505/2507s

• Topology 2: Small network - point to point 2514 and 2501/2505/2507

• Topology 3: Small network - ring of 2501/2505/2507s

• Topology 4: Large network - two 2501/2505/2507s in an NE area

• Topology 5: Large network - one 2501/2505/2507 in an NE area

• Topology 6: Large network - three 2501/2505/2507s in an NE area

• Topology 7: Large network - management area with 1 site and 1-5 NEareas

• Topology 8: Large network - management area with 1 site and 6-10 Nareas

• Topology 9: Large network - management area with 1 site and 11-20areas

• Topology 10: Large network - management area with 2 sites and 1-5areas



Each diagram indicates the template that should be used in each router topology.


15-2 Appendix D: Router configuration diagrams and templates

t outer

in page

IP

l.

, IP

, IP

, IP

e an

“< >”

The 2507 has a larger hub than the 2505. As the hub is not configured, ifollows that the configuration information for each router is the same. Nospecific reference has been made to the 2507 in this section as the two rmay be used interchangeably (as with the 2501) in the context of these configurations.

The following router templates (Nortel PEC code of the template shown brackets) are available. They are also held on the Nortel SDH DCN Web at http://47.217.33.140/DCN/.

• Template A (NTJM9901) 2501/2505/2507 with one Ethernet and twoserial ports, IP only.

• Template B (NTJM9902) 2514 with two Ethernet and two serial ports,only.

• Template C (NTJM9903) 2501/2505/2507 with one Ethernet and twoserial ports, IP and OSI L1 and L2 routing, and one OSI over IP tunne

• Template D (NTJM9904) 2501/2505/2507 with one Ethernet and twoserial ports, IP and OSI L2 routing.

• Template E (NTJM9905) 2501/2505/2507 with one Ethernet and twoserial ports, IP and OSI L1 and L2 routing.

• Template F (NTJM9906) 2514 with two Ethernet and two serial portsand L2 OSI routing, and one OSI over IP tunnel.

• Template G (NTJM9907) 2514 with two Ethernet and two serial portsand L2 OSI routing, and two OSI over IP tunnels.

• Template H (NTJM9908) 2514 with two Ethernet and two serial portsand OSI L1 and L2 routing, and one OSI over IP tunnel.

The templates contain fields that need to be replaced in order to generatactual router configuration.

The fields that need to be changed within the templates are enclosed in (for example, < interface IP address >). The values for the router configuration template fields will be defined by the address design for therouter network.


Appendix D: Router configuration diagrams and templates 15-3

15

Topology diagramsFigure 15-1Topology 1: Small network - point to point 2501/2505/2507s

2501/2505/2507

EC

NRM

NE

NE

Router config “A”

Router config “A”E0

S0 S1

E0

S1S0

2501/2505/2507



Figure 15-2Topology 2: Small network - route IP, bridge OSI

2514

EC

NRM

NE

NE

Router config “B”


OPC

OPC

E0

S0 S1

E0

S1S0

E1

2501/2505/2507



15

Figure 15-3Topology 3: Small network - ring of 2501/2505/2507s

Figure 15-4Topology 4: Small network - ring of 2501/2505/2507s

EC

NRM

NE

NE



NE

Router config “A”E0

S1S0

E0

E0

S1S0

S1S0

2501/2505/25072501/2505/2507

2501/2505/2507

NE

Router config “C”

L2 only

NE


L2 onlyL1/L2

Tunnel

S1S0 S1 S0

E0 E0

2501/2505/2507 2501/2505/2507



Figure 15-5Topology 5: Large network - one 2501/2505/2507 in an NE area

Figure 15-6Topology 6: Three 2501/2505/2507s in an NE area

NE

Router config “D”

L2 only L2 onlyS1S0

E0

2501/2505/2507


L2 only


L2 only

Router config “E”

L1/L2 L1/L2

Tunnel

S1S0 S1S0 S1 S0

NE NENE

E0 E0 E0

2501/2505/2507 2501/2505/2507 2501/2505/2507



15

Figure 15-7Topology 7: Large network - management area with 1 site and 1-5 NE areas


Router config “D”

L2 onlyL2 only

Area 5-1Area 1-5

E0

S1S0

2501/2505/2507

2514

L2 only

Area 6-10Area 1-5

Router config “F”

L2 only

L1/L2


2514

Tunnel

Area 5-1

L2 only

Area 10-6

L2 only

E0 E0 E1E1

S1S0 S1S0




Figure 15-10Topology 10: Large network - management area with 2 sites and 1-5 NE areas

2514

L2 onlyL2 only

Area 6-10Area 1-5

Router config “G”

L2 only

L1/L2

Tunnel

L2 only

Area 16-20Area 11-15


L2 only

Tunnel

L2 only

Area 10-6Area 5-1


Tunnel

L2 onlyL2 only

Area 20-16Area 15-11


2514 2514 2514

Tunnel

E0 E1 E0 E1 E0 E1 E0 E1

S1S0 S1S0 S1S0 S1S0

2501/5

L2 only

Area 1-5

Router config “H”

L1/L2


2514

Tunnel L1/L2

L1/L2

E0E0 E1

S1S0 S0



15

Figure 15-11Topology 11: Large network - management area with 2 sites and 6-10 NE

Figure 15-12Topology 12: Large network - management area with 2 sites and 11-20 NE areas

2514

L2 only

Area 6-10Area 1-5


L2 only

L1/L2

Tunnel


2514

TunnelL1/L2

L1/L2

E0 E1E0 E1

S1S0 S1S0

2514

L2 only


L2 only

L1/L2


L2 only

Tunnel

L2 only


Tunnel

2514 2514

Tunnel

L1/L2

L1/L2

Area 16-20Area 11-15Area 6-10Area 1-5

E0 E1 E0 E1 E0 E1

S1S0 S1S0 S1S0



rge

e.00

Example The following router configurations are based on the example given in Chapter 9. The configurations show the completed templates (C) for tworouters in an SDH NE area in Brazil. This is the same as “Topology 4: LaNetwork - two 2501/2505/2507s in an NE area”.

One router is in location NW07 and the other router is in location NW13.

Figure 15-13Example SDH NE area with two routers

Addressing information OSI area address - 39.076F.8012.3456.0000.0001.0002.eeee.eeee.eee

IP addresses and subnetwork masks:

IP network - 192.168.2.0

NW07 loopback0 - 192.168.2.1 255.255.255.240

NW07 ethernet0 - 192.168.2.17 255.255.255.240

NW13 loopback0 - 192.168.2.33 255.255.255.240

NW13 ethernet0 - 192.168.2.49 255.255.255.240

Template C:

!

hostname <router location>

!

enable secret sdhdcn

!

NE

NW07L2 only

NE

NW13L2 onlyL1/L2

Tunnel

2501/2505/2507 2501/2505/2507



15

clns configuration-time 20

clns holding-time 41

clns packet-lifetime 255

clns routing

!

interface Loopback0

ip address <interface IP address> <subnetwork mask>

!

interface Ethernet0

ip address <interface IP address> <subnetwork mask>

clns router isis

isis metric 63 level-1

isis priority 65 level-1

!

interface Serial0

ip unnumbered Loopback0

clns router isis

isis circuit-type level-2-only

!

interface Serial1


clns router isis


!

router isis

net <OSI NET - ISO DCC format (39)>

net <OSI NET - Local format (49)>

!

router rip

network <IP network of interface IP addresses>

!

line con 0

line aux 0

transport input all

line vty 0 4

password cisco

login



the

!

end

When the templates addressing information is filled in for the two routers,following router configurations are produced.

Router configuration for NW07:

!

hostname NW07A2R1

!


!




clns routing

!

interface Loopback0

ip address 192.168.2.1 255.255.255.240

!

interface Tunnel0


clns router isis

tunnel source Loopback0

tunnel destination 192.168.2.33

tunnel mode eon

!

interface Ethernet0

ip address 192.168.2.17 255.255.255.240

clns router isis



!

interface Serial0


clns router isis


!



15

interface Serial1


clns router isis


!

router isis

net 39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.00

net 49.0000.eeee.eeee.eeee.00

!

router rip

network 192.168.2.0

!

line con 0

line aux 0

transport input all

line vty 0 4

password cisco

login

!

end

Router configuration for NW13:

!

hostname NW13A2R2

!


!




clns routing

!

interface Loopback0

ip address 192.168.2.33 255.255.255.240

!

interface Tunnel0




clns router isis

tunnel source Loopback0

tunnel destination 192.168.2.1

tunnel mode eon

!

interface Ethernet0

ip address 192.168.2.49 255.255.255.240

clns router isis



!

interface Serial0


clns router isis


!

interface Serial1


clns router isis


!

router isis

net 39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.00

net 49.0000.eeee.eeee.eeee.00

!

router rip

network 192.168.2.0

!

line con 0

line aux 0

transport input all

line vty 0 4

password cisco

login

!end

end of chapter


16-1

16re

er

o nt is ed

Appendix E: Bay Networks hubs 16-This range of AC- and DC-powered hubs was introduced into the DCN portfolio at Release 2, as Allied Telesyn hubs are AC only. The Allied Telesyn hubs will continue to be supported for existing installations but anot preferred for new projects.

The Baystack hubs may be upgraded to being managed by adding a management module into the expansion slot. After configuration the routbecomes a manageable entity with an IP address.

Ordering information for this unit is available from Nortel Engineering, whwill be able to offer some limited further support. Note that as managemenot a supported DCN feature, verification of such a system must be carriout on a project-by-project basis.

end of chapter


17-1

17

. te is

ISs.

r the

. It rder

le,

r 2). AN

r ith

List of terms 17-10BaseT

Ethernet wiring scheme using twisted-pair cabling in a star configurationUses RJ-45 connectors and has a reach of up to 100 m. Maximum bit ra10 Mbp/s.

ADMAdd-Drop Multiplexer

areaA subdomain of the SDH management domain. Within an area, IS-IS protocol Level 1 routing is used. Between areas, IS-IS protocol Level 2 routing is used. An area in a Nortel supplied network contains up to 150 Each area has an area address that uniquely defines the area and all thesystems it contains within a domain.

ATUAsynchronous Telemetry Unit

AUIAttachment Unit Interface (a DCE in a network element, a DTE in a dropcable). Connection to 10BaseT LAN requires 10BaseT transceiver to beprovisioned.

autonomous systemAn IP data communications network of hosts, routers, and networks undesame administration. Inside the autonomous system, interior gateway protocols such as RIP or OSPF are used to maintain routing informationfunctions as an independent system with regard to other IP networks. In oto reach other Autonomous Systems, a “gateway” is required (for examprunning a Border Gateway Protocol).

bridgeJoins two or more LAN segments together at the OSI data link layer (layeBridges are normally connected together in pairs--one at either end of a Wserial link. The terms “transparent bridge” or “spanning tree bridge” are sometimes used to refer to bridges that link Ethernet LANs.

This function is conventionally used to provide a communications path foprotocols that cannot be routed at OSI layer 3. This would be the case w


17-2 List of terms

rd f se

ken,

(for

ata

r IP

rnet

es a s

d by hin LAN

proprietary network layer protocols or OSI protocols in an IP only router network.

The operation of a bridge is to store frames received on a port and forwathem on all other ports. Bridges normally learn the Ethernet addresses osystems connected to a LAN and do not forward frames destined for thosystems.

Bridges can be connected in a mesh network. Any loops created are broby the operation of the spanning trees algorithm, which stops frames circulating endlessly round network loops.

No more than three bridge pair links are allowed between any two DTEsexample, a maximum of four routers on the path between DTEs).

Use bridging only in a limited fashion, as it results in a large amount of dtraffic being broadcast through the network.

Cisco routers can be configured to support bridging for OSI and routing foat the same time. This would normally be used in small SDH networks (<150), when access to remote groups of SDH NEs is required.

CIDRClassless Inter-Domain Routing

CLTPConnectionless-mode Transport Protocol

CNETCommunications Network. Data bus used to connect OPC to TN-16X.

DCCData Communications Channel. Channel which is available to carry Ethepackets within the overhead of telecommunications links between NEs. Supports only OSI protocol packets.

DCE Data Circuit Terminating Equipment. Refers to the equipment that providconnection into a data transmission network. In this document the term iused to refer specifically to the type of physical interface provided by theequipment.

Conventionally the interface of a dial-up PSTN modem is a DCE type interface. In this document, DCE is also used to describe the port providea 10BaseT LAN hub, which is really a DTE plus a cross-over function, witthe hub. Therefore, connection between a 10BaseT DTE and a 10BaseThub will be a straight cable.

DCN Data Communications Network


List of terms 17-3

17

cally

DCE

wo

ch is

an be they

.

,

to als.

s DH

DILDual In-Line

DTEData Terminal Equipment. This term refers to equipment that is to be connected to a network. In this document the term is used to refer specifito the type of physical interface provided by the equipment.

Conventionally a DTE is connected to a DCE of a network. For example,when a PC is connected via a dial-up PSTN modem, in order to access aremote computer, the PC has a DTE type interface and the modem has atype interface.

When a DTE is connected to a DCE, a straight cable is required. When tDTEs or DCEs are connected together, a crossover cable is required.

ECElement Controller. Consists of a workstation and software. Used to configure one or more NEs. EC and NE are connected via a network whithe DCN.

ECCEmbedded Communications Channel. See DCC.

end systemProvides a source and destination for data communications traffic. ESs cattached to one or more data communications links or subnetworks, but cannot pass data communications traffic between them. The Element Controllers (ECs) and some NEs (for example, TN-1P and ATU) are ESs

ESEnd System. See above.

high-capacity SDH NENE which will multiplex Virtual Containers VC3 and above (that is, TN-16XTN16 4F, and TN-X/40).

hostAn IP equivalent of the OSI end system. Examples of IP hosts connectedthe SDH DCN are network controllers, element controllers, and X termin

IANAInternet Address Numbering Authority

IPInternet Protocol

intermediate system Can pass data communications traffic between subnetworks to which it iconnected. This functionality is sometimes referred to as routing. Most SNEs and third-party OSI routers are ISs. ISs may be Level 1 or Level 2.


17-4 List of terms

s

a

C.

ISIntermediate System. See above.

ITU-TInternational Telecommunications Union Telecommunications Standardization Section

LAPDLink Access Protocol on the D-channel

LEDLight Emitting Diode

LANLocal Area Network

low-capacity SDH NENE which will multiplex Virtual Containers VC12 and above (that is, all NEnot regarded as high capacity, including ATU).

MOAManaged Object Agent

MTBF Mean Time Between Failures

MTTRMean Time To Repair

MSOHMultiplex Section Overhead

NCNetwork Controller

NENetwork Element. Refers to an element within the SDH network, such asTN-1X, TN-4X etc.

NETNetwork Entity Title. OSI address used for routing purposes.

NICNetwork Information Center

NRMNetwork Resource Manager. Workstation with software used to provide network services across an SDH network. Connected to ECs via the DC

NSAPNetwork Service Access Point. OSI address used for the purpose of communication between users or applications.


List of terms 17-5

17

t).

r 1). h is

ed to

r 3).

ered

e cols

t of en

ems,

OPCOperations Controller. Element controller used by TN-16X, TN16 4F, andTN-X/40 radio.

OSIOpen Systems Interconnect

PVCPermanent Virtual Circuit

PDMX-EPrimary Digital Multiplexer-Enhanced

private networkNetwork that is not connected to another network (specifically the Interne

PSTNPublic Switched Telephone Network

repeaterJoins two or more LAN segments together at the OSI physical layer (layeAn example of a repeater in the SDH DCN is the 10BaseT LAN hub, whica multiport repeater.

No more than four repeaters are allowed between any two DTEs connectan ISO 8802-3 10 Mbit/s baseband CSMA/CD or Ethernet LAN.

routerJoins two or more LAN segments together at the OSI network layer (layeRouters are normally connected to other routers over WAN serial links.

Routers forward packets on the most appropriate port to each of their destinations. Routers determine which is the most appropriate port be accessing their routing tables. The entries in these routing tables are entmanually or built up by dynamic routing protocols (RIP/OSPF for IP and ES-IS/IS-IS for OSI) between routers.

Cisco routers can be configured to route IP and OSI protocols if they havEnterprise software. They can be configured to support one or both protoon an individual port basis.

SDH NEs that are classified as Intermediate Systems are OSI protocol routers.

Routing is preferred to bridging, since it reduces to a minimum the amoundata traffic crossing the WAN. In addition, it finds the quickest route betweany two DTEs.

routing domainAn OSI data communications network of end systems, intermediate systand networks under the same administration. Inside the routing domain,


17-6 List of terms

[L1/

other

iated

intra-domain routing protocols (such as the ES-IS protocol and the IS-ISL2] protocol) are used to maintain routing information. It functions as an independent system with regard to other OSI networks. In order to reach routing domains, a “gateway” is required (for example, running an inter-domain routing protocol).

RSOHRegenerator Section Overhead

RDRouting Domain. See above.

SDHSynchronous Digital Hierarchy

SDH management domainThe set of all ESs, ISs, and the links between them, involved in SDH management for a particular customer network. All OSI addresses assocwith these systems will have the same structure.

STMSynchronous Transport Module

TMNTelecommunications Management Network

TCP/IPTransmission Control Protocol/Internet Protocol

WANWide-Area Network

end of chapter


18-1

18

nt

H

ce

/

References 18-Standard texts

Nortel document references

32DMA00001ALP 1996 SDH Data Communications Network Bullet PoiCommercial Specification, Issue 1

32DSS00001AND 1996 Requirements for Interoperability within the SDDCN, Issue 1

25DPS00750ABD 1996 Requirements for Interoperability of STM1 Interface.

ITU recommendations

G.784 1994 Synchronous Digital Hierarchy (SDH) Management

X.200 1994 Information technology - Open Systems Interconnection - Basic Reference Model: The Basic Model (ISO/IEC 7498-1)

M.3010 1992 Principles for a Telecommunications Management Network

Q.811 1993 Lower Layer Protocol Profiles for the Q3 Interface

Q.812 1993 Upper Layer Protocol Profiles for the Q3 Interfa

X.214 1994 Information technology - Open Systems Interconnection - Transport service definition (ISO/IEC 8072)

X.224 1992 Information technology - Telecommunications and information exchange between systems - Open Systems Interconnection - Protocol for providing the connection-mode transport service(ISO/IEC 8073)

X.234 1994 Information technology - Protocol for providing the connectionless-mode transport service (ISOIEC 8602)

X.213 1993 Information technology - Network service definition for Open Systems Interconnection (ISO/IEC 8348)


18-2 References

et

ta

us

l

nd

n

X.233 1994 Information technology - Protocol for providing the connectionless-mode network service (ISO/IEC 8473)

X.212 1995 Information technology - Open Systems Interconnection - Data link service definition (IOS/IEC 8886)

Q.920 1993 Digital Subscriber Signalling System No. 1 (DSS1) - ISDN User-Network Interface-Data Link layer - General aspects

Q.921 1993 ISDN User-Network Interface-Data Link layer specification

T.50 1992 Information technology - 7-bit coded character sfor information interchange (International Reference Alphabet, International Alphabet No.5or ASCII)

V.24 1993 List of definitions for interchange circuits between data terminal equipment (DTE) and dacircuit-terminating equipment (DCE)

X.21 1992 Interface between DTE and DCE for synchronooperation on public data networks.

G.703 1991 Physical/electrical characteristics of hierarchicadigital interfaces.

ISO/IEC specifications

ISO/IEC 10589 1992 Information technology - Telecommunications and information exchange between systems - Intermediate system to Intermediate system intra-domain routing information exchange protocol for use in conjunction with the protocol for providing the connectionless-mode Network Service (ISO 8473)

ISO/IEC 9542 1994 Information technology - Telecommunications and information exchange between systems - Esystem to Intermediate system routing information exchange protocol for use in conjunction with the Connectionless-mode Network Service (ISO 8473)

ISO/IEC 8802-2 1994 Information technology - Telecommunications and information exchange between systems - Local and metropolitan area networks - Specificrequirements - Part 2: Logical link control

ISO/IEC 8802-3 1993 Information technology - Local and metropolitaarea networks - Part 3: Carrier sense multiple access with collision detection (CSMA/CD) access method and physical layer specifications


References 18-3

18

r

ISO/IEC ISP 10608-1 1992 Information technology -- International Standardized Profile -- Connection-mode Transport Service over Connectionless-mode Network Service -- Part 1: General overview andsubnetwork-independent requirements.

ISO/IEC ISP 10608-2 1992 Information technology -- International Standardized Profile -- Connection-mode Transport Service over Connectionless-mode Network Service -- Part 1: General overview andsubnetwork-independent requirements.

ISO 8648 1988 Information technology - Open Systems Interconnection - Internal organization of the Network Layer.

ISO 8877 1992 Information technology - Telecommunications exchange between systems - Interface connectoand contact assignments for ISDN Basic AccessInterface located at reference points S and T (RJ45)

Internet RFCs

RFC 793 Transmission Control Protocol (TCP)

RFC 791 Internet Protocol (IP)

RFC 792 Internet Control Message Protocol (ICMP)

RFC 826 Ethernet Address Resolution Protocol (ARP)

RFC 768 User Datagram Protocol (UDP)

RFC1331 Point to Point Protocol (PPP)

RFC 783/1350 Trivial File Transfer Protocol (TFTP)

RFC 414 File Transfer Protocol (FTP)

RFC 854 Telnet Protocol

RFC 906 Bootstrap loading using TFTP (BooTP)

RFC 1058 Routing Information Protocol (RIP)

RFC 1247 Open Shortest Path First v2 (OSPF)

Regulatory requirements

93/68/EEC CE Mark Directive

73/23/EEC Low Voltage Directive

EN60950 Safety of Information Technology Equipment

EN60825 Laser Safety

89/336/EEC EMC Directive

92/31/EEC EMC Amendment

EN50082-1 EMC Generic Immunity

EN55022 EMC Emissions

EN61000-3-2 Harmonic Current Emissions


18-4 References

EN60555-2 Supply disturbance caused by household appliance

Cisco documentationCisco IOS Software Documentation (CD-ROM)

end of chapter


19-1

Index 19-

19

Aaddresses, allocation of 8-6addressing

IP 8-2IP vs OSI 8-10preferred method 8-1private networks 8-2

addressing schemeslarge SDH network 8-1

asynchronous serial ports, remote 4-4

Bbridge link, purpose of 5-13

CCIDR strategy 13-2component spares 3-8

Ddata country codes 14-13DCN equipment configuration 3-9DCN management strategy 6-1DCN repair 7-1DCN security strategy 6-2DCN, definition of 4-1DCN, external 1-2DCN, internal 1-2DCN, main component types 4-2device configurations 8-13document audience ix

Eend-to-end interoperability 4-2engineering limits 12-1, 16-1equipment list, site-by-site 3-9equipment options 10-6Ethernet ports 4-5

metric maximum 8-16

external DCN, device connections 5-1external SDH DCN 5-1

Ffirewall functionality 6-2firewalls 6-3, 9-1firewalls, configuring 6-4firewalls, determining requirements 6-3

IIANA class C addresses 9-10installation information 9-15installation information, required 3-10interface, unnumbered 8-8internal DCN, structure of 5-2internal SDH DCN 5-2internal SDH DCN components 5-2internal SDH DCN, topologies 5-2internal/external DCN, balancing 5-2Internet protocol addressing 13-2Internet protocols 13-1interoperability requirements 13-1interoperability restrictions 4-3interoperability, EC/NE 4-1IP 8-2IP address 8-10IP addresses

assigning 9-10IP addressing 13-2

examples 8-2IP networks 8-2IP/OSI protocol co-existence 5-3IS-IS

Level-1 routing 8-13Level-2 routing 8-13

ISO DCC formatusage 8-12

isolated SDH NEs 5-8


19-2 Index

LLAN bridges

SDH networks 5-13LAN components 14-4large domain structure 5-3loopback interface 8-8lower layer interoperability 4-2lower-layer interoperability 4-3

Mmaintenance agreement, supplier 7-2management area LANs 8-6Mean Time Between Failure figures, DCN

components 7-1Mean Time To Repair figures, DCN 7-1modem approvals 14-5modem, asynchronous 6-2modems, dial-up low-speed voice 4-5modems, high-speed 4-4modems, low-speed 4-5

NNEs

AUI ports 5-9NET 13-6Network and element controllers 1-3Network elements 1-2network example 9-3network printers 5-5network size limitations 5-1network topologies 5-1non-coded parts 3-9non-interoperability 5-12Nortel management systems 1-3NSAP address 13-5

OOPCs 9-5OSI addres 8-10OSI address

allocation of 9-9ISO DCC format 8-11local format 8-13parts of 8-11

OSI address allocation processUK 13-7

OSI address components 8-10, 9-9OSI addressing

concepts of 8-10

country codes 13-6examples 8-14

OSI network addressstructure of 13-5

OSI protocols, types of 8-13OSI system

main element controller types 14-2OSI tunnel 8-10OSI tunnels, function of 8-14OSI-over-IP tunnel 8-9, 8-16

Ppassword, Cisco routers 6-3passwords 6-3, 9-19point 8-2point-to-point links 8-2private network addresses 9-10process, detailed design of SDH DCN 3-1protocol interoperability 13-1

Rremote access 6-2, 6-4risk factors influencing total DCN cost 2-1router configuration diagrams 15-1router configurations, example 15-10router templates 15-2routers

as main SDH DCN components 14-3

SSDH DCN

design stages of 9-1SDH DCN components list 14-7SDH management area 5-4, 5-5SDH management domain

DCN topology 9-4SDH management domain, definition 9-4SDH management domain, definition of 5-3SDH management location 5-6SDH NE area 5-6, 5-7SDH NE area chains 5-4SDH NE areas 9-5SDH NE configuration 8-15SDH NE location

router present 5-8SDH NE topologies 5-8SDH network analysis 3-1, 9-1SDH network design activity 2-2SDH network elements 4-3


Index 19-3

19

SDH radio line system 5-7, 9-2security strategy 6-2serial interfaces 8-2serial ports

metric maximum 8-16site survey 9-15, 10-1small domain 5-11small domains, minimum requirements 5-9small domains, router networks 5-10SNMP 6-2spares, "hot" 7-2spares, in-country 7-1STM-16 ring 5-6subnetwork masks 8-2subnetworks 8-2subnetworks, broadcast 4-1subnetworks, general topology point to

point 4-2

TTCP/IP address strategy 13-2technical support xtemplate addressing 15-10terminal servers 4-4topology diagrams 15-3topology restrictions 5-7tunnel, failure and re-routing 8-8tunneling 5-3tunnelling, definition of 8-9

WWAN links 5-13Web sites 11-1Web sites, DCN equipment

manufacturers 10-6


International Broadband Networks (Dept18600)Nortel LimitedOakleigh Road SouthLondon, N11 1HB

So far as Northern Telecom is aware the contents of this document are correct. However, such contents have been obtained from a variety of sources and Northern Telecom can give no warranty or undertaking and make no representation as to their accuracy. In particular, Northern Telecom hereby expressly excludes liability for any form of consequential, indirect or special loss, and loss of data, loss of profits or loss of business opportunity, howsoever arising and whether sustained by the user of the information herein or any third party arising out of the contents of this document.

SDH TRANSMISSION

Data Communications NetworkProvisioning Guide

Copyright 1998 Northern Telecom

The copyright of this document is the property of Northern Telecom. Without the written consent of Northern Telecom, given by contract or otherwise, this document must not be copied, reprinted or reproduced in any material form, either wholly or in part, and the contents of this document, or any methods or techniques available therefrom, must not be disclosed to any other person whatsoever.

NORTHERN TELECOM CONFIDENTIAL: The information contained in this document is the property of Northern Telecom. Except as specifically authorized in writing by Northern Telecom, the holder of this document shall protect same in whole or in part from disclosure and dissemination to third parties and use same for evaluation, operation, and maintenance purposes only.

Document Number: 323-4061-151Release Number: 2Document Status: StandardDate: January 1998Printed in England

Documents

151 Standard