Академический Документы
Профессиональный Документы
Культура Документы
SDH TRANSMISSION
Data Communications
Networks
Provisioning Guide
Release 2 Standard January 1998
RESTRICTED DOCUMENT
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.
Publication history
January 1998
Release 2 Standard
December 1997
Release 2 Draft A
October 1997
Release 1 Standard
August 1997
Release 1 Draft C
August 1997
Release 1 Draft B
June 1997
Release 1 Draft A
Contents
Contents iii
About this document ix
Audience ix
Associated documents ix
Technical support and information x
Telecommunications terminal equipment approval x
General 1-1
Overview 1-1
Scope 1-2
Network elements 1-2
Network and element controllers 1-3
Document structure 1-3
Topologies 5-1
Overview 5-1
Basic DCN component connectivity 5-1
External SDH DCN 5-1
Internal SDH DCN 5-2
Balancing the internal and external DCN 5-2
IP and OSI protocol co-existence 5-3
SDH management domain architecture 5-3
Large domains 5-3
SDH management area 5-4
SDH NE area 5-6
Isolated SDH NEs 5-8
SDH NE location 5-8
Small domains 5-9
Narrowband access support 5-12
Non-interoperability 5-12
Dependability 7-1
Design 7-1
Availability 7-1
Reliability 7-1
Maintenance 7-1
In-country spares 7-1
Supplier maintenance agreements 7-2
Hot spares 7-2
Configuration backup 7-2
Protocols 8-1
Addressing 8-1
Overview 8-1
IP networks, subnetworks, and subnetwork masks 8-2
IP addressing examples 8-2
Loopback interface 8-8
Tunnel interface 8-9
OSI protocol addressing 8-10
Example 9-1
Overview 9-1
Introduction 9-1
SDH network analysis 9-1
SDH management domain definition 9-4
DCN topology 9-4
Addressing 9-9
Power supply type 9-13
Location definition 9-13
Generate components list 9-14
Installation information 9-15
References 18-1
Standard texts 18-1
Index 19-1
List of figures
Figure 1-1 The scope of the SDH DCN design 1-2
Figure 4-1 Indirect NE connections to DCN for communications with their
management systems 4-3
Figure 5-1 Basic components of the external DCN 5-1
Figure 5-2 Basic structures of the internal DCN 5-2
Figure 5-3 Maximum size domain 5-4
Figure 5-4 Example of an SDH management area 5-5
Figure 5-5 Example of a large SDH management area 5-6
Figure 5-6 Example of an SDH NE area 5-7
Figure 5-7 Example of an SDH NE area with SDH radio systems 5-8
Figure 5-8 Example of an SDH NE location with a router present 5-9
Figure 5-9 Minimal SDH DCN 5-10
Figure 5-10 Routers in a small domain 5-11
Figure 5-11 Narrowband access multiplexer and the ATU 5-12
Figure 5-12 Use of bridges in SDH networks 5-13
Figure 6-1 Access using Telnet/TCP/IP over a LAN port from a UNIX
workstation 6-2
Figure 8-1 Two routers within an SDH NE area 8-3
Figure 8-2 Allocation of IP addresses 8-5
Figure 8-3 Routers within a management area 8-5
Figure 8-4 Allocation of IP addresses in a management location 8-8
Figure 8-5 Tunnelling 8-9
Figure 8-6 Two routers within an SDH NE area 8-15
Figure 8-7 Two routers within an SDH NE area 8-16
Figure 9-1 Network example 9-3
Figure 9-2 Management domain 9-4
Figure 9-3 SDH management area 9-5
Figure 9-4 SDH NE area one 9-6
Figure 9-5 SDH NE area three 9-7
Figure 9-6 SDH NE area four 9-8
Figure 9-7 System illustrating connectivity at location 9-13
Figure 9-8 Generating a components list 9-14
Figure 13-1 Domain/area structure 13-5
Figure 13-2 OSI address structure as defined in ITU-T X.213 13-6
Figure 15-1 Topology 1: Small network - point to point 2501/2505/2507s 15-3
Figure 15-2 Topology 2: Small network - route IP, bridge OSI 15-4
Figure 15-3 Topology 3: Small network - ring of 2501/2505/2507s 15-5
Figure 15-4 Topology 4: Small network - ring of 2501/2505/2507s 15-5
Figure 15-5 Topology 5: Large network - one 2501/2505/2507 in an NE area
15-6
Figure 15-6 Topology 6: Three 2501/2505/2507s in an NE area 15-6
Figure 15-7 Topology 7: Large network - management area with 1 site and 1-5
NE areas 15-7
Figure 15-8 Topology 8: Large network - management area with 1 site and
List of tables
Table 8-1 Addresses that can be allocated 8-6
Table 9-1 Needed DCN components 9-15
Table 9-2 Example location and connectivity table 9-16
Table 9-3 Example interface/configuration for area 1 9-17
Table 9-4 Example interface/configuration for area 2 9-17
Table 9-5 Example of addressing, area 1 9-18
Table 10-1 Standard items supplied with equipment 10-4
Table 12-1 Management sites 12-1
Table 12-2 Large system 12-1
Table 12-3 Small systems 12-2
Table 12-4 LANs 12-2
Table 12-5 TN-16X CNET 12-3
Table 12-6 SDH DCC Bandwidth and limitations 12-3
Table 12-7 TN-4X 12-3
Table 12-8 TN-16X with low-order MUXs 12-4
Table 12-9 TN-16X 12-4
Table 12-10 TN-16X with low-order MUXs 12-4
Table 12-11 Bandwidth requirements 12-5
Table 12-12 DCC 12-5
Table 12-13 EC-1 span of control 12-5
Table 12-14 EC-4X span of control 12-5
Table 12-15 EC-16X, EC-16X 4F, and EC-64X span of control 12-6
Table 14-1 NEs and respective ECs that may be connected to SDH DCN
ports supporting OSI protocols 14-1
Table 14-2 Main element controller types (OSI system) 14-2
Table 14-3 Routers forming the main components of the SDH DCN 14-3
Table 14-4 Components used to extend or construct LANs (Ethernet or
CNET) 14-4
Table 14-5 Multi-Tech MT2834BL modem approvals with part numbers 14-5
Table 14-6 SDH DCN components list, Release 2 14-7
Table 14-7 Rack mounting kits and options available 14-11
Table 14-8 Data country codes 14-13
List of procedures
Procedure 3-1 Pre-bid information collection and SDH network analysis 3-1
Procedure 3-2 Pre-bid engineering 3-3
Procedure 3-3 Post-contract re-engineering 3-5
Procedure 3-4 Detailed DCN topology for small SDH networks 3-6
Procedure 3-5 Detailed DCN topology for large SDH networks 3-6
Procedure 3-6 Detailed DCN topology for the management area in large SDH
networks 3-7
Procedure 8-1 Designing addressing scheme for large SDH networks 8-1
Audience
The audience for this document includes the following Nortel organizations:
Sales
Marketing
Product Line Management
Customer Systems Engineering
Customer Network Solutions
Customer Technical Support
Associated documents
The 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
United Kingdom
Freephone: 0800 626 881
Telephone: 0181 361 4693
FAX: 0181 945 3456
International
Telephone: +44 181 361 4693
FAX: +44 181 945 3456
1-1
General 1-
Overview
This document provides sufficient material to allow Systems Engineering
groups to design customer-specific SDH DCNs.
Figure 1-1
The scope of the SDH DCN design
LAN
Router External
DCN
WAN
Router
Element
Controllers LAN
Cross
16X 4X 1X 1C 1PH Connect
Internal DCN
16
X
16
X
1X
SDH NEs
Scope
This section indicates the type of Nortel-supplied equipment that the SDH
DCN can be used to support.
Network elements
The 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
TN-4XE Release 1 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)
Document structure
This document consists of two major parts. The first part provides
information on the process associated with Nortel defining a customer SDH
DCN. The second part provides SDH DCN tutorial information, which is
reference material for the process-oriented part.
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 found
on the DCN Web page (http://47.217.33.140/DCN/).
When the available material is not adequate, consult members of the SDH
DCN design team.
end of chapter
Initial estimation
ATTENTION
Failure to estimate the DCN correctly at the bid stage typically leads to an
under-performing network, customer dissatisfaction, and additional
unbudgeted rectification costs.
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 DCN
provided to date has cost $9 million.
During this stage of a project, it is not possible to provide rules for estimating
the true cost. All that can be given is the following list of risk factors that will
influence 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
The more of the above factors that apply, the more the SDH DCN will move
from 1% to 10%.
Sales stage
Before placing the final bid, carry out a design of the SDH network. Refer to
Detailed design on page 3-1. This design activity normally consists of traffic
analysis, SDH traffic network topology planning, and placement of
management centers.
Additionally, the network design activity includes the SDH DCN topology
and equipment list. Carry out this activity in accordance with this documents
guidelines (refer to Topologies on page 5-1and Appendix C: Tables on page
14-1). The application of the SDH DCN spares policy normally adds extra
items to the equipment list.
Once the first draft of the SDH DCN equipment list is available, provide the
information 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 the
cost to Nortel of the SDH DCN, associated with a given bid.
Detailed design 3-
3
General
This section contains a definition of the process required to do the detailed
design of a customer SDH DCN.
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
Procedure 3-1
Pre-bid information collection and SDH network analysis
Step Action
end
SDH network analysis information will change during the design process, but
it should be maintained as accurately as possible.
The approach to the DCN depends on the number of SDH NEs. Networks
with more than 150 NEs are large and other networks are small (from a DCN
perspective).
The main objective of the pre-bid engineering stage is to quantify the list of
DCN components required.
This is accomplished by first designing the internal DCN (SDH NE DCC and
SDH NE LAN links) and determining the quantity and placement of the
management systems. The external DCN (routers, etc.) can then be added to
provide connectivity between the management systems and the SDH NEs.
Procedure 3-2
Pre-bid engineering
Step Action
continued
Procedure 3-2
Pre-bid engineering (continued)
Step Action
end
The object of the post-contract re-engineering is to add all the aspects of the
design that do not add to the list of DCN components.
Procedure 3-3
Post-contract re-engineering
Step Action
end
Procedure 3-4 outlines the detailed DCN topology for small SDH networks.
Procedure 3-4
Detailed 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
The detailed DCN topology for large SDH networks is defined in Procedure
3-5.
Procedure 3-5
Detailed 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
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).
3
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 large
SDH networks.
Procedure 3-6
Detailed DCN topology for the management area in large SDH networks
Step Action
continued
Procedure 3-6
Detailed DCN topology for the management area in large SDH networks
Step Action
end
Location definition
Once the basic router network, Ethernet LAN connectivity requirements, and
power supply types are known, produce a DCN network diagram for each
location, showing how all the DCN components and other equipment are
interconnected.
The list in this document is not exclusive and other DCN components can be
used if desired. When other non-approved components are used, Nortel
suggest consulting the SDH DCN design group.
Non-coded parts may be used if customers already have DCN equipment they
wish to use or a new Nortel-supplied DCN component is needed. In the latter
case, 25Z... codes will be needed.
Configuration
Some of the equipment in the DCN needs to be configured. The configuration
can vary from a dual in-line package (DIP) switch setting to a list of router
configuration statements. The items that may require configuration are:
routers (IP address, OSI address and topology dependent configuration)
terminal servers (IP address and general configuration)
management systems (IP address and for some ECs OSI addresses as
well)
SDH NEs (OSI address, LAN/DCC port on/off status and DCC (RSOH/
MSOH usage)
high-speed modems (clock master/slave)
Installation information
Define the physical location of the DCN equipment, including information on
the type of equipment racking to be used. SDH DCN Release 2 offers a
variety of racking configurations based on two rack heights, 36U and 42U A.
Basic rack in each size is available preassembled from the supplier. For
further information about ancillary racking equipment, see Appendix C.
End system
ESs provide a source and destination for data communications traffic. They
can be attached to one or more data communications links or subnetworks,
but they cannot pass data communications traffic between them. The ECs and
some NEs are ESs.
Intermediate system
ISs can pass data communications traffic between subnetworks to which they
are connected. This functionality is sometimes referred to as routing. Most
SDH NEs and third-party OSI routers are ISs. ISs are either Level 1 or
Level 2.
Subnetworks
Two types of subnetworks are considered in this document:
broadcast
End-to-end interoperability
This level of interoperability is required when an application on one TCP/IP
or OSI entity needs to communicate information to an application on another
TCP/IP or OSI entity. This involves the operation of the transport layer in
addition to the three lowest layers.
The following NEs are indirectly connected to the DCN for communications
with their management systems, as illustrated in Figure 4-1:
Tellabs 532E 1/0 cross connect via a Cisco 2509 terminal server V.24 port
4
PDMX-E via an ATU, TN-1P, or TN-1C V.24 port
Figure 4-1
Indirect NE connections to DCN for communications with their management
systems
NRM
LAN
MOA Router
WAN
Router
OA
LAN
Terminal
server
V. 24
532
The NRM communicates to its ECs via the DCN using conventional TCP/IP
protocols. The ECs communicate to their NEs via the DCN using OSI
protocols. Therefore, the DCN must support both IP and OSI protocols. Refer
to Main element controller types (OSI system) on page 14-2.
Routers
See Routers forming the main components of the SDH DCN on page 14-3.
Terminal servers
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
The terminal servers listed above only support TCP/IP and cannot be used via
OSI-only systems.
High-speed modems
Use 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
These devices are supplied with a Cisco X.21 DTE male router cable (3 m)
for connection to a Cisco router high-speed synchronous serial interface.
LAN components
Ethernet ports are RJ45, DCE, and AUI. Refer to Components used to extend
or construct LANs (Ethernet or CNET) on page 14-4.
Dial-up low-speed voice modems
Use the Multi-Tech Systems External dial-up low-speed voice modems
(MT2834BL) to provide remote access to workstations or routers (aux port).
These modem links are used for remote access to Nortels staff.
Note that different versions of this modem exist for different countries.
Consult the manufacturer to determine the correct part for a particular country
(for example, MT2834BLK for the UK). 4
Release 2 requires 64 kbit/s modems.
Component tables
Refer 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
Topologies 5-
Overview
This section provides information on the network topologies to be used as
part of a SDH DCN design. Refer to Appendix A: SDN DCN deployment
engineering limits on page 12-1 for size limitations of the networks various
parts.
X.21 G.703
LAN Serial 2 Mbit/s
Modem
10BaseT
UTP x
10BaseT Router G.703
LAN Hub 2 Mbit/s
LAN cables
and transceivers Modem
10BaseT X.21
UTP Serial
WAN
Other: TN-1/0, TN-1X, ATU, terminal servers, and other ancillary devices
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, loops,
and chains of DCC links. The internal DCN in a real network can be very
large and complex.
Figure 5-2
Basic structures of the internal DCN
DCC
1P 1P 16X
DCC No DCC
10BaseT DCC 10BaseT
LAN Hub LAN Hub
1X 1X 4X
DCC 4X 4X 4X
1C 1C 1C 1X 1X 1X 1P
DCC DCC DCC DCC
Connect SDH NE LAN ports only to the SDH DCN and not directly to a
general-purpose customer TCP/IP network.
SDH DCN Release 2 does not provide a technique for carrying IP packets
over an OSI-only network, such as the DCC links between SDH NEs.
Large domains
Figure 5-3 shows the structure of the domain is built up from chains of SDH
NE areas. Each chain links up to five SDH NE areas. The links between the
areas are E1 (2 Mbit/s) leased lines.
Figure 5-3
Maximum size domain
SDH NE SDH NE
Area 1 SDH NE Area 6-10 Area 5
All inter- or intra-area links are E1 (2 Mbit/s). An SDH NE area can contain up to 150 NEs.
The SDH NE area chains are linked back to two separate locations in the
management area. The management area can have only a single location, but
this reduces the availability of the management system.
Figure 5-4
Example of an SDH management area
Management Management
OSI and IP System OSI and IP System
5
Router Router Router Router
(2501/5/7) (2501) (2501) (2501/5/7)
M M M M M M M M
E1
E1
E1
OSI (L1/L2) and IP
The recommended SDH management area has two locations to provide a high
level of availability. A single SDH management location is possible but not
recommended.
The LAN connecting the router to the management systems supports IP and
OSI protocols. This means the ECs need only a single LAN port, which
supports IP and OSI.
Router (2514)
M
E1
M
to other
Management Management Management
System System Location
10BaseT 10BaseT
LAN Hub LAN Hub
M M M M
E1 E1
OSI (L2 only) and IP OSI (L2 only) and IP
SDH NE area
Figure 5-6 illustrates the structure of an SDH NE area. This is a common
structure. An STM-16 ring forms the backbone of the area.
Figure 5-6
Example of an SDH NE area
Router Router
OSI
OSI and IP
LAN OPC LAN
and IP 1X
OPC
4X 4X 1X
DCC
DCC CNET 16X CNET DCC
DCC
DCC
SDH NE Location
16X OSI 16X
SDH NE Location
5
DCC
16X
SDH NE Area
DCC disabled
4X
An optimum SDH NE area has two SDH NE locations with routers present. A
single-location area with a router present is not recommended because it
reduces 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 possible to
reach the 150-NE limit for the area.
When an STM-N link crosses the boundary of an SDH NE area, the DCC
must be disabled.
Figure 5-7
Example of an SDH NE area with SDH radio systems
SDH NE Area
Router Router
LAN LAN
OPC OPC
4X 4X
Clear Clear
Channel Channel
DCC DCC
4X
A router is needed at each end of the 64 kbit/s leased line. Configure the
router to bridge or route the OSI protocols.
SDH NE location
Figure 5-8 shows in more detail the structure of an SDH NE location with a
router present.
Figure 5-8
Example of an SDH NE location with a router present
M M SDH NE Location
Router (2505)
(OSI and IP)
OPC
LAN
Terminal
4X 1X
Server
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, NEs
with 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 external
10BaseT LAN hub is needed.
Small domains
Figure 5-9 shows that the minimum SDH DCN consists of a simple 10BaseT
LAN hub and DCC links to support simple SDH rings.
Figure 5-9
Minimal SDH DCN
NRM
IP LAN
10BaseT
LAN Hub
OSI LAN
10BaseT
LAN Hub
1X
1X
1X
STM-1 Ring
ECC
TN-1X Ring
TN-1X Ring
TN-1X Ring
TN-1X Ring
TN-1X Ring
TN-1X Ring
TN-1X Ring
1X
1X
ECC
ECC
ECC
ECC
ECC
ECC
ECC
1X
1X
1X
The DCN type shown in Figure 5-9 can be used in a small SDH management
domain when a smaller number of SDH NEs (<150) are present in the SDH
network.
In this case, provide the ECs with two LAN ports. Configure one LAN port
for 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 small
groups of remote NEs or link OPCs back to the NRM. In this situation, the
routers do not support OSI routing protocols; they are configured to route IP
and bridge OSI protocols.
Figure 5-10
Routers in a small domain
NRM
10BaseT
LAN Hub IP LAN
EC-4X EC-1
5
STM-1 Ring
Router (2514)
ECC
1X
1X
M M
1X
1X
1X
M M M M
OPC 1X
1X 4X OPC
CNET CNET
DCC
DCC
16X DCC 16X
EC-1 TN-1X
Shelf PDMX-E
ATU EC
LAN
ATU
10BaseT Baydel
LAN Hub ATU Box
ATU 16 x V.24
LAN 1X
LAN
ATU ATU
1X
1X
STM-1 Ring
ATU
1X
1X
ECC
ATU
TN-1X Ring
TN-1X Ring
TN-1X Ring
TN-1X Ring
TN-1X Ring
TN-1X Ring
TN-1X Ring
ATU
1X
1X
ATU
ECC
ECC
ECC
ECC
ECC
ECC
ECC
1X
LAN
ATU
PDMX-E V.24
PDMX-E
PDMX-E
PDMX-E
Non-interoperability
For network topologies not supported by the LAN/DCC alone, use G.703
2 Mbit/s WAN links and third-party bridge functionality (Cisco 250x bridge/
router plus X.21/G.703 modem).
Figure 5-12 illustrates the usage of a pair of LAN bridges linked via a G.703
2 Mbit/s circuit or 64 kbit/s leased lines.
Figure 5-12
Use of bridges in SDH networks
1X 1X 1X
STM-1 Ring
1X
EC-1 DCC
1X 1X 1X
LAN
10BaseT No DCC
1X
LAN Hub No DCC 10BaseT
LAN LAN Hub
LAN No DCC
No DCC Non OSI
1X
1X
1X
1X
Modem 2Mbit/s
G.703 Modem
G.703 2Mbit/s
OSI communications path
5
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 be due
to
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
Refer to the SDH DCN Commissioning Guide NTP 323-4061-210 for the
detailed configuration for the local terminal characteristics.
6
In an established SDH DCN, use Telnet to connect to remote routers from the
local router command line interface. This requires set-up of IP addresses in
the router network.
Access can also be obtained using Telnet/TCP/IP over a LAN port from a
UNIX workstation. Nortel recommends an Xterm window operating in
VT100 mode for Telnet connection to remote routers. This type of access
requires the IP addresses to have been set up correctly in the router and the
workstation. Therefore, use this approach only after the DCN has been
installed.
Figure 6-1
Access using Telnet/TCP/IP over a LAN port from a UNIX workstation
PC
UNIX WS
X.21 G.703
Serial 2 Mbit/s
Console Modem WAN
This release supports only configuration and diagnostics. Future releases may
support network-wide fault monitoring using SNMP.
Remote access
Remote access to the SDH DCN may be provided to a customer DCN for
general maintenance and diagnostics by Nortel staff. Note that it must be
done in a secure fashion.
Security strategy
DCN Release 2 offers improved security features:
Ciscos router password scheme is explained in more depth. Detailed
recommendations on its implementation are made.
Firewall functionality within routers is introduced. When the DCN is
connected to an external network, (for example, a customers Intranet)
access across the boundary of the two networks is controlled by using
access lists.
Passwords
The Cisco routers password scheme provides security. Use either of two
levels of password on the Cisco routers. The first level provides access to
view the configuration, while the second level enable provides full access.
Most routers are supplied with Cisco default passwords. It is essential that
these are changed for something unique to the device or part of the network in
which 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]).
Firewalls
Protection must be provided for the DCN network at every point where an
external connection exists. The firewall offers control over access by external
users to the DCN and if necessary restricts DCN users access to the Internet.
Using the access-list command from the IOS on a Cisco router, lists of IP
packets defined by source or destination address and packet type are allowed
or denied passage across the firewall.
6
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/pub/
acl-examples.
Determining requirements
Determine whether the DCN needs external access. If no external access is
required, the most effective firewall known is already in place. Otherwise,
ascertain from the network designer (and customer) what packets must pass
out of and into the DCN network and why such traffic is justified to support
the administration of the DCN.
Configuring
The Cisco IOSTM has a number of commands for firewall construction. (Refer
to the Cisco IOSTM software documentation on CD ROM for the full range of
commands.) 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 (access list).
Each entry matches or compares the source IP address of all packets
entering 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 decisions
based on a particular protocol or service.
Note 1: The standard form of the access-list command constructs access
lists with numbers from 1 to 99 and the extended form constructs access
lists 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 (except
packets from a specific address within that mask), write an entry with the
exception as a permit followed by the bar as a deny.
Thus a series of access lists may be constructed which completely
define the criteria for allowing passage of packets through the router.
show access-lists
All access lists will be listed. This is not a privilege command and the
lists are available to anyone who can log on to the router. A range of
Cisco IOSTM privilege commands prevents this.
IP access-group access-list-number, in/out
This command assigns an access list to an interface.
Remote access
Nortel recommends remote access via dial-back modems for security
purposes.
end of chapter
Dependability 7-
Design
Availability
Design the SDH DCN to be dependable. It should be proof against any single
link or equipment failure preventing the operation of the DCN.
Note that there is a cost penalty associated with high dependability. Unless
there is a clear requirement for full dependability which justifies the
additional DCN costs, maintain duplicated links but omit duplicate
equipment.
Reliability 7
In general, DCN components have a good level of reliability with high Mean
Time Between Failure (MTBF) figures.
Maintenance
In-country spares
Use the in-country spares policy to minimize the time to repair the DCN.
The target Mean Time To Repair (MTTR) for the DCN is approximately four
hours. Particular customers specify MTTR requirements for their SDH
networks and even their DCNs.
Hot spares
Where DCN components contain software, connect them permanently to the
network. They perform no useful function within the DCN but are present as
hot spares. This ensures that their functionality is monitored and that they
are 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 their
parking position and move them to the part of the network that they are
needed in. Update the access lists and password information.
Configuration backup
DCN components often require configuration to provide their function. This
configuration ranges from some DIL switch settings to a Cisco router
configuration.
Protocols 8-
Addressing
Overview
Note: Subsequent sections are Nortels preferred method of addressing.
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. 8
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
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 addressing examples
The following examples illustrate how this system works.
Figure 8-1
Two routers within an SDH NE area
Loopback 0 Loopback 0
Ethernet 0 Ethernet 0
LAN LAN
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, serial 1: unnumbered and referenced to loopback 0
router 1, Ethernet 0
router 1, loopback 0
router 2, serial 0: unnumbered and referenced to loopback 0
router 2, serial 1: unnumbered and referenced to loopback 0
router 2, Ethernet 0
router 2, loopback 0
Four separate subnetworks are required. These are the networks connected to
R1 Ethernet 0, R1 loopback 0, R2 Ethernet 0, and R2 loopback 0. The serial
ports are unnumbered and thus do not require subnetworks. In order to
provide four subnetworks, two bits are required.
8
If three bits are used for the subnetwork addresses, this gives provision for up
to 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 00001.
Therefore 00010 to 11110 are available for up to 29 other devices.
in binary:
11111111 11111111 11111111 111 00000
Subnetwork Host ID
in decimal: 255.255.255.224
Figure 8-2
Allocation of IP addresses
LAN LAN
Subnet: Subnet:
192.168.7.0 192.168.7.64
Network: 192.168.7.0
Figure 8-3
Routers within a management area
LAN
R3
Ethernet 0
Serial
Loopback 0
links
LAN LAN
R1
Eth 0 Eth 1 Eth 0
R2
Eth 1
8
Loopback 0 Loopback 0
Serial Serial
links links
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
router 2 - loopback 0
router 3 - loopback 0
Each serial loop supports up to 750 NEs. Each LAN in the management
area must therefore be capable of supporting enough workstations to
manage 750 NEs. Thirteen host IDs are not adequate, thus the management
areas will require multiple IP network addresses. This is achieved in the
following way:
network address 192.168.1.0 for router 1 - Ethernet 1, router 2 - Ethernet
1, 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. The
subnetwork mask for these two networks is 255.255.255.0. Up to 253
workstations or other devices can be connected to Ethernet 0.
Network address 192.168.1.0 has four subnetworks. To allow for addition of
extra serial loops and routers, use four bits for subnetwork address and the
remaining four bits for host IDs. The subnetwork mask is therefore
in binary:
11111111 11111111 11111111 1111 0000
Subnetwork Host ID
in decimal: 255.255.255.240
Table 8-1 shows possible address allocations.
Table 8-1
Addresses that can be allocated
continued
Table 8-1
Addresses that can be allocated
Subnetworks 192.168.1.64
available for future 192.168.1.80
expansion, though 192.168.1.96
each has only four 192.168.1.112
bits available for the 192.168.1.128
host ID 192.168.1.144
192.168.1.160
192.168.1.176
192.168.1.192
192.168.1.208
192.168.1.224
192.168.1.240
end
8
Figure 8-4 illustrates IP address allocation in a management location.
Figure 8-4
Allocation of IP addresses in a management location
Network 192.168.1.0
Subnetwork 192.168.1.0
LAN
R3
Ethernet 0:
192.168.1.1
Serial
Loopback 0: links
Network: Network: 192.168.1.17
192.168.2.0 192.168.3.0
LAN LAN
R1 R2 192.168.1.3
Loopback 0: Loopback 0:
192.168.1.33 192.168.1.49
Serial Serial
links links
Loopback interface
A 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 exist if a
connector falls out, or if the device at the other end of the cable fails for any
reason. The interface then shuts down and is removed from the routing tables.
Having an interface that always exists within a router is very useful for the
following reasons:
1 If a tunnel is set up between two router interfaces and one of the interfaces
fails, the tunnel will fail. However, when the tunnel is set up between two
loopback interfaces, if the normal route fails the tunnel will be re-routed if
another route exists and will not fail.
2 If a Telnet session is used to configure a router, if the interface goes down
that has the IP address to which the Telnet session is referenced, it will not
be possible to access the router unless the IP address of an alternative
interface is known. As the loss of an interface or part of the network is
exactly the kind of eventuality which requires reconfiguration of a router,
this is undesirable. If Telnet sessions are set up to access the router via the
loopback interface and any connection is up, the session will work.
3 Other interfaces can safely be referenced to the loopback interface. This is
known as an unnumbered interface. This applies only to point-to-point
interfaces (that is, not an Ethernet port). This reduces the number of IP
addresses needed and starts make router appear to have an address rather
than each interface. This starts to make the IP addressing structure more
similar to the OSI addressing structure and makes the network easier to
visualize.
Tunnel interface
Tunnelling is a method by which non-IP traffic (such as OSI) can be routed
across networks that support only IP. A tunnel can be set up between two
routers, whereby non-IP traffic is encapsulated into an IP format, sent across
the tunnel, and decoded at the other end. In this way, two OSI networks can
be linked together across an IP-only network. The two routers advertise the
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 appear the
same as any other IP packet to the IP network. Figure 8-5 illustrates the
concept.
Figure 8-5
Tunnelling
OSI network
IP only network
IP OSI
OSI packet encapsulated 8
within IP packet
OSI network
Note: The router at each end of the tunnel must support the protocol which
is being sent across the tunnel. It must have a tunnel interface configured
and referenced to the router at the other end of the tunnel.
Note: Each router can be anywhere within its respective OSI network
where there is an IP path to the other router which forms the tunnel. The
routers do not need to be at the edge of the part of the network which
supports OSI.
Addressing
An IP address points to an interface or network, whereas an OSI address
points to a device such as a router or SDH NE. OSI addressing is more
structured and controlled than IP addressing. The IP addressing schemes
recommended 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 example
used in Chapter 9 uses one management area and four SDH NE areas. A
different IP network address is used for each area. This type of approach is
not absolutely necessary to make IP function correctly, but it cannot be
avoided when designing OSI networks.
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 complete
OSI supports many different schemes for assigning the area address. Nortel
recommends only two schemes or formats:
1 the data country code (ISO DCC) format, which is to be used in networks
that contain more than one area and
2 the local format, which can be used only in smaller networks with one
area. #
One area can contain no more than 150 SDH NEs.
An OSI address that uses ISO DCC format is expressed in the following way:
39.076F.8012.3456.0000.dddd.aaaa.eeee.eeee.eeee.ss
This address has the following components: 8
39
This is called the AFI and specifies that the address uses ISO DCC
format.
076F
This is called the IDI and specifies that the country is Brazil (used as
an 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 addressing
is used. No other ISO DCC format is recommended by Nortel so this
is always set to 80.
123456
This is called the organization field. The correct code must be used for
the organization that owns the network. Use of the incorrect code may
well 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 used
by the owners of the network.
aaaa
This is the area (for example, 0001 for the management area, 0002,
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 this
address unchanged.
Often a shortened version of this format is seen. This is three bytes shorter
and has the two reserved bytes and one of the RD bytes removed. This is seen
in some management areas as it is a format used by EC-1 Release 6. This is
because 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-2
Using ISO DCC format
Step Action
end
Protocols
OSI supports two types of systems, ESs and ISs. An ES is equivalent to a host
in IP, and an IS is equivalent to a router.
Two ISs connected together and running IS-IS can use Level-1 and/or Level-2
routing.
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 which
are connected together but in different OSI areas should have only Level-2
routing 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 to
support both Level-1 and Level-2 routing, and interfaces which connect to
routers in other areas are configured to support only Level-2 routing. This
must be specified by the network designer for every interface of every
router which supports OSI routing.
SDH NEs which are connected together but in different OSI areas must be
8
prevented from exchanging routing information. This is achieved by
switching off or disabling the DCC between them. It is the responsibility
of the network designer to ensure that this is carried out.
Device configurations
Devices which require OSI configurations include EC workstations, SDH
NEs, 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 learn the
correct ISO DCC address from the routers via the following process:
Nortel SDH NEs are shipped configured with an OSI local address
of the form 49.0000.eeee.eeee.eeee.ss which is often referred to as
the default address.
Figure 8-6
Two routers within an SDH NE area
Loopback0 Loopback0
Tunnel
Ethernet0 Ethernet0
LAN LAN
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 Level-2
only)
metric for each interface
For the purposes of this example, the area will be part of a network belonging
to 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 0001
can be used.
This is area 0002. Area 0001 will be the management area. 8
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 with.
The default configuration for all interfaces is to allow Level-1 and Level-2
routing. Enter the commands into the serial port configuration of each router,
which leaves the area to allow Level-2 routing only. The serial ports which
connect the two routers within the area must be left as default (Level-1 and
Level-2 enabled).
This is because the SDH NEs have a priority of 64. In accordance with
the IS-IS protocol, whichever IS has the priority set numerically
highest is the designated router. Setting the routers to a Level-1
priority of 65 guarantees that one of the routers is the designated router,
not one of the SDH NEs. The designated router is the router which
advertises the LAN connectivity to all of the other routers and SDH
NEs 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 routed
through the path that has the lowest total metric. Set the routers metric
high enough to be unattractive to packets which are sent between
OPC pairs in a TN-16X ring
low enough to encourage traffic to a cross connect near to a router
to follow a direct path through the router, rather than using the
SDH network.
Setting 63 on the Ethernet ports and 20 on the serial ports achieves this,
provided 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 and
must have a higher metric than the serial link.
The routers must also be configured with the Nortel SDH NE default OSI
address
49.0000.eeee.eeee.eeee.00, where eeee.eeee.eeee is the MAC address
which the router is shipped with.
Figure 8-7 shows the area as configured for OSI.
Figure 8-7
Two routers within an SDH NE area
.
L1/L2 L1/L2
LAN LAN
R1: 39.076F.8012.3456.0001.0001.0002.1C3F.2B95.780E.00
49.0000.1C3F.2B95.780E.00
R2: 39.076F.8012.3456.0001.0001.0002.34A0.8C45.98F4.00
49.0000.134A0.8C45.98F4.00
The routers in all of the other areas are configured in the same way, except that
the 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 SDH NE
area one
39.076F.8012.3456.0000.0001.0003.eeee.eeee.eeee.ss for SDH NE
area two
39.076F.8012.3456.0000.0001.0004.eeee.eeee.eeee.ss for SDH NE
area three
39.076F.8012.3456.0000.0001.0005.eeee.eeee.eeee.ss for SDH NE
area four
Example 9-
Overview
This section contains a worked example of an SDH DCN design. It illustrates
how to apply the processes and tutorial information given in this document.
Introduction
Use 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 implementation
could be achieved in a number of ways. As a general rule, make access to and
from an external network either via a serial interface or from a dedicated
Ethernet port, but never from an Ethernet hub port. For further information on
firewalls, see Firewalls on page 6-3 or SDH DCN Commissioning Guide,
NTP 323-4061-210, Section 6.
The six rings are composed of optical interfaces. Most of the interfaces
between TN-1X and TN-16X are electrical interfaces. Connections
between TN-4X and TN-16X are a mixture of electrical and optical
interfaces. 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.
Northeast ring
Data Communications Networks Provisioning Guide
Central
ring
TN-16X
TN-16-4FR
Southeast
TN-4X
ring
STM-16
Example 9-3
Regenerator
SDH
Radio
9
9-4 Example
DCN topology
The first action is to group the SDH NEs into areas and allocate the routers.
Base the areas around STM-16 rings and include a management area. The
large sizes of the northwest and northeast rings make them obvious separate
areas. The remainder of the system will be 112 NEs. Given that the limit for
an area is 150 NEs, it is prudent to have two areas. The best connectivity is
between southwest and southeast as one area, and the central ring and the
radio system as another. The addition of a management area gives a total of
five areas. The TN-4X NEs used to connect STM-16 rings are all included in
the central/radio area.
Arrange the four areas in a chain. Connect each end of the chain to a
management area.
Figure 9-2
Management domain
SDH NE SDH NE
Area 1 Area 4
SDH NE SDH NE
Area 2 Area 3
Management area
The 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 (depending
upon platform). One is provided in each management location.
NRM: 2, 1 in each management location
OPC: 10, 2 per STM-16 ring/radio system
TN-4X EC TN-4X EC
NRM NRM
OSI and IP OSI and IP
M M M M
E1 E1
Notes:
One TN-1X EC is capable of controlling 64 NEs.
One TN-4X EC is capable of controlling 10 to 30 NEs (depending upon
platform); two are used in this network to protect the network against the
failure of one management location.
OPCs are deployed in pairs. One pair can control up to 18 STM-16
9
regenerators and 16 TN-16X NEs in a ring (24 NEs otherwise).
NRM is scalable to control an extremely large number of NEs. Two are
used in this network to protect the network against the failure of one
management location.
SDH NE areas
SDH NE area one consists of the northwest STM-16 ring. It requires two
router locations. Each router location contains an OPC, a router, and two
2 Mbit/s connections.
Figure 9-4
SDH NE area one
M E1 to management area
Router 1
M E1 to Router 2
LAN
DCC
OPC
CNET
E1 to area 2
M
No DCC Router 2
M
E1 to Router 1
Notes:
An OPC pair controls up to 16 TN-16X NEs and 18 STM-16 regenerators.
Place OPCs on opposite sides of the ring. This ensures that packets sent
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 data
communications 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 have
the DCC link to a shared TN-16X. The first two may have the DCC to the
TN-16X active and be connected to a LAN; after that, the others must be
connected via either the DCC or the LAN but not both.
The DCC of the TN-16X that connects to the next area must be switched
off.
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 SDH
radio system. Three router locations are required, as each OPC requires direct
connection to a router.
Figure 9-5
SDH NE area three
No DCC No DCC
OPC
CNET CNET LAN
CNET
E1 to area 4
M
Central
LAN M Router 3
ring E1 to Router 2
CNET
OPC
E1 E1
to to OPC
R1 R3 OPC
M E1 to area 2 M M
Router 1
M No DCC
E1 to Router 2 Router 2
No DCC
LAN
Notes:
An OPC pair controls up to 16 TN-16X NEs and 18 STM-16 regenerators.
Place OPCs on opposite sides of the ring. This ensures that packets sent
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 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 have
the DCC link to a shared TN-16X. The first two may have the DCC to the
TN-16X active and be connected to a LAN; after that, the others must be
connected via either the DCC or the LAN, but not both.
The DCC of the TN-4Xs that connect to the other areas must be switched 9
off.
If TN-4X electrical interfaces are used to connect to TN-16X or TN-1X,
there is no DCC. The NEs must be connected using a LAN (except for
connections 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
SDH NE area four includes an STM-16 ring and an STM-4 ring. Three router
locations are required.
Figure 9-6
SDH NE area four
No DCC No DCC
E1 to management area
M
M E1 to area 3 Router 3
M
Router 1 Southeast E1 to
M E1 to Router 2 ring Router 2
LAN LAN
OPC
CNET
OPC
Southwest ring
LAN
CNET
E1 to Router 3
M
Router 2
M
E1 to Router 1
Notes:
Router 3 is required to provide a second path for DCN to the southeast ring;
otherwise the failure of the SDH link between the southwest and southeast
link would result in loss of management of the southeast link. The E1 link
from router 3 to the management area must be implemented via the SDH
link 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 loss
of any one SDH link from isolating router 3.
An OPC pair controls up to 16 TN-16X NEs and 18 STM-16 regenerators.
Place OPCs on opposite sides of the ring. This ensures that packets sent
between the OPCs use the DCN rather than the ring.
Connect every OPC directly to a router.
Nortel recommends that DCN equipment be DC powered.
Management packets can be 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 have
the DCC link to a shared TN-16X. The first two may have the DCC to the
TN-16X active and be connected to a LAN; after that, the others must be
connected via either the DCC or the LAN but not both.
The DCC of the TN-16X that connects to the next area must be switched
off.
In this example, an optical interface must be used to connect the two rings
between TN-16X and TN-4X. The TN-4X electrical interface does not
support 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 is no
DCC. The NEs must be connected using a LAN (except for connections to
other areas when DCC is not wanted in any case).
E1 channels should travel by different routes to protect the DCN. VC-12
paths need to be diverse to carry E1s.
Addressing
The second action is to assign addresses to the DCN.
OSI addresses
For the purpose of this example, the ANSI country code format is used, using
an 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 does not
need to be specified, as it usually cannot be changed.
3 Routers in an area with no SDH NEs (that is, management areas) need only
the ISO DCC OSI address.
4 Send the installation engineer instructions for each serial interface. State in
the instructions whether the port is connected to another router in the same
OSI 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 two
routers in the same OSI area. See IP addresses for more details.
IP addresses
Assigning the IP addresses and subnetwork masks is a more involved process.
For a detailed description of IP networking and subnetworking, see IP
networks, subnetworks, and subnetwork masks on page 8-2.
This example uses the IANA class C addresses, which are reserved for private
networks. These are addresses 192.168.0.0 to 192.168.255.255.
Network addresses are chosen to align with the OSI areas; therefore, the IP
addresses 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 interface, and
two 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 for the
subnetwork mask.
The subnetwork mask is 255.255.255.224 for all routers and workstations
in the management area. In decimal, 224 is equivalent to 11100000 in
binary (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)
For each subnetwork, this leaves five bits to assign the host identifier (ID).
Four of the eight subnetworks are used as follows:
subnetwork 192.168.1.0 for router 1 loopback interface. The address of
the interface is 192.168.1.1 with subnetwork mask 255.255.255.224.
subnetwork 192.168.1.32 for router 1 Ethernet interface. The address
of 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.224
TN-1X EC1: 192.168.1.36 with subnetwork mask
255.255.255.224
TN-1X EC2: 192.168.1.37 with subnetwork mask
255.255.255.224
subnetwork 192.168.1.64 for router 2 loopback interface. The address
of 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 address
of 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.224
TN-1X EC1: 192.168.1.100 with subnetwork mask
255.255.255.224
TN-1X EC2: 192.168.1.101 with subnetwork mask
255.255.255.224 9
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 two
OPCs. Most of the devices connected to a router in an SDH NE area do not
support IP. In the case of this particular example, a subnetwork mask of at
least four bits from the last byte is recommended. This will make the
subnetwork mask 255.255.255.240, allowing up to 16 subnetworks per
network 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
For each subnetwork, this leaves four bits to assign host IDs. For each
subnetwork, the last four bytes are 0001 for the interface (either Ethernet or
loopback), then 0010 for the first OPC, and so forth.
Notes:
1 Large management areas for systems containing thousands of NEs may
well 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 loopback
interface.
4 Links between routers that are in the same OSI area should have a tunnel
interface configured between them in order to protect the OSI against link
failure. 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 router
at 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 suggests
linking the name to the physical location of the router.
Consider power supply for each location so that the correct part can be
purchased.
Location definition
One of the router locations from the northwest ring is used as an example to
illustrate 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
OPC
STM-1E ports
with no no with
DCC DCC DCC DCC
straight cable
TN-1X
straight cable
TN-1X
TN-1X
straight cable
9
Transceiver
10base-T
TN-1X
Ethernet ports
E1 E1
M Serial 0 Serial 1
M
X 21 Router
Notes:
1 TN-1Xs and TN-4Xs require an AUI to 10base-T transceiver to connect
their 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 together
using the hub instead of using the DCCs. Switch on the DCCs of only two
of the NEs connected to the hub.
5 Leave one hub port free for plugging in diagnostic equipment or terminal
in the future. If there are not enough hub ports for all the NEs, use DCCs.
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 LAN
ports.
OPC
OPC Ethernet cable
TN-16X CNET straight cable
Table 9-1 details all the DCN components needed for this site.
Table 9-1
Needed DCN components
end
See SDH DCN components list, Release 2 on page 14-7 for a complete
components list.
Installation information
This section describes an example of the format for the exchange of
information from the DCN designer to the installation team. For each part,
information needs to include
location
addressing
interfaces
9
configuration
connectivity
Table 9-2
Example location and connectivity table
end
Table 9-3
Example interface/configuration for area 1
Router 1 Router 2
end
Table 9-4
Example interface/configuration for area 2
Router 1 Router 2
continued
Table 9-4
Example interface/configuration for area 2
Router 1 Router 2
end
Table 9-5
Example of addressing, area 1
end
Where the quantity of DCN equipment does not justify using a rack, the rack
mounting brackets supplied with hubs and routers may be used to wall mount
instead. The use of these brackets is fully described in the appropriate user
documentation.
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 expected
(00C- +400C) and the maximum number of DCN components does not exceed
15, there is a standard list of components which can be added to the standard
supplied rack.
Castors
Castors and feet are supplied with the standard unit. The unit may be
manipulated into position with the castors and then made firm by lowering
the feet. As cables are attached to the unit, it is not recommended that the unit
is allowed to remain on castors
Fan units
No ventilation should be necessary for most installations. However, if fan
assistance is recommended by installation technology three fan units are
available and coded:
a top-mounted fan tray
a withdrawable fan tray
a front-mounted fan tray
Cantilever shelf
This is the recommended shelf for holding non-front-panel mounted
equipment (in Release 2, Fourthtrack/Market Vision modems). An empty
shelf 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 this
is less than the height of a cantilever shelf itself, no space needs to be left
above the shelf for ventilation.
Plain shelves are also available in two depths. As it is not possible to panel-
mount a plain shelf (as the height is minimal), a pair of chassis rails are
required to give front-to-back support.
Cable tray
Cables travelling vertically are held by this cable tray, which comes as part of
the standard rack. There is a cable tray for each rack height. It is important to
attach each cable individually to the tray. If cables are bundled and then
attached, the weight of the cable assembly may fall on one connector which
would be unable to take the strain.
Doors
An acrylic door is supplied as standard, as it would be required by most
customers to view equipment indicators. Plain and vented doors are available
as alternatives.
There is also a rear door option as an alternative to the standard panel if rear
cable access is required. The door is 5U shorter than the standard back panel
and the mounting kit includes a blank 5U panel.
10
Table 10-1
Standard items supplied with equipment
Manufacturer/ Description
Model
Cisco 2501 Power cord, 19 Rack Mtg. Kit, Wall Mt.g Kit, Console cable
(Router) 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 Power cord, 19 Rack Mtg. Kit, Wall Mtg. Kit, Console cable
(Router) 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 Power cord, 19 Rack Mtg. Kit, Wall Mtg. Kit, Console cable
(Router) 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 Power cord, 19 Rack Mtg. Kit, Wall Mtg. Kit, Console cable
(Router) 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 Power cord, 19 Rack Mtg. Kit, Wall Mtg. Kit, Console cable
(Router) 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
Allied Telesyn
International
CentreCOM 208
Transceiver
continued
Table 10-1
Standard items supplied with equipment
Manufacturer/ Description
Model
Baystack 106 19 Rack Mtg. Kit, Wall Mtg. Kit and documentation
10Base-T Hub
with 12 port RJ45
Connectors and
-48V DC Power;
Hub Order No.
CG1001A06
Baystack 107 19 Rack Mtg. Kit, Wall Mtg. Kit and documentation
10Base-T Hub
with 24 port RJ45
Connectors and
-48V DC Power;
Hub Order No.
CG1001A07
continued
10
Table 10-1
Standard items supplied with equipment
Manufacturer/ Description
Model
Baystack 101 Power cord, 19 Rack Mtg. Kit, Wall Mtg. Kit and
10Base-T Hub documentation
with 12 port RJ45
Connectors and *The seventh character (x) of the hub order number must be
240V AC Power; replaced with the proper code to indicate desired product
Hub Order No. nationalization, as indicated below:
CG1001x01*
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 Peoples Republic of China.
Baystack 102 Power cord, 19 Rack Mtg. Kit, Wall Mtg. Kit and
10Base-T Hub documentation
with 24 port RJ45
Connectors and *The seventh character (x) of the hub order number must be
240V AC Power; replaced with the proper code to indicate desired product
Hub Order No. nationalization, as indicated below:
CG1001x02*
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 Peoples Republic of China.
end
Web sites
Web sites for various DCN equipment manufacturers follow.
Cisco
Cisco Systems home page:
http://www.cisco.com/
Multi-Tech Systems
http://www.multitech.com/
Bay Networks
http://www.baynetworks.com/Products/
end of chapter
10
11
Table 12-1
Management sites
Table 12-2
Large system
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 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 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
Data Communications Networks Provisioning Guide
12-2 Appendix A: SDN DCN deployment engineering limits
Table 12-3
Small systems
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-4
LANs
Ethernet Both IP and OSI protocols may be present. Only a single protocol
LANs is available if no router is present.
Ethernet TN-1Xs should not be on IP LANs with ECs (with the exception of
LANs the OPC).
Ethernet A single LAN may have no more than 32 ISs attached. Include
LANs remote ISs connected by a bridge link in the total.
Ethernet A single LAN may have no more than 64 ESs attached. Include
LANs remote ESs connected by a bridge link in the total.
Ethernet Install no more than four physical layer repeaters between any
LANs two DTEs connected via a LAN.
Table 12-5
TN-16X CNET
CNET All SDH NEs can use a CNET link as part of the path to their ECs.
Table 12-6
SDH DCC Bandwidth and limitations
SDH NE The largest number of SDH NEs supported within a single domain
related 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 No more than 63 remote low rate SDH NEs may be managed via
related a single low rate SDH NE gateway. The remote NEs may be in
the span of control of several ECs.
Table 12-7
TN-4X
12
Data Communications Networks Provisioning Guide
12-4 Appendix A: SDN DCN deployment engineering limits
Table 12-8
TN-16X with low-order MUXs
SDH NE No more than 128 remote low rate SDH NEs may be managed via
related a TN-16X.
Table 12-9
TN-16X
SDH NE The management path between the OPC and TN-16X should
related 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-10
TN-16X with low-order MUXs
Table 12-11
Bandwidth requirements
Table 12-12
DCC
Table 12-13
EC-1 span of control
Table 12-14
EC-4X span of control
EC-4X span With 715/100 platform, span of control is 10 NEs; with G60 server,
of control span of control is 30 NEs.
related
12
Data Communications Networks Provisioning Guide
12-6 Appendix A: SDN DCN deployment engineering limits
Table 12-15
EC-16X, EC-16X 4F, and EC-64X span of control
end of chapter
13-1
Both OSI and TCP/IP protocols are in the SDH DCN. Interoperability using
standard protocols is a key feature of the SDH DCN. This enhances the
chance of interoperability with new SDH equipment and existing customer
LAN/WANs.
OSI protocols are used mainly for communication between the SDH NEs and
their 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 used to
provide management access to the external SDH DCN components.
Internet protocols
The following Internet protocols are supported in the SDH DCN, allowing
interoperability 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)
Data Communications Networks Provisioning Guide
13-2 Appendix B: Protocol reference information
IP addressing
The information in this section covers various aspects of Internet protocol
addressing as it relates to the SDH DCN.
The following OSI services and protocols are supported in the SDH DCN,
allowing 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 procedures
for operating over the connectionless-mode network server (CLNS), as
defined 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-mode
Network Layer Protocol (CLNP)
ESs only ES-IS routing information exchange protocol as an ES defined in
ISO/IEC 9542 (ES-IS)
ISs only ES-IS routing information exchange protocol as an IS defined in
ISO/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 in
ITU-T G.784 (D4-D12). Serial channel bit rate 576 kbit/s
SDH OSI LAN:
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 transceiver
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 on
ITU-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).
IS
L2 L2
Area B Area C
L1 L1
IS IS IS IS
L1 L1/L2 L1
L1/L2
L2
ES IS IS ES
Country codes are defined in ISO 3166; further definition is by the ISO
member body within each country (for example, ANSI for the United
States 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 as an
NSAP, 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-2
OSI address structure as defined in ITU-T X.213
IDP DSP
For more information on the structure of the OSI addresses, see ITU-T X.213
Network Service Definition.
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.
The AFI and the IDI are defined in the international standards. An address
allocation 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 an
ORG field value, it is allocated one from the list maintained by the authority.
The organization (for example, Telesp) is then responsible for defining the
values used in the RD and AREA fields.
The SID field is the physical address of the equipment, which is normally an
IEEE 802.3 MAC address administered by the IEEE. The first three octets
indicate 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
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-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 One Ethernet LAN port (AUI) (IS). The DCC ports are functional, but
connect Release 4 they are not currently used in Nortel networks.
continued
Table 14-1
NEs and respective ECs that may be connected to SDH DCN ports supporting
OSI protocols (continued)
Product/Release Specifics
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-2
Main element controller types (OSI system)
Controller Specifics
type
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)
EC-16X (1) Managed NEs - TN-16X, STM-16 4F, and X/40 SDH Radio
WX-5X 4F
(IS or ES)
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-2
Main element controller types (OSI system)
Controller Specifics
type
OPC (IS or ES) (1) Managed NEs - TN-16X, STM-16 4FR, and X/40 SDH Radio
end
Table 14-3
Routers forming the main components of the SDH DCN
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 one LAN port (AUI), two high-speed serial ports (X.21), IP, OSI, and DC
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 8-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports
DC (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 16-port LAN hub (10BaseT RJ45 DCE), two high-speed serial ports
DC (X.21), IP, OSI, and DC power
continued
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 two LAN ports (AUI), two high-speed serial ports (X.21), IP, OSI, and DC
DC power
end
Table 14-4
Components used to extend or construct LANs (Ethernet or CNET)
Ethernet LAN hubs (1) Allied Telesyn CentreCOM 8-port 10BaseT hub (RJ45), AC
power
(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
end
Table 14-5
Multi-Tech MT2834BL modem approvals with part numbers
Australia MT2834BLI-AUSTRALIA
Austria MT2834BLG-AUSTRIA
14
Belgium MT2834BLI-BELGIUM
Canada MT2834BL-DOC
Denmark MT2834BLI-DENMARK
Finland MT2834BLI-FINLAND
France MT2834BLF
Germany MT2834BLG
Greece MT2834BLI-GREECE
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
Norway MT2834BLI-NORWAY
Poland MT2834BLI-POLAND
Portugal MT2834BLI-PORTUGAL
Russia MT2834BLI
Singapore MT2834BLI-SINGAPORE
Spain MT2834BLI-SPAIN
continued
Table 14-5
Multi-Tech MT2834BL modem approvals with part numbers (continued)
Sweden MT2834BLI-SWEDEN
Switzerland MT2834BLI-SWISS
Turkey MT2834BLI-TURKEY
Ukraine MT2834BLI
end
Table 14-6
SDH DCN components list, Release 2
Model Interfaces Protocols/ Power/ Hardware MTBF Nortel Nortel PEC
IOS IP/
Enterprise
software
consump-
tion
Predicted
(P)/
actual (A)
CPC
14
Routers
Cisco 2 serial and IP only; 85 to 264 [CISCO2501] minimum P: 23 yrs A0678094 NTJM01AA
2501 1 LAN [SF25C-11.0.13 VAC, 47 to dual 4 MB Flash banks A: 122 yrs
(IP) 63 Hz; 40 W and 4 MB DRAM
Cisco 2 serial and IP and OSI; 85 to 264 [CISCO2501] minimum P: 23 yrs A0680001 NTJM01BA
2501 OSI 1 LAN [SF25A-11.0.13] VAC, 47 to dual 8 MB Flash banks A: 122 yrs
(Enterprise) 63 Hz; 40 W and 8 MB DRAM
Cisco 2 serial and IP only; -48V DC; [CISCO2501-DC] P: 23 yrs A0680010 NTJM01CA
2501 DC 1 LAN [SF25C-11.0.13] 40 W minimum dual 4 MB A: 122 yrs
(IP) Flash banks and 4 MB
DRAM
Cisco 2 serial and IP and OSI; -48V DC; [CISCO2501-DC] P: 23 yrs A0680011 NTJM01DA
2501 1 LAN [SF25A-11.0.13] 40 W minimum dual 8 MB A: 122 yrs
OSI DC (Enterprise) Flash banks and 8 MB
DRAM
Cisco 2 serial and IP only; 85 to 264 [CISCO2505] minimum P: 17 yrs A0680014 NTJM01EA
2505 8-port LAN [SF25C-11.0.13] VAC, 47 to dual 4 MB Flash banks A: 94 yrs
hub (IP) 63 Hz; 40 W and 4MB DRAM
Cisco 2 serial and IP and OSI; 85 to 264 [CISCO2505] minimum P: 17 yrs A0680018 NTJM01FA
2505 OSI 8-port LAN [SF25A-11.0.13] VAC, 47 to dual 8 MB Flash banks A: 94 yrs
hub (Enterprise) 63 Hz; 40 W and 8 MB DRAM
Cisco 2 serial and IP only; -48V DC; [CISCO2505-DC] P: 17 yrs A0680020 NTJM01GA
2505 DC 8-port LAN [SF25C-11.0.13] 40 W minimum dual 4 MB A: 94 yrs
hub (IP) Flash banks and 4 MB
DRAM
Cisco 2 serial and IP and OSI; -48V DC; [CISCO2505-DC] P: 17 yrs A0680167 NTJM01HA
2505 8-port LAN [SF25A-11.0.13] 40 W minimum dual 8 MB A: 94 yrs
OSI DC hub (Enterprise) Flash banks and 8 MB
DRAM
Cisco 2 serial and IP only; 85 to 264 [CISCO2507] minimum P: 17 yrs A0724751 NTJM02EA
2507 16-port [SF25C-11.0.13] VAC, 47 to dual 4 MB Flash banks A: 94 yrs
LAN hub (IP) 63 Hz; 40 W and 4 MB DRAM
Cisco 2 serial and IP and OSI; 85 to 264 [CISCO2507] minimum P: 17 yrs A0724752 NTJM02FA
2507 OSI 16-port [SF25A-11.0.13] VAC, 47 to dual 8 MB Flash banks A: 94 yrs
LAN hub (Enterprise) 63 Hz; 40 W and 8 MB DRAM
Cisco 2 serial and IP only; -48V DC; [CISCO2507-DC] P: 17 yrs A0724753 NTJM02GA
2507 DC 16-port [SF25C-11.0.13] 40 W minimum dual 4 MB A: 94 yrs
LAN hub (IP) Flash banks and 4 MB
DRAM
Cisco 2 serial and IP and OSI; -48V DC; [CISCO2507-DC] P: 17 yrs A0724754 NTJM02HA
2507 16-port [SF25A-11.0.13] 40 W minimum dual 8 MB A: 94 yrs
OSI DC LAN hub (Enterprise) Flash banks and 8 MB
DRAM
continued
Table 14-6
SDH DCN components list, Release 2 (continued)
Cisco 2 serial and IP only; 85 to 264 [CISCO2514] minimum P: 17 yrs A0680171 NTJM01JA
2514 2 LAN [SF25C-11.0.13] VAC, 47 to dual 4 MB Flash banks A: 126 yrs
(IP) 63 Hz; 40 W and 4 MB DRAM
Cisco 2 serial and IP and OSI; 85 to 264 [CISCO2514] minimum P: 17 yrs A0680172 NTJM01KA
2514 OSI 2 LAN [SF25A-11.0.13] VAC, 47 to dual 8 MB Flash banks A: 126 yrs
(Enterprise) 63 Hz; 40 W and 8 MB DRAM
Cisco 2 serial and IP only; -48V DC; [CISCO2514-DC] P: 17 yrs A0680174 NTJM01LA
2514 DC 2 LAN [SF25C-11.0.13] 40 W minimum dual 4 MB A: 126 yrs
(IP) Flash banks and4 MB
DRAM
Cisco 2 serial and IP and OSI; -48V DC; [CISCO2514-DC] P: 17 yrs A0680180 NTJM01MA
2514 2 LAN [SF25A-11.0.13] 40 W minimum dual 8 MB A: 126 yrs
OSI DC (Enterprise) Flash banks and 8 MB
DRAM
Terminal Servers
continued
Table 14-6
SDH DCN components list, Release 2 (continued)
High-speed modem
software actual (A)
14
Fourth- X.21 and 100/240V [SP-1-RA], [T-120], P: 17 yrs A0680486 NTJM01SA
track/ G.703(E1) -50/60 Hz; [PSU-INT] and A: 160 yrs
Market 120 ohm (or 2.5 W [CAB-X21MT]
Vision 75 ohm)
MicroMux
SP-1-RA
High-
speed
modem
and
router
cable
Fourth- X.21 and -48V DC; [SP-1-RA], [T-120], P: 17 yrs A0680499 NTJM01TA
track G.703(E1) 2.5 W [PSU-DC] and A: 160 yrs
Market 120 ohm (or [CAB-X21MT]
Vision 75 ohm
MicroMux
SP-1-RA
High-
speed
modem
and
router
cable
Ethernet transceivers
continued
Table 14-6
SDH DCN components list, Release 2 (continued)
LAN cables
continued
Table 14-6
SDH DCN components list, Release 2 (continued)
Variable
software actual (A)
32YCN01094***
14
length (specify code +
cable
assembly required cable
2x RJ45 length)
with
crossover
end
Table 14-7
Rack mounting kits and options available
continued
Table 14-7
Rack mounting kits and options available
Castors, set of 4 95000000/600 P0878638 NPS50088 AHACAC
Allied Telesyn
Mtg. Bracket 208 Transceiver AT-BRKT-0A P0878722 NPS50091 ACAEAE
end
Data country codes are defined in ISO 3166 and are listed in Table 14-8 (for
information only).
Table 14-8
Data country codes
AFGHANISTAN 004
ALBANIA 008
ALGERIA 012
ANDORRA 020
ANGOLA 024
ANGUILLA 660
ANTARCTICA 010
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
Table 14-8
Data country codes (continued)
BOTSWANA 072
BRAZIL 076
BULGARIA 100
BURUNDI 108
CAMBODIA 116
CAMEROON
CANADA 124
CHAD 148
CHILE 152
CHINA 156
COLOMBIA 170
COMOROS 174
CONGO 178
CUBA 192
CYPRUS 196
continued
Table 14-8
Data country codes (continued)
DJIBOUTI 262
DOMINICA 212
ECUADOR 218
EGYPT 818
EL SALVADOR 222
ERITREA 232
ESTONIA 233
ETHIOPIA 231
FIJI 242
FINLAND 246
FRANCE 250
GABON 266
GAMBIA 270
GEORGIA 268
GERMANY 276
GHANA 288
GIBRALTAR 292
GREECE 300
continued
Table 14-8
Data country codes (continued)
GREENLAND 304
GRENADA 308
GUADELOUPE 312
GUAM 316
GUATEMALA 320
GUINEA 324
GUINEA-BISSAU 624
GUYANA 328
HAITI 332
HONDURAS 340
HUNGARY 348
ICELAND 352
INDIA 356
INDONESIA 360
IRAQ 368
IRELAND 372
ISRAEL 376
ITALY 380
JAMAICA 388
JAPAN 392
JORDAN 400
KAZAKHSTAN 398
KENYA 404
KIRIBATI 296
continued
Table 14-8
Data country codes (continued)
KUWAIT 414
14
KYRGYZSTAN 417
LATVIA 428
LEBANON 422
LESOTHO 426
LIBERIA 430
LIECHTENSTEIN 438
LITHUANIA 440
LUXEMBOURG 442
MACAU 446
MADAGASCAR 450
MALAWI 454
MALAYSIA 458
MALDIVES 462
MALI 466
MALTA 470
MARTINIQUE 474
MAURITANIA 478
MAURITIUS 480
MAYOTTE 175
MEXICO 484
MONACO 492
MONGOLIA 496
continued
Table 14-8
Data country codes (continued)
MONTSERRAT 500
MOROCCO 504
MOZAMBIQUE 508
MYANMAR 104
NAMIBIA 516
NAURU 520
NEPAL 524
NETHERLANDS 528
NICARAGUA 558
NIGER 562
NIGERIA 566
NIUE 570
NORWAY 578
OMAN 512
PAKISTAN 586
PALAU 585
PANAMA 591
PARAGUAY 600
PERU 604
PHILIPPINES 608
PITCAIRN 612
POLAND 616
PORTUGAL 620
continued
Table 14-8
Data country codes (continued)
REUNION 638
ROMANIA 642
RWANDA 646
SAMOA 882
SENEGAL 686
SEYCHELLES 690
SINGAPORE 702
SLOVENIA 705
SOMALIA 706
SPAIN 724
SUDAN 736
SURINAME 740
continued
Table 14-8
Data country codes (continued)
SWAZILAND 748
SWEDEN 752
SWITZERLAND 756
TAJIKISTAN 762
THAILAND 764
TOGO 768
TOKELAU 772
TONGA 776
TUNISIA 788
TURKEY 792
TURKMENISTAN 795
TUVALU 798
UGANDA 800
UKRAINE 804
URUGUAY 858
UZBEKISTAN 860
VANUATU 548
VENEZUELA 862
continued
Table 14-8
Data country codes (continued)
VIETNAM 704
14
VIRGIN ISLANDS (BRITISH) 092
YEMEN 887
YUGOSLAVIA 891
ZAIRE 180
ZAMBIA 894
ZIMBABWE 716
end
end of chapter
Each diagram indicates the template that should be used in each router in the
topology.
The 2507 has a larger hub than the 2505. As the hub is not configured, it
follows that the configuration information for each router is the same. No
specific reference has been made to the 2507 in this section as the two router
may be used interchangeably (as with the 2501) in the context of these
configurations.
The following router templates (Nortel PEC code of the template shown in
brackets) are available. They are also held on the Nortel SDH DCN Web page
at http://47.217.33.140/DCN/.
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 the
router network.
Topology diagrams
Figure 15-1
Topology 1: Small network - point to point 2501/2505/2507s
NRM
EC 15
E0
NE
2501/2505/2507
S0 S1 Router config A
S0 S1
2501/2505/2507
E0 Router config A
NE
Figure 15-2
Topology 2: Small network - route IP, bridge OSI
NRM OPC
EC
E0 E1
NE
2514
S0 S1 Router config B
S0 S1
2501/2505/2507
E0 Router config A
OPC NE
Figure 15-3
Topology 3: Small network - ring of 2501/2505/2507s
NRM
EC
15
Router config A E0
NE
2501/2505/2507
S0 S1
S0 S1 S0 S1
2501/2505/2507 2501/2505/2507
E0 Router config A E0 Router config A
NE NE
Figure 15-4
Topology 4: Small network - ring of 2501/2505/2507s
NE NE
Figure 15-5
Topology 5: Large network - one 2501/2505/2507 in an NE area
Router config D
L2 only L2 only
S0 S1
2501/2505/2507
E0
NE
Figure 15-6
Topology 6: Three 2501/2505/2507s in an NE area
NE NE NE
Figure 15-7
Topology 7: Large network - management area with 1 site and 1-5 NE areas
E0 Router config D
15
2501/2505/2507
S0 S1
L2 only L2 only
Figure 15-8
Topology 8: Large network - management area with 1 site and 6-10 NE areas
L1/L2
Figure 15-9
Topology 9: Large network - management area with 1 site and 11-20 NE areas
E0 E1 E0 E1 E0 E1 E0 E1
2514 2514 2514 2514
S0 S1 S0 S1 S0 S1 S0 S1
Tunnel Tunnel Tunnel
Tunnel
Figure 15-10
Topology 10: Large network - management area with 2 sites and 1-5 NE areas
L1/L2
L2 only
Area 1-5
Figure 15-11
Topology 11: Large network - management area with 2 sites and 6-10 NE
L1/L2
L2 only L2 only
Figure 15-12
Topology 12: Large network - management area with 2 sites and 11-20 NE areas
E0 E1 E0 E1 E0 E1
2514 2514 2514
S0 S1 S0 S1 S0 S1
Tunnel Tunnel Tunnel
L1/L2
L1/L2
Example
The following router configurations are based on the example given in
Chapter 9. The configurations show the completed templates (C) for two
routers in an SDH NE area in Brazil. This is the same as Topology 4: Large
Network - two 2501/2505/2507s in an NE area.
One router is in location NW07 and the other router is in location NW13.
Figure 15-13
Example SDH NE area with two routers
NW07 NW13
L2 only L1/L2 L2 only
2501/2505/2507 2501/2505/2507
Tunnel
NE NE
Addressing information
OSI area address - 39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.00
Template C:
!
hostname <router location>
!
enable secret sdhdcn
!
clns configuration-time 20
clns holding-time 41
clns packet-lifetime 255
clns routing
!
interface Loopback0
ip address <interface IP address> <subnetwork mask>
! 15
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
ip unnumbered Loopback0
clns router isis
isis metric 20 level-1
!
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
Data Communications Networks Provisioning Guide
15-12 Appendix D: Router configuration diagrams and templates
!
end
When the templates addressing information is filled in for the two routers, the
following router configurations are produced.
interface Serial1
ip unnumbered Loopback0
clns router isis
isis metric 20 level-1
!
router isis
net 39.076F.8012.3456.0000.0001.0002.eeee.eeee.eeee.00
net 49.0000.eeee.eeee.eeee.00 15
!
router rip
network 192.168.2.0
!
line con 0
line aux 0
transport input all
line vty 0 4
password cisco
login
!
end
Ordering information for this unit is available from Nortel Engineering, who
will be able to offer some limited further support. Note that as management is
not a supported DCN feature, verification of such a system must be carried
out on a project-by-project basis.
end of chapter
ADM
Add-Drop Multiplexer
area
17
A 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 ISs.
Each area has an area address that uniquely defines the area and all the
systems it contains within a domain.
ATU
Asynchronous Telemetry Unit
AUI
Attachment Unit Interface (a DCE in a network element, a DTE in a drop
cable). Connection to 10BaseT LAN requires 10BaseT transceiver to be
provisioned.
autonomous system
An IP data communications network of hosts, routers, and networks under the
same administration. Inside the autonomous system, interior gateway
protocols such as RIP or OSPF are used to maintain routing information. It
functions as an independent system with regard to other IP networks. In order
to reach other Autonomous Systems, a gateway is required (for example,
running a Border Gateway Protocol).
bridge
Joins two or more LAN segments together at the OSI data link layer (layer 2).
Bridges are normally connected together in pairs--one at either end of a WAN
serial link. The terms transparent bridge or spanning tree bridge are
sometimes used to refer to bridges that link Ethernet LANs.
Bridges can be connected in a mesh network. Any loops created are broken,
by 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 DTEs (for
example, a maximum of four routers on the path between DTEs).
Cisco routers can be configured to support bridging for OSI and routing for IP
at the same time. This would normally be used in small SDH networks
(<150), when access to remote groups of SDH NEs is required.
CIDR
Classless Inter-Domain Routing
CLTP
Connectionless-mode Transport Protocol
CNET
Communications Network. Data bus used to connect OPC to TN-16X.
DCC
Data Communications Channel. Channel which is available to carry Ethernet
packets within the overhead of telecommunications links between NEs.
Supports only OSI protocol packets.
DCE
Data Circuit Terminating Equipment. Refers to the equipment that provides a
connection into a data transmission network. In this document the term is
used to refer specifically to the type of physical interface provided by the
equipment.
DCN
Data Communications Network
DIL
Dual In-Line
DTE
Data Terminal Equipment. This term refers to equipment that is to be
connected to a network. In this document the term is used to refer specifically
to the type of physical interface provided by the equipment.
EC
Element Controller. Consists of a workstation and software. Used to
configure one or more NEs. EC and NE are connected via a network which is
the DCN.
17
ECC
Embedded Communications Channel. See DCC.
end system
Provides a source and destination for data communications traffic. ESs can be
attached to one or more data communications links or subnetworks, but they
cannot pass data communications traffic between them. The Element
Controllers (ECs) and some NEs (for example, TN-1P and ATU) are ESs.
ES
End System. See above.
high-capacity SDH NE
NE which will multiplex Virtual Containers VC3 and above (that is, TN-16X,
TN16 4F, and TN-X/40).
host
An IP equivalent of the OSI end system. Examples of IP hosts connected to
the SDH DCN are network controllers, element controllers, and X terminals.
IANA
Internet Address Numbering Authority
IP
Internet Protocol
intermediate system
Can pass data communications traffic between subnetworks to which it is
connected. This functionality is sometimes referred to as routing. Most SDH
NEs and third-party OSI routers are ISs. ISs may be Level 1 or Level 2.
IS
Intermediate System. See above.
ITU-T
International Telecommunications Union Telecommunications
Standardization Section
LAPD
Link Access Protocol on the D-channel
LED
Light Emitting Diode
LAN
Local Area Network
low-capacity SDH NE
NE which will multiplex Virtual Containers VC12 and above (that is, all NEs
not regarded as high capacity, including ATU).
MOA
Managed Object Agent
MTBF
Mean Time Between Failures
MTTR
Mean Time To Repair
MSOH
Multiplex Section Overhead
NC
Network Controller
NE
Network Element. Refers to an element within the SDH network, such as a
TN-1X, TN-4X etc.
NET
Network Entity Title. OSI address used for routing purposes.
NIC
Network Information Center
NRM
Network Resource Manager. Workstation with software used to provide
network services across an SDH network. Connected to ECs via the DCC.
NSAP
Network Service Access Point. OSI address used for the purpose of
communication between users or applications.
323-4061-151 Release 2 Standard
List of terms 17-5
OPC
Operations Controller. Element controller used by TN-16X, TN16 4F, and
TN-X/40 radio.
OSI
Open Systems Interconnect
PVC
Permanent Virtual Circuit
PDMX-E
Primary Digital Multiplexer-Enhanced
private network
Network that is not connected to another network (specifically the Internet).
PSTN
Public Switched Telephone Network
repeater
17
Joins two or more LAN segments together at the OSI physical layer (layer 1).
An example of a repeater in the SDH DCN is the 10BaseT LAN hub, which is
a multiport repeater.
No more than four repeaters are allowed between any two DTEs connected to
an ISO 8802-3 10 Mbit/s baseband CSMA/CD or Ethernet LAN.
router
Joins two or more LAN segments together at the OSI network layer (layer 3).
Routers are normally connected to other routers over WAN serial links.
Cisco routers can be configured to route IP and OSI protocols if they have
Enterprise software. They can be configured to support one or both protocols
on an individual port basis.
SDH NEs that are classified as Intermediate Systems are OSI protocol
routers.
routing domain
An OSI data communications network of end systems, intermediate systems,
and networks under the same administration. Inside the routing domain,
intra-domain routing protocols (such as the ES-IS protocol and the IS-IS [L1/
L2] protocol) are used to maintain routing information. It functions as an
independent system with regard to other OSI networks. In order to reach other
routing domains, a gateway is required (for example, running an
inter-domain routing protocol).
RSOH
Regenerator Section Overhead
RD
Routing Domain. See above.
SDH
Synchronous Digital Hierarchy
STM
Synchronous Transport Module
TMN
Telecommunications Management Network
TCP/IP
Transmission Control Protocol/Internet Protocol
WAN
Wide-Area Network
end of chapter
References 18-
Standard texts
Nortel document references
32DMA00001ALP 1996 SDH Data Communications Network Bullet Point
Commercial Specification, Issue 1
32DSS00001AND 1996 Requirements for Interoperability within the SDH
DCN, Issue 1
25DPS00750ABD 1996 Requirements for Interoperability of STM1
Interface.
ITU recommendations
G.784 1994 Synchronous Digital Hierarchy (SDH)
Management 18
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 Interface
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 (ISO/
IEC 8602)
X.213 1993 Information technology - Network service
definition for Open Systems Interconnection
(ISO/IEC 8348)
Index 19-
A external DCN, device connections 5-1
external SDH DCN 5-1
addresses, allocation of 8-6
addressing
IP 8-2 F
IP vs OSI 8-10 firewall functionality 6-2
preferred method 8-1 firewalls 6-3, 9-1
private networks 8-2 firewalls, configuring 6-4
addressing schemes firewalls, determining requirements 6-3
large SDH network 8-1
asynchronous serial ports, remote 4-4 I
IANA class C addresses 9-10
B installation information 9-15
bridge link, purpose of 5-13 installation information, required 3-10
interface, unnumbered 8-8
C internal DCN, structure of 5-2
CIDR strategy 13-2 internal SDH DCN 5-2
internal SDH DCN components 5-2
19
component spares 3-8
internal SDH DCN, topologies 5-2
internal/external DCN, balancing 5-2
D Internet protocol addressing 13-2
data country codes 14-13 Internet protocols 13-1
DCN equipment configuration 3-9 interoperability requirements 13-1
DCN management strategy 6-1 interoperability restrictions 4-3
DCN repair 7-1 interoperability, EC/NE 4-1
DCN security strategy 6-2 IP 8-2
DCN, definition of 4-1 IP address 8-10
DCN, external 1-2 IP addresses
DCN, internal 1-2 assigning 9-10
DCN, main component types 4-2 IP addressing 13-2
device configurations 8-13 examples 8-2
document audience ix IP networks 8-2
IP/OSI protocol co-existence 5-3
E IS-IS
end-to-end interoperability 4-2 Level-1 routing 8-13
engineering limits 12-1, 16-1 Level-2 routing 8-13
equipment list, site-by-site 3-9 ISO DCC format
equipment options 10-6 usage 8-12
Ethernet ports 4-5 isolated SDH NEs 5-8
metric maximum 8-16
T
TCP/IP address strategy 13-2
technical support x
template addressing 15-10
terminal servers 4-4
topology diagrams 15-3
topology restrictions 5-7
tunnel, failure and re-routing 8-8
tunneling 5-3 19
tunnelling, definition of 8-9
W
WAN links 5-13
Web sites 11-1
Web sites, DCN equipment
manufacturers 10-6
Data Communications
Network
Provisioning Guide