Evolution & NetMaster - DCN Design Guidelines Rev A2

Guidelines
Rev.Date
Rev.
Document ID
28.05.2008
A2
Prepared by
Subject Resp.
Approved by
SBR
KA
ERB
Evolution Series - Netmaster

Data Communication Network (DCN) Design Guidelines
EVOLUTION SERIES
&
NETMASTER
DCN
GUIDELINES
Evolution & NetMaster_DCN Design Guidelines Rev A2.doc
Page 1(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
Document history
Revision
Rev A
Rev A2
Page 2(32)
Date
23.05.08
28.05.08
Summary of changes
First release
Corrected wrong spelling of XPAND mode. Inserted document
history.
Guidelines
Rev.Date
Rev.
28.05.2008
Document ID
A2
TABLE OF CONTENTS..........................................................................................................PAGE
1.
INTRODUCTION ............................................................................................................... 4
2.
2.1
2.2
2.2.1
2.2.2
MANAGEMENT NETWORK DESIGN GUIDELINES ........................................................ 4

General.............................................................................................................................. 4
Guidelines.......................................................................................................................... 4
Use of external routers ...................................................................................................... 4
Use of Ethernet wayside channel ...................................................................................... 6
3.
NETWORKS...................................................................................................................... 7
4.
4.1
4.2
4.3
4.3.1
4.3.2
4.3.3
DEFINITIONS.................................................................................................................... 8
STATIC ROUTING ............................................................................................................ 8
RIP..................................................................................................................................... 8
OSPF................................................................................................................................. 8
Backbone area .................................................................................................................. 8
Stub area ........................................................................................................................... 8
Example of arranging OSPF areas.................................................................................. 10
5.
5.1
5.2
5.2.1
5.2.2
5.3
5.4
CONSTRAINTS............................................................................................................... 11
DCN using external routers ............................................................................................. 11
DCN using Ethernet Wayside Channel (METRO only) ................................................... 13
Ethernet Wayside with Switch Enabled ........................................................................... 13
Ethernet Wayside Channel with Switch Disabled ............................................................ 15
Use of Area Border Routers (ABR) ................................................................................. 18
Limitations in number of Autonomous System Border Router (ASBR)............................ 20
6.
6.1
6.1.1
6.1.2
6.1.3
EXAMPLE OF DCN SETUP............................................................................................ 21

IP addressing example .................................................................................................... 23
Radio setup when using OSPF ....................................................................................... 23
Radio setup when using RIP ........................................................................................... 28
Radio setup when using static routing ............................................................................. 29
7.
7.1
7.2
7.3
7.4
HARDWARE SOLUTIONS FOR CONNECTIVITY.......................................................... 31

ROUTERS with multiple E1 ports.................................................................................... 31
SWITCHES...................................................................................................................... 31
Management of 3rd part equipment.................................................................................. 32
WWW links ...................................................................................................................... 32
Page 3(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
1. INTRODUCTION
These Guidelines are meant as a help for Network Design Engineers to design DCN for Nera Evolution
Series Radio Equipment and NetMaster management systems. The document is based on features available
in the R6-release of the embedded software. Co-existence with other Nera radios (InterLink, CityLink,
CompactLink etc) is not within the scope of the document, and must be handled separately.
2. MANAGEMENT NETWORK DESIGN GUIDELINES

2.1 General
When managing a large network of Evolution radios (or other radios), a Data Communication Network
(DCN) is required. How to build the DCN may be a challenge. Below there are some aspects to consider:
The depth of a network (how many elements in a row can you poll through the internal router of the
Evolution)
In case the networks are too deep, external routers with multiple WAN and LAN ports may be used.
These routers should be connected at 2Mb/s. The elements monitored through a router, we have called a
segment. The number of elements in a segment has to be considered. Alternatively the 2Mb/s Ethernet
Wayside may be used instead of external routers.
The number of segments connected through a 2Mb/s also has to be considered.
2.2 Guidelines
For efficient and reliable handling of management traffic in the network, it is recommended that some
network design guidelines are followed.
2.2.1 Use of external routers

When building a DCN, external routers may be used. Some useful terms related to this are:
Router segment
By router segment we mean a number radio network elements connected to an external router:
R o u te r S e g m e n t
The elements within the frame are all connected to the router in this segment.
Page 4(32)
Guidelines
Rev.Date
28.05.2008
Rev.
Document ID
A2
Depth
When monitoring remote sites, the management traffic has to be routed through a number of other
network elements. The number of elements the management traffic has to be routed through is
referred to as the network depth:
T h e re d lin e s in d ic a te s h o w m a n y ra d io
te rm in a ls a re c o n n e c te d in a c h a in . T h e
n u m b e r o f e le m e n ts c o n n e c te d in a c h a in
fro m th e re d m a in s ite in d ic a te s th e d e p th
o f th e c h a in .
Connection point
The connection point is the where the elements are physically connected to the router:
Connection point
Page 5(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
When a connection point manages many connected network elements, some constraints apply.
There is no constraint on the number of connections from the NetMaster. Also, the constraints given below
are guidelines, and not imposed by software. Thus it is possible to violate the constraints, but this will often
result in degraded network performance.
The following design guidelines/constraints should be followed:
Max depth 20 elements

Max 30 Elements in one segment
Each segment is connected to an external router
External router interconnection at minimum 2Mb/s
Max 500 elements connected through one 2Mb/s DCN channel
2.2.2 Use of Ethernet wayside channel

Instead of using the external routers, the 2 Mb/s wayside channel may be used for connecting the
management of the Evolution radio. This is possible only for METRO terminals (not XPAND), and the
Ethermapper license has to be available in the terminal (EVLIC-METRO-ETHERMAP). The wayside
channel is using bytes in the section overhead (SOH) of the SDH-frame. In these bytes the radio will carry
Ethernet traffic.
2 Mb/s Ethernet Wayside
(management traffic & user traffic)
SITE A
SITE B
LAN 1
LAN 1
For the systems using the built-in wayside channel, the guidelines suggested are:
Page 6(32)
OSPF is recommended for the routing

Max depth 20 elements
Max 30 Elements in each OSPF area
Evolution internal routers in Area 0 are interconnected at 2Mb/s Ethernet
wayside channel
Max 500 elements connected through one 2Mb/s DCN channel
Guidelines
Rev.Date
Rev.
28.05.2008
Document ID
A2
NOTE!
9 Minimum management channel is based on a 256 kb/s channel; the DCC channel.
9 If software download to the NEs is performed remotely, this requires a large bandwidth due to
the file size of the software. 256 kb/s may then be insufficient.
9 Single NE management via WEB browser may operate down to 64 kb/s.
3. NETWORKS
A Nera Evolution Radio Network is a collection of radio equipments. Radio Terminals or Traffic Nodes are
the basic building blocks of the network, and are called the Network Elements (NE). A group of NEs
connected via network interfaces (TCP/IP LAN) or radio interfaces (DCC) forms a Network Island.
NetMaster connects to network islands by TCP/IP LAN. Each NE in the network island has the capability of
gating network management information through the network interface to the other NEs in the island it
belongs to.
To be connected to other NEs there are several solutions. When the built-in router of the NEs is used to see
any remote station, this may cause extra design challenges. For an Evolution radio, the following drawing
shows how the system is made:
SU communication
LAN port
LAN port
Site 2
Site 1
Bandwidth on SU communication from Site1 to Site 2 via Radio is 256 Kb/s.

An equivalent drawing can be shown to visualize the functionality:
DCC Radio
LAN port
Interface
Interface
Interface
Router 1
Interface
LAN port
Router 2
Page 7(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
To be able to use the built-in router for management routing, the system has to be configured to use:
9 Static routing
9 Dynamic routing
o RIP
o OSPF
4. DEFINITIONS
4.1 STATIC ROUTING
Static routing describes a system that does not implement adaptive routing. In these systems routes through a
data network are described by fixed paths (statically). These routes are usually entered into the router by the
system administrator.
4.2 RIP
The Routing Information Protocol (RIP) was one of the most commonly used interior gate protocol (IGP).
Routing protocols on internal networks (and to a lesser extent, networks connected to the Internet) help
routers dynamically adapt to changes of network connections by communicating information about which
networks each router can reach, and how far away those networks are. RIP is a distance-vector routing
protocol, which employs the hop count as a routing metric. The maximum number of hops allowed with RIP
is 15, and the hold down time is 180 seconds. Originally, each RIP router transmits full updates every 30
seconds by default.
4.3 OSPF
The Open Shortest Path First (OSPF) protocol is a hierarchical interior gateway protocol (IGP) for routing in
Internet Protocol, using a link-state in the individual areas that make up the hierarchy.
An OSPF network is divided into areas, which have 32-bit area identifiers (often denoted in the dotted
decimal format of an IP address.)
A computation based on Dijkstra's algorithm is used to calculate the shortest path tree inside each area.
4.3.1 Backbone area
The backbone area (also known as Area zero or Area 0.0.0.0) forms the core of an OSPF network. All other
areas are connected to Area 0.0.0.0, and inter-area routing happens via routers connected to the backbone
area and to their own non-backbone areas (often referred to as Area Border Routers (ABR). It is the logical
and physical structure for the 'OSPF domain' and is attached to all nonzero areas in the OSPF.
4.3.2 Stub area
A stub area is an area which does not receive external routes, but does receive inter-area routes. This kind of
area is useful when, for example, all Internet access goes through Autonomous System Border Routers
(ASBR) in Area 0.0.0.0, but there are multiple paths to other nonzero areas in the OSPF domain.
Please note that the so-called Totally Stubby Area (TSA) and Not-So-Stubby area (NSSA), (extensions to
the Stub Area) are not supported by the NERA Evolution Series.
External routes are defined as routes which were distributed in OSPF from another routing protocol.
Page 8(32)
Guidelines
Rev.Date
28.05.2008
Rev.
Document ID
A2
Therefore, stub areas typically need to rely on a default route to send traffic to routes outside the present
domain.
Page 9(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
4.3.3 Example of arranging OSPF areas

Below an example of a possible network is shown.
Beach BSC
Area
DCN
BackBone
Area D
High Site
OSPF Area 0
OSPF Area 0
DCN
BackBone
Area B
DCN
BackBone
Area C
High Site
High Site
DCN
BackBone
OSPF Area 0
External Routers
DCN
BackBone
LAN
DCN
BackBone
OSPF Area 0
DCN
BackBone
DCN
BackBone
LAN
LAN
Evolution Routers
Static Routes between routers

OSPF to be enabled on
the Evolution Lan port
connected to the
External Router
Evolution Default Gateway =
External Router IP Address
OSPF Area 0
Page 10(32)
OSPF Area 0
OSPF Area 0
Guidelines
Rev.Date
Rev.
28.05.2008
Document ID
A2
5. CONSTRAINTS
5.1 DCN using external routers
For efficient and reliable handling of management traffic in the network, it is recommended that each
NetMaster connection point is set up according to the parameters described in Drawing 1 & 2:
SDH Backbone Site

SDH Backbone Site
SDH Backbone Site
SDH Backbone Site
2Mb/s
Wayside
2Mb/s
Wayside
SDH Backbone Site

2Mb/s
Wayside
SDH Backbone Site
SDH Backbone Site
SDH Backbone Site
2Mb/s
Wayside
2Mb/s
Wayside
2Mb/s
Wayside
2Mb/s
Management
DCN
2Mb/s
Management Center
Remote
Management Center
NetMaster
Server
LAN
100Mb/s
WAN
10Mb/s
LAN
10Mb/s
NetMaster
Client
WAN
10Mb/s
Remote
Management Center
NetMaster
Database
NetMaster
Client
NetMaster
Client
Drawing 1: Chain solution
Page 11(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
2Mb/s
Wayside
2Mb/s
Wayside
2Mb/s
Wayside
2Mb/s
Wayside
High Site
High Site
High Site
2Mb/s
Wayside
High Site
2Mb/s
Wayside
2Mb/s
Wayside
2Mb/s
Wayside
High Site
2Mb/s
Wayside
2Mb/s
Wayside
High Site
2Mb/s
Wayside
2Mb/s
Wayside
2Mb/s
2Mb/s
Management
DCN
2Mb/s
Management Center
Remote
Management Center
NetMaster
Server
LAN
100Mb/s
WAN
10Mb/s
LAN
10Mb/s
NetMaster
Client
WAN
10Mb/s
Remote
Management Center
NetMaster
Database
NetMaster
Client
NetMaster
Client
Drawing 2: Ring solution

Solution:
Several distributed connection points should be made in the network. This can be done using 2 Mb/s leased
lines or TCP/IP networks etc. (The example is showing 2Mb/s lines due to the use of external routers with
multiple WAN-ports).
Evolution elements are grouped into areas and connected through an external router to the 2Mb/s Wayside
channel.
Page 12(32)
Guidelines
Rev.Date
28.05.2008
Rev.
Document ID
A2
5.2 DCN using Ethernet Wayside Channel (METRO only)

As an alternative to the use of external routers for building a DCN, the Ethernet Wayside Channel of the
Evolution METRO may be used. No routing is then necessary; a flat management network may be
constructed. This design may be realized in two different ways, as described below.
5.2.1 Ethernet Wayside with Switch Enabled

When configuring the Switch Enabled (In-band management), the two ports of the METRO SU are
configured as a switch. This means that management traffic between the two SUs across the hop is not
separated from other types of traffic fed into one of the Ethernet-ports of the SU. We then need to connect
the two SUs to the same LAN, using a 2 Mb/s pipe. See the example below:
2 Mb/s Ethernet Wayside
(management traffic & user traffic)
SITE A
SITE B
LAN 1
LAN 1
When configuring this feature for the system, the following precautions have to be taken:
The SOH bytes of the SDH-frame have to be available (not used by other equipment).
SU Ethernet mapper is required to enable Ethernet traffic in SOH (Wayside) or VC-4, hence an
Ethernet Mapper License has to be installed. The product code for this license is EVLIC-METROETHERMAP.
Configuration for this feature is shown below:
Page 13(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
Enabling of Ethernet Wayside.
Enabling of the Switch Mode (In-band management).
Page 14(32)
Guidelines
Rev.Date
Rev.
28.05.2008
Document ID
A2
5.2.2 Ethernet Wayside Channel with Switch Disabled

When configuring the Switch Disabled, the two ports of the METRO SU are configured as two separate
ports carrying different traffic. The ETH1 port is used for management traffic; this traffic will not be routed
across the hop. The ETH2 port will carry other types of traffic, and this traffic will appear also on the ETH2
port on the opposite side of the radio hop. To combine the management traffic and other kind of traffic of the
wayside channel and let them appear on the opposite side of the radio hop, an external switch with VLANtagging possibility may be used. The management traffic and the other traffic will be kept isolated, not
visible for other users. See the drawing below:
2 Mb/s Ethernet Wayside (management
traffic & user traffic separated by VLAN)
VLAN 20
VLAN 7 + VLAN 20
SITE A
VLAN 20
VLAN 7 + VLAN 20
VLAN 7
LAN 1
VLAN 7
LAN 1
Note that VLAN tags used in the example above may be different at customer side.
Configuration for this feature is shown below:
Page 15(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
Enabling of Ethernet Wayside.
Enabling of the Ethernet Ports.
Page 16(32)
Guidelines
Rev.Date
28.05.2008
Rev.
Document ID
A2
When using the wayside channel for making the backbone ring, this ring will be a flat backbone area (all
Evolution terminals will be a part of the same LAN). When connecting spur links to area 0, OSPF-routing
can be enabled for the LAN ports in the backbone ring and the spurs.
Area 0
Area 1
Area 2
Are
a
Backbone area
Stub areas
Page 17(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
5.3 Use of Area Border Routers (ABR)

The use of stub areas is recommended to reduce the size and complexity of an area. To use a stub area, the
evolution radio being a member of both the sub area and area 0 may serve as an Area Border Router (ABR).
See drawing below:
Area Border
Router
AREA 0
AREA 1
AREA 3
AREA 2
Area 0
DCC
Radio
LAN
port
Interface
AREA 4
Area 1
DCC
Radio
LAN
port
Interface
Router 1
Interface
Router 2
Equvalent drawing
Page 18(32)
Guidelines
Rev.Date
28.05.2008
Rev.
Document ID
A2
Please note that two ore more ABRs are currently not allowed to be a member of the same Stub Area. See
the drawing below:
Area Border
Router
AREA 0
AREA 1
Note! This configuration should be avoided!
Page 19(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
5.4 Limitations in number of Autonomous System Border Router (ASBR)

In some cases we have to export static routing and export RIP to OSPF and vice versa. These options should
only be used when strictly necessary. When too many of such routers are used, the performance will be
degraded. It is recommended to keep the number of such routers at 3 or less. Please note that when using an
ASBR, the LAN-port has to be a part of the OSPF. Below there is shown an example of the use of ASBR:
OSPF Domain
OSPF
ASBR
LAN
RIP
WAN(E1)
LAN
WAN(E1)
RIP
RIP
RIP Domain
Page 20(32)
Guidelines
Rev.Date
Rev.
28.05.2008
Document ID
A2
6. EXAMPLE OF DCN SETUP

Below there is shown an example of how a number of network elements may be connected via external
routers. This is done in order to meet the requirements on maximum depth of the network.
SDH Backbone Site

SDH Backbone Site
SDH Backbone Site
SDH Backbone Site
2Mb/s
Wayside
2Mb/s
Wayside
SDH Backbone Site

2Mb/s
Wayside
SDH Backbone Site
SDH Backbone Site
SDH Backbone Site
2Mb/s
Wayside
2Mb/s
Wayside
2Mb/s
Wayside
2Mb/s
Management
DCN
2Mb/s
Management Center
Remote
Management Center
NetMaster
Server
LAN
100Mb/s
WAN
10Mb/s
LAN
10Mb/s
NetMaster
Client
WAN
10Mb/s
Remote
Management Center
NetMaster
Database
NetMaster
Client
NetMaster
Client
Page 21(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
For further studies, a subsection of the network example is used:
IP range 10.1.1.0 - 10.1.1.255

Subnet mask 255.255.255.240
Using this mask size there are 16 subnets available and 14 elements per site.
Configure Default Gateway in the Evolution NE closest to the external router and enable redistribute static
routes on OSPF interface.
In all other elements there is no need to set a Default Gateway.
Page 22(32)
Guidelines
Rev.Date
Rev.
28.05.2008
Document ID
A2
6.1 IP addressing example

In the following example, random IP-addresses are selected to show the purpose of routing. The routing over
the radio hop may be static or dynamic (OSPF/RIP).
Site2
Site1
RIP / OSPF / STATIC routing
Radio
192.168.1.2
Radio
192.168.1.1
eth
10.0.0.10
eth
10.0.1.10
Subnet
10 0 0 0
PC1
IP:10.0.0.1
GW:10.0.0.10
Subnet mask used in all ;

255.255.255.0
IP connection established, verfied by ping test..
Subnet
10 0 1 0
PC2
IP:10.0.1.1
GW:10.0.1.10
6.1.1 Radio setup when using OSPF

6.1.1.1 Site 1
Network setting Ethernet Port (eth0) and radio port (DIR0@1)
Page 23(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
OSPF Area setting

In this example only Area 0 is used.
OSPF Interfaces setting

In this case we are only using the Ethernet port and radio port (eth0 & DIR0@1)
Page 24(32)
Guidelines
Rev.Date
28.05.2008
Rev.
Document ID
A2
OSPF General setting

Here the enabling of OSPF is performed.
Page 25(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
6.1.1.2 Site 2
Network setting Ethernet Port (eth0) and radio port (DIR0@1)
OSPF Area setting

In this case only Area 0 is used.
Page 26(32)
Guidelines
Rev.Date
28.05.2008
Rev.
Document ID
A2
OSPF Interfaces setting

In this case we are only using the Ethernet port and radio port (eth0 & DIR0@1)
OSPF General setting

Here the enabling of OSPF is performed.
Page 27(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
6.1.2 Radio setup when using RIP

When using the RIP protocol for routing, there are two possible options available; RIP 1 and RIP 2. Both of
the connected terminals have to be set up the same way if they shall be able to communicate.
6.1.2.1 Site 1
The Network Setting will be the same as above (Ethernet Port (eth0) and radio port (DIR0@1)).
RIP Interfaces (Ethernet Port (eth0) and radio port (DIR0@1)
RIP General setting

Here the enabling of RIP is performed.
Page 28(32)
Guidelines
Rev.Date
28.05.2008
Rev.
Document ID
A2
6.1.2.2 Site 2
The Network Setting, RIP Interfaces & RIP General Setting will be the same as above (no area is needed
in RIP).
6.1.3 Radio setup when using static routing

6.1.3.1 Site 1
Static Route Setting
Page 29(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
6.1.3.2 Site 2
Static Route Setting
NOTE! In case the radio port shall be used as default gateway this has to be set as a static route. Ex: IPaddress 0.0.0.0 Mask: 0.0.0.0 Gateway = remote radio hop IP address
Page 30(32)
Guidelines
Rev.Date
Rev.
28.05.2008
Document ID
A2
7. HARDWARE SOLUTIONS FOR CONNECTIVITY

The recommended solution for connection of management tools/configuration tools to network islands is
described in section 4. Below the most common units used for this solution are listed.
7.1 ROUTERS with multiple E1 ports

Routers with multiple WAN and LAN ports may be used. These routers should be connected through E1lines.
Example of routers to be used:
Rad FCD-IPD dual E1 router
CISCO 2811 with Multiflex Trunk Voice/WAN Interface Card
7.2 SWITCHES
Sometimes there may be a need for more than two E1-ports of a router. See example below:
SWITCH
SWITCH
Ring3
Ring2
OPTIONAL
SWITCH
Ring1
LINK1
LINK1
LINK2
LINK1
LINK2
LINK1
SWITCH
Ring4
SWITCH
Site with more than 2

directions of E1
In such cases the use of external switches may be a solution.

Example of switch is Techaya ICE608ETR, 8 port 10/100 Switch -48VDC
Page 31(32)
Guidelines
Document ID
Rev.
Rev.Date
A2
28.05.2008
7.3 Management of 3rd part equipment

In case the same DCN is used for management of 3rd part equipment, such as rectifiers, routers etc., factors
such as the available number of ports on the switch and the bandwidth requirements of the various NEs in the
network must be taken into account.
7.4 WWW links

RAD: http://www.rad.com/
Cisco: http://www.cisco.com/
Page 32(32)

Evolution & NetMaster - DCN Design Guidelines Rev A2

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Evolution & NetMaster - DCN Design Guidelines Rev A2

Enviado por

Direitos autorais:

Formatos disponíveis

Guidelines

Evolution Series - Netmaster

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

MANAGEMENT NETWORK DESIGN GUIDELINES ........................................................ 4

EXAMPLE OF DCN SETUP............................................................................................ 21

HARDWARE SOLUTIONS FOR CONNECTIVITY.......................................................... 31

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

2. MANAGEMENT NETWORK DESIGN GUIDELINES

2.2.1 Use of external routers

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Max depth 20 elements

2.2.2 Use of Ethernet wayside channel

OSPF is recommended for the routing

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Bandwidth on SU communication from Site1 to Site 2 via Radio is 256 Kb/s.

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

4.3.3 Example of arranging OSPF areas

Static Routes between routers

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

SDH Backbone Site

SDH Backbone Site

SDH Backbone Site

SDH Backbone Site

SDH Backbone Site

Drawing 1: Chain solution

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Drawing 2: Ring solution

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

5.2 DCN using Ethernet Wayside Channel (METRO only)

5.2.1 Ethernet Wayside with Switch Enabled

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Enabling of Ethernet Wayside.

Enabling of the Switch Mode (In-band management).

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

5.2.2 Ethernet Wayside Channel with Switch Disabled

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Enabling of Ethernet Wayside.

Enabling of the Ethernet Ports.

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

5.3 Use of Area Border Routers (ABR)

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

5.4 Limitations in number of Autonomous System Border Router (ASBR)

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

6. EXAMPLE OF DCN SETUP

SDH Backbone Site

SDH Backbone Site

SDH Backbone Site

SDH Backbone Site

SDH Backbone Site

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

For further studies, a subsection of the network example is used:

IP range 10.1.1.0 - 10.1.1.255

Evolution & NetMaster_DCN Design Guidelines Rev A2.doc

6.1 IP addressing example

Subnet mask used in all ;

IP connection established, verfied by ping test..

6.1.1 Radio setup when using OSPF