Embedded IP Router in SDH Radio Application Note

7/27/2019 Embedded IP Router in SDH Radio Application Note

1/16

Application Guide

Rev.Date Rev. Document no.

04.10.2002 BPrepared by Approved by

Kjetil Alvestad Johnny Henriksen

Embedded IP router in Nera SDH radio

Copyright 2002 Nera Networks ASEmbedded IP router Example Rev B.doc Page 1(16)


OSPF Network Example

Subject:

Configuration of embedded CityLink and InterLink IP router. OSPF network examples.

DOCUMENT HISTORY

Version Date Changes

A 26-09-02 First issue

B 04-10-02 Added InterLink


2/16

Application Guide


04.10.2002 B


Copyright 2002 Nera Networks AS

Embedded IP router Example Rev B.doc Page 2(16)

1. INTRODUCTION ................................................................................................................ 3

1.1 OSPF Routing..................................................................................................................... 31.2 Software Requirements ...................................................................................................... 31.2.1 CityLink.............................................................................................................................. 31.2.2 NEW-NMS......................................................................................................................... 3

2. MANAGEMENT INTERFACES...........................................................................................4

2.1 CityLink ............................................................................................................................... 42.2 ECC (Embedded Communication Channel) ....................................................................... 52.3 Internal OSPF Router ......................................................................................................... 6

3. OSPF ROUTING EXAMPLE............................................................................................... 7

3.1 TCP/IP Configuration NE 1.2.............................................................................................. 83.2 OSPF Configuration N E 1.2.............................................................................................103.2.1 AREA............................................................................................................................... 103.3 Static Routes NE 2.2......................................................................................................... 15


3/16

Application Guide


04.10.2002 B




1. INTRODUCTION

This document is intended as a guide for configuration of the IP routing in the CityLink and InterLink. The

document will also show an example configuration of a CityLink network with OSPF routing.

1.1 Management DCN IP Routing

The CityLink and InterLink contains an embedded routing function, which enables routing of TCP/IP and

UDP/IP traffic between the various management interfaces in the radios. The routing protocol used is OSPF

(Open Shortest Path First) or RIP2 (Routing Information Protocol). This enables transport of IP based

management protocols for other telecom equipment over a CityLink or InterLink path/network.

OSPF Facts:

Link State protocol. All routers share topology of network, not IP routes

Based on topology and cost, each routers runs dijkstras algorithm to find the best path and to generate

routing table. Convergence is fast, and the network is fast to re-route (when faults have been found)

Very suitable for redundant networks

In stable networks very bandwidth efficient.

Specified in RFC 1583 & RFC2328

1.2 Software Requirements

1.2.1 CityLink

The OSPF and RIP2 routing functionality requires the following CityLink application software:

SW-CL2IDU-APP R2B00 or later

1.2.2 InterLink

The OSPF and RIP2 routing functionality requires the following InterLink application software:

SW-2KCN231-APP R3B00 or later

1.2.3 NEW-NMS

The OSPF routing function requires the following NEW-NMS software:

NEW-NMS R7D02 or later


4/16

Application Guide


04.10.2002 B




2. MANAGEMENT INTERFACES

All Nera radio relay systems has several build-in interfaces for management networking. Common for all

families is a connection inside a section, i.e. between two terminals, implemented by internal 64 kb/s datachannels, and use DCC bytes1 in the SOH in the SDH radios.

2.1 CityLink

The CityLink has several alternative communication ports in the equipment:

DCC radio

Ethernet 10baseT

Network InterfaceLocal Craft Terminal

DCC line

Local Craft Terminal to interconnect a CityLink network to the NEW-NMS

Electrical interface: RS-232

Baudrate: 1.200 - 115.200kbit/s

Protocol: Proprietary, Q1

Connector type: 9 pin D-sub, female

Cable (NERA code): UWMK3123, included in the NEW-NMS and Config. SW.

Two Network Interface (NI) ports to interconnect Nera Radio Relay equipment. If the Ethernet port isused only one port is available.


Baudrate: 1.200 - 115.200kbit/s asynchronous or

64 - 200kbit/s synchronous

Protocol: Proprietary, NNP (Nera Network Protocol)


10Mb/s Ethernet port to interconnect CityLink network to the NEW-NMS, or to interconnect radio sub-networks using a LAN/WAN (IP Tunnelling or OSPF/RIP routing)

LAN (TP): Twisted pair interface (IEEE802.3):

Embedded 10BASE-T Medium Attachment Unit (MAU).

Connector type: RJ-45

DCCr (or DCCm) SDH management channels. Both SDH line side and radio side can be used.

Protocol: NNP (proprietary), TCP/IP or Qecc

1 D1-D3 or D4-D12 for CityLink and InterLink.


5/16

Application Guide


04.10.2002 B




2.2 InterLink

The InterLink has several alternative communication ports in the equipment:

Local Craft Terminal to interconnect a InterLink network to the NEW-NMS


Baudrate: 1.200 - 115.200kbit/s

Protocol: Proprietary, Q1Connector type: 9 pin D-sub, female

Cable (NERA code): UWMK3123, included in the NEW-NMS and Config. SW.

Two Network Interface (NI) ports to interconnect Nera Radio Relay equipment. If the Ethernet port isused only one port is available.


Baudrate: 1.200 - 115.200kbit/s asynchronous or

64 - 200kbit/s synchronous

Protocol: Proprietary, NNP (Nera Network Protocol)


10Mb/s Ethernet port to interconnect InterLink network to the NEW-NMS, or to interconnect radio sub-

networks using a LAN/WAN (IP Tunnelling or OSPF/RIP routing)

LAN (TP): Twisted pair interface (IEEE802.3):

Embedded 10BASE-T Medium Attachment Unit (MAU).

Connector type: RJ-45

DCCr (or DCCm) SDH management channels. Both SDH line side and radio side can be used.

Protocol: NNP (proprietary), TCP/IP or Qecc

Ethernet 10BaseT

Network Interface (NI1 & NI2)

Local Craft Terminal (LCT2)

Local Craft Terminal (LCT1)


6/16

Application Guide


04.10.2002 B




2.3 ECC (Embedded Communication Channel)

The ECC channel can be configured by the operator. The DCC-r (D1 to D3) is used normally for ECC

purpose when the radio element is configured for RST, but any other available SOH byte can be used. In

MST configuration2 the DCC-m (D4 to D12) can also be used. When DCC-r is used the transmission

capacity is 192 kb/s, If another single SOH byte is used the transmission capacity is 64kb/s. The protocolused can be NNP (Nera Networking Protocol), TCP/IP or Qecc. The operator can configure the link layer

properties of the Qecc.

2.4 Internal IP Router

The figure below shows all CityLink/InterLink interfaces that handle OSPF/RIP protocol traffic.

Router

LAN

Port

NI

port

DCC

Radio

LAN port is used

as element address..

DCC

Line

Note! When LAN port is enabled, only one NI port is available.

The LAN port IP address is used as the IP address on the element.

2 Applicable when a build-in mux unit is used.


7/16

Application Guide


04.10.2002 B




3. CITYLINK OSPF ROUTING EXAMPLE

The following example explains how to set up the IP Routing in the CityLink using OSPF. CityLink

Network Element 1.2 (IP address 10.9.9.9) configuration is shown (see drawing below).Private IP Addresses with Subnetmask 255.255.255.248 is used.

Configuration sequence:

Check that IP Stack is available.

Define IP Address, including Subnetmask and Default Gateway.

Enable TCP/IP stack on the ports where IP traffic is sent.

Define one AREA (or more).

Define on which ports OSPF or RIP is used.

Enable OSPF or RIP.

Routing Table.

NI-NICitylink1.2

Citylink 1.1Citylink2.1

Citylink2.2

DCCr DCCr

LAN

IP 10.9.9.2

IP 10.9.9.25IP 10.9.9.17IP 10.9.9.9IP 10.9.9.1

Equipment with SNMP

based management, using the

Nera DCC channel as DCN.

LAN

IP 10.9.9.27


8/16

Application Guide


04.10.2002 B




3.1 TCP/IP Configuration NE 1.2

Check that IP Stack is available on the

CityLink elements.TheAvailable Functions Menu is found from

Equipment node.

Available functions menu.

Set the IP Address of the CityLink LAN port.

TheElement ID Menu is found from the

Element node.

Element ID menu.

Set the IP Subnetmask of the CityLink LAN

port.

The Communication Ports Menu is found

from the Equipment node.

Network Element 1.2 is not usingDefault

Gateway in the example.

IP SettingsCommunication Portmenu.


9/16

Application Guide


04.10.2002 B




The Communication Ports menu allows the

user to enable TCP/IP stack on the different

communication ports, LAN, NI, DCC Line

and DCC Radio.

In the example, CityLink 1.2 has to enableboth NI and DCC Radio port since these are in

use.

SelectDCCin the Communication Ports menu

to enable the TCP/IP stack on the DCC Radio.

DCC Communication Portmenu.

OpenNIin the Communication Ports menu to

enable the TCP/IP stack on the NI1

NI Communication Portmenu.


10/16

Application Guide


04.10.2002 B




3.2 OSPF Configuration N E 1.2

3.2.1 AREA

OSPF Area

Areas are used to put a boundary on the explosion of link-state updates. Flooding and calculation of the

Dijkstra algorithm on a router is limited to changes within an area. All routers within an area have the exact

link-state database. Routers that belong to multiple areas, and connect these areas to the backbone area are

called Area Border Routers (ABR). ABRs must therefore maintain information describing the backbone

areas and other attached areas. It is not recommended (according to Cisco) to have more than 50 routers in

one area.

OSPF Cost

The cost (also called metric) of an interface in OSPF is an indication of the overhead required to send

packets across a certain interface. The cost of an interface is inversely proportional to the bandwidth of that

interface. A higher bandwidth indicates a lower cost. There is more overhead (higher cost) and time delays

involved in crossing a 56k serial line than crossing a 10M Ethernet line. The formula used to calculate the

cost is:

cost= 10000 0000/bandwith in bps

Stub Areas

OSPF allows certain areas to be configured as stub areas. External networks, such as those redistributed from

other protocols into OSPF, are not allowed to be flooded into a stub area. Routing from these areas to the

outside world is based on a default route. Configuring a stub area reduces the topological database size inside

an area and reduces the memory requirements of routers inside that area.

In our example all CityLink:

belongs to the same Area 1

cost is set to 100.

Stub area is not used

Note! In order to edit the 'OSPF areas' settings, the OSPF protocol must be disabled in the General Setting

page.


11/16

Application Guide


04.10.2002 B




Open OSPF Areas menu from Equipment

node.

Define one AREA by selectingAdd.

Note!

A maximum of 4 areas are allowed for each

Network Element.OSPF Areas menu

SelectArea ID and Cost, for the new Area.

Area Id:

Identifies the current area.

Cost:

Default cost for the current area.

Possible values: 0 - 4294967295.

Stub Area, Not Used in the example:

When this checkbox is set, the current area is

configured as a stub network.

Define Network ranges for the Area by

selectingAdd:

Opens the 'Add OSPF Area Network Range'

dialog. Allows the user to add new network

ranges to the current area.

Add OSPF Areas menu


12/16

Application Guide


04.10.2002 B




AddNetwork range to the Area.

IP Network Address:

Enter the IP network address.

NB! The IP network address must be valid forthe given network mask entered below.

Mask:

Enter the network mask.

NB! The network mask must be continuous.

Advertise:

When this checkbox is set, the information

regarding this network range is advertised.

Range Cost:

An indication of the overhead required to sendpackets across the current network range.


Note!

A maximum of 8 network ranges are allowed

for each OSPF area.

Add OSPF Areas Network Range menu

Define on which ports OSPF is used

Define OSPF interface by selectingAdd.

Add:

Add a new OSPF interface to the list using theappearing dialog.

Edit:

Select a row and press 'Edit' to open the 'Edit

OSPF Interface' dialog. In this dialog the

settings for the selected interface may be

changed.


13/16

Application Guide


04.10.2002 B




TheAdd OSPF Interface andEdit OSPF

Interface dialogs may be opened from the

OSPF Interfacespage.

The dialogs are identical, but are handled

differently; the 'Add' dialog ads new OSPFinterfaces and the 'Edit' dialog edits existing

OSPF interfaces.

In the example Network Element 1.2 is using

the DCC and NI ports.

Cost:

An indication of the overhead required

sending packets across current interface.


Transmit Delay:The estimated number of seconds it takes to

transmit a Link State Update Packet over

current interface.

Default value is 1 second.


Area Id:

Identifies the OSPF area the current interface

is part of.

Designated Router Priority:

Indicates the current NE's reliability as adesignated router (DR). Higher values =

higher reliability.

0 = cannot be DR.



14/16

Application Guide


04.10.2002 B




The General Settingpage allows the user to

control the general use of the OSPF or RIP2

protocols for the selected NE.

Enable protocol: Select routing protocol(s)available to the interfaces on current Network

Element.

OSPF: Allow use of OSPF

RIP (not used in the example): Allow use of

RIP v2

Export to... (not used in the example):

The "Export to..." options allow the routing

information to be passed to the different

protocols.

For information to be passed between the

OSPF and RIP protocols, the current NE musthave both protocols enabled.

Routing information regarding static routes

may always be passed to enabled protocol(s).

Default metric:

The values entered in these controls set the

default metric used for the different protocols.

IP Configurable Interfaces:

List of interfaces available on the current NE

for the OSPF and RIP protocols.

Interfaces may be enabled for IP in theCommunication Ports page for the specific

interface (e.g. NI interface on CityLink).


15/16

Application Guide


04.10.2002 B




Monitor active routes for current Network

Element from this page.

3.3 Static Routes NE 2.2

In order to establish a routing between Nera Network Elements using OSPF or RIPv2 and other equipment

not using one of these standards, static routes must be used.

In the example Static Routes must be added to Network Element 2.2.

Add:

Add a new static route to the list using the

appearing dialog.

Edit:

Select a row and press 'Edit' to open the 'Edit

Static Route' dialog. In this dialog the settings

for the selected route may be changed.

Delete:

Deletes the selected row(s) from the list.


16/16

Application Guide


04.10.2002 B



TheAdd Static Route andEdit Static Route

dialogs may be opened from the Static Routes

page.

The dialogs are identical, but are handled

differently; the 'Add' dialog add new staticroutes and the 'Edit' dialog edits existing static

routes.

Destination: IP address of the destination for

current static route.

NB! The IP address must be valid for the

given subnet mask entered below.

Mask: Subnet mask for current static route.

NB! The subnet mask must be continuous.

Gateway: IP address of the gateway throughwhich the current static route may be reached.

Interface Id: Interface used by the static route.

Metric: Interface metric.


A maximum of 20 static routes is allowed for

each NE.

Embedded IP Router in SDH Radio Application Note

Documents

Transcript of Embedded IP Router in SDH Radio Application Note