Download - DCN Course

s

DCN Course

Siemens Radio IP Equipment Issue 2

IMC 6032 AEDG

DCN COURSE

Siemens Radio IP Equipment

Copyright (C) Siemens Mobile Communications S.p.A. V.le Piero e Alberto Pirelli, 10I-20126 Milano

Issued by Technical Assistance DepartmentS.S. 11 Padana Superiore, km 158I-20060 Cassina de’ Pecchi MI

Technical modifications are possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

Authors: A. Auditore, A. Costa, P. Cuccaro, M.GrandiAuthorized: Andrea Baldini

Documento IMC 6032 AEDGIssue 2, April 2005 - 2/77 -

DCN COURSE


INDICE1. OVERVIEW....................................................................................................................................5

2. DUAL-QADAPTER MANAGEMENT DESCRIPTION....................................................................6

3. SRAL MANAGEMENT DESCRIPTION.........................................................................................9

4. SRAL XD MANAGEMENT DESCRIPTION..................................................................................19

5. SRA3/SRA4 MANAGEMENT DESCRIPTION.............................................................................30

6. SKYWEB MANAGEMENT DESCRIPTION..................................................................................34

7. BUILDING A DCN WITH MW RADIOS........................................................................................37

7.1. INTER-WORKING SRALXD & SRAL.......................................................................................37

7.1.1. OVERVIEW...........................................................................................................................37

7.1.2. STATION WITH A ROUTER/DUALQ-ADAPTER.................................................................38

7.1.3. REMOTE STATION WITHOUT DUALQ-ADAPTER.............................................................41

7.1.3.1. USING THE D-EXTERNAL INTERFACE:.........................................................................41

7.1.3.2. USING THE F-INTERFACE:.............................................................................................42

7.1.3.3. USING THE V-BUS INTERFACE:.....................................................................................43

7.1.4. GENERAL NETWORK SCENARIO......................................................................................44

7.1.5. EXAMPLE OF NETWORK SCENARIOS..............................................................................46

7.1.5.1. USING THE D-EXTERNAL INTERFACE:.........................................................................46

7.1.5.2. USING THE ETHERNET INTERFACE (THROUGH DUAL Q-ADAPTER):......................47

7.1.5.3. USING THE F INTERFACE:.............................................................................................48

7.1.5.4. USING THE V-BUS INTERFACE (FOR SRAL XD SVR3.5):............................................49

7.2. INTERWORKING SRA3 & SRA4.............................................................................................50

7.2.1. OVERVIEW...........................................................................................................................50

7.2.2. EXAMPLES OF NETWORK SCENARIOS...........................................................................51

7.3. RING TOPOLOGY...................................................................................................................54

7.4. SRA3/SRA4 RING TOPOLOGY WITH THE METRIC LIMIT OF RIP.......................................55

8. IMPLEMENTATION OF SDH AND PDH NETWORK..................................................................57

9. LABORATORIES.........................................................................................................................60

9.1. PDH/SDH NETWORKS INTERCONNECTION........................................................................60

9.2. D-EXTERNAL CONNECTIONS...............................................................................................63

9.3. D-EMBEDDED CHANNELS.....................................................................................................65

9.4. INTERWORKING BETWEEN CISCO ROUTERS AND RAD FCD/IP......................................67

9.5. IP/OSI tunnelling.......................................................................................................................72


DCN COURSE



DCN COURSE


Revision

Edition Data Author Capitols Cause Mutation

01 July 2004

Agostino Auditore

All New Document

NA

02 April 2005

Antonio CostaPietro CuccaroMauro Grandi

All New Document

New Course

Acronym

ATM Asynchronous Transfer Mode

BTS Base Terminal Station

CLNP ConnectionLess Network Protocol

DCN Data Communication Network

DQA Dual Q Adapter

IP Internet Protocol

LAN Local Area Network

LCT Local Craft Terminal

MS Master Station

NB Node B

NE Network Element

NMS Network Management System

OSI Open Standard Interconnection

PDH Plesyochronous Digital Hierarchy

PMP Point-to-MultiPoint

PS Peripheral Station

PVC Permanent Virtual Circuit

RBE Routed Bridge Encapsulation

SDH Synchronous Digital Hierarchy

SRAL System Radio Access Low Capacity

TMN Telecommunication Management Network

VCI Virtual Channel Identifier

VPI Virtual Path Identifier

WLL Wireless Local Loop


DCN COURSE


1. OVERVIEW

This document describes the management features of the Siemens IP Radio equipments.

It should not be considered as a user manual of the devices described in the next sections, but rather as a guideline for the DCN planning in the most common design scenarios.


DCN COURSE


2. DUALQ-ADAPTER MANAGEMENT DESCRIPTION

The DualQ-Adapter network device supports TCP/IP protocol (RIP routing protocol included). Several communications channel are used in Dual Q-Adapter for management itself and to provide low capacity PDH Radio IP Equipments as SRAL, SRAL XD, to intercommunicate each other in a DCN scenario.

DualQ-Adapter is provided with:

Lan 10Base2 Ethernet interface

F interface

The F Interface is a 19.2 kbit/s asynchronous data channel for LCT connection (RS232C standard).

V-bus

The V-bus interface is a 128 kbit/s data bus with burst mode (HDLC frame). It is used to interconnect SRALs of the same station (RS485).

For DualQ-Adapter version H, local management is only possible through Ethernet interface.

The DualQ-Adapter is a gateway device able to support different functions according to the using mode:

Interface converter

This function allows the communication between NetViewer and a NE sub-network of NEs (SRAL) not provided with the Ethernet 10base2 interface but equipped with the V-bus interface.

In this mode, the DualQ-Adapter uses the following interfaces:

o Ethernet 10base2: NetViewer side

o V-bus: SRAL side.


BNCCable

HUB RJ45/BNCNetViewer

DualQ

SRAL SRAL

VBUSCable

RJ45Cable

DCN COURSE


Figure 1

IP Tunneling on CLNP

This function allows realizing a connection tunnel between IP networks through an OSI network.

This allows to Net Viewer to reach and to manage IP NEs (SRAL, SRA Series 3) installed on a remote IP sub-network, that can be reached through an OSI sub-network, without distinguishing if the NEs belong or not to the same IP sub-network of NetViewer.

In this mode, the DualQ-Adapter uses the Ethernet 10base2 interface.

Figure 2

Drop/insert of standard embedded D channel on SRAL

It allows the connection of SRAL clouds to NetViewer by means of a 2Mbit/s network.

For the transport of the supervision information, the drop/insert functionality of the embedded D channel of SRAL is used.

SRAL is provided with a embedded D channel with non standard proprietary protocol.

The insertion of the version H DualQ-Adapter (software release 4.5) in the SRAL sub-rack automatically determines the switching of the type of available protocol on the embedded D channel of SRAL:

o when version H DualQ-Adapter is equipped, the standard embedded D channel is available on SRAL (IP on Cisco HDLC protocol)

o when version H DualQ-Adapter is not equipped, the embedded D channel is available on SRAL with proprietary protocol of SRAL type.

The standard embedded D channel, which transports the TMN information of a whole SRAL cloud, is transmitted on a time slot of E1 tributary (2 Mbit/s) of SRAL

equipped with DualQ-Adapter, which acts as gateway.


HUB RJ45/BNC

SRAL SRAL

IP OSI

OSI

VBUSCable IP

IP

BNCCable

BNCCable

NetViewer

DualQ

SRA3 SRA3

OSIOSI

DualQ

DCN COURSE


Figure 3


SRALSRALDualQ-Ad.

Router

E1Cross-Connector

SRALSRALDualQ-Ad.

SRALSRALDualQ-Ad.

SRALSRALDualQ-Ad.

E1 – Time Slots 1,2,3,4

E1 – Time Slot 4

E1 – Time Slot 3

E1 – Time Slot 2

E1 – Time Slot 1

Eth. – TCP/IP

DCN COURSE


3. SRAL MANAGEMENT DESCRIPTION

The equipment of the SRAL family supports the TCP/IP (RIP routing protocol included) .

Several communication channels are used in SRAL, for the transmission of information concerning the PDH network management and supervision:

Integrated R1/R2 channel

The integrated R channel is a 64 Kbit/s synchronous data channel with TCP/IP protocol. It is a reserved channel in the radio frame and is used for the transmission of management information between two SRALs of two different stations via radio. In case of SRAL with 2x(1+0) and A/D-RPT configuration, there are two different integrated channels (R1 and R2). In case of SRAL with (1+1) configuration, the two channels R1 and R2 are used in protected mode; the redundancy is managed by SRAL hardware.

F Interface

The F interface is a 19.2 Kbit/s asynchronous data channel (RS-232C standard).

It is used for transmission of management information between the SRAL and LCT. It could to be used for transmission of management information between the SRAL and NetViewer Server through a router.

V-bus

The V-bus is a 128 Kbit/s data bus with burst mode (HDLC frame) and TCP/IP protocol.

It is used for the transmission of management information between SRALs of the same station.

D1/D2 channel

They are two interfaces of the Controller that can be used for the transmission of the TMN supervision information on two different physical interfaces (these options are mutually exclusive):

the external D channels (D-Ext external interfaces of the optional D-External Card)

or

the D channels embedded in the 2 Mbit/s tributary streams.

In case of equipment provided with optional V&D Channel Distributor unit (also known as D-External Card), the D1 and D2 channels are available at connector (D-External), for the possible connection towards other transmission systems.

The D-External interface is a 64Kbps V.11 contra-directional interface that implements the standard IP over proprietary protocol (RIP included).

D-Embedded channel: it is a 64 Kbps channel using a Time Slot of a E1 line tributary side, software configurable. D-Embedded channel can be enabled only


DCN COURSE


on the E1 line tributary configured to be transmitted over the radio frame. The Data-link protocol used for D-Embedded channel depends on whether the SRAL is provided with the H Dual Q-Adapter or not:

o when version SRAL is provided with H DualQ-Adapter, the Cisco HDLC protocol is used on the D-Embedded on SRAL

o when version SRAL is not provided with H DualQ-Adapter, the embedded D channel is available on SRAL with proprietary protocol of SRAL type.

By using the D channel, the supervision information can cross different transmission systems (e.g.: optical fiber systems) and reach other PDH networks.

Depending on System Type and on configuration of external interfaces, one or two D channels can be available:

In case of SRAL in 2x(1+0) and A/D-RPT configuration, there are two independent D1 and D2 channels, available to be configured on the D embedded channels or on the D-Ext interfaces.

In case of SRAL in (1+1) or (1+0) configuration, only one D-Ext channel or D embedded channel is available (the options are mutually exclusive).

D-Channel interface is fully routed and routing protocol RIPv1 announcements are supported.

User Channel

To extend the management visibility to NEs of other vendors, the User Channel interface (V.11) could be used.

As in figure 4, by using the User Channel it is possible to carry a 64 Kbit/s channel over the radio frame. The Routers could be replaced with a 64kbit cross-connector

Figure 4

It is necessary to use a Dual-QAdapter to connect the SRAL equipment to the Ethernet network.


Router

To Management System of other

Vendors

User Channel

Router

64k – V11 cable64k – V11 cable

To NEs of other VendorsSRAL SRAL

DCN COURSE


The DualQ-Adapter is connected into the network, on Ethernet interface, with the Customer DCN and it is directly connected, through the V-bus interface (RS-485 serial interface), to the SRAL that acts as access points to the SRAL network (see figure 5).

Figure 5

The use of routers allows the connection between a SRAL network and the NetViewer Server inside an Ethernet network context (Intranet or Internet networks).

The network access to SRAL clouds towards NetViewer can be made via a 2 Mbit/s network (see figure 6), using the DualQ-Adapter version H (Housed) and the drop/insert functionality from embedded D channel of SRAL.

The standard embedded D channel, which transports the TMN information of the whole SRAL cloud, is transmitted on a time slot of a (2Mbit/s) E1 tributary of the SRAL that acts as gateway.

All the time slots of the SRAL clouds can be managed in 2 Mbit/s signals via E1 cross-connector; these 2 Mbit/s signals are then demultiplexed and reported on the DCN network of NetViewer via a router (e.g.: Cisco router).

The DualQ-Adapter version H and the SRAL equipped in the same sub-rack are however seen by NetViewer as two independent NEs.


BNC Cable

DCNDCN

Converter HUB

RJ45/BNC

RJ 45 Cable

SRALDualQ-Ad.

Router

Router

NetViewer

Management Centre SRAL

DCN COURSE


Figure 6


SRAL

RJ 45 Cable

SRALDualQ-Ad.

Router

NetViewer

Management Centre

E1Cross-Connector

SRALSRALDualQ-Ad.

SRALSRALDualQ-Ad.

SRALSRALDualQ-Ad.

E1

E1

E1

E1

E1

DCN COURSE


From the point of view of the network, every SRAL is a device with dual function: the host and the router. This feature is possible because the SRAL is able to identify the destination (the SRAL itself, another SRAL, a router, a PC) on the basis of the IP address and consequently to route the message towards the proper network.

As a router, the SRAL is capable of branching the signal over different routes:

– towards its own circuits; in this case the SRAL behaves a host

– towards LCT or router, through serial line (F interface)

– towards a SRAL of the same station, through LAN (V-bus) or D channels

– towards a SRAL of another station, through radio (R or D channels).

In the figure below (Figure 7), SRALs of the same station are interconnected by means of a two-wire V-bus (half-duplex) with a daisy-chain structure that constitutes a sub-network of the PDH network.

Figure 7


SRAL

SRALSRALDualQ-Ad.

SRALSRAL

SRALV-Bus Daisy-Chain

Converter HUB

RJ45/BNC

BNC Cable

RJ 45 Cable

Router

To NetViewer

DCN COURSE


SRAL Addressing Rules:

For each SRAL two consecutive IP addresses must be reserved. The first IP must be assigned to the controller; the second IP address will be automatically assigned to the LCT connected via F interface.

All the IP classes A, B, C are allowed with relative subnet mask.

The IP addresses of all SRAL NEs connected with the radio unit via V-bus interface must belong to the same sub-network.

The IP address of the remote radio unit connected via R-Channel, D-Embedded, D-Ext, must be assigned on a different sub-network.

All subnet masks inside the same network must be chosen to be equal.

For each radio unit up to 3 Static Routes can be set.

The minimum bandwidth required to manage an island of 2 SRAL is 15 Kbit/s and it is possible to manage up to 64 NEs under a common gateway (Dual Q-Adapter).

It is possible to have a chain of up to 15 SRAL, it means 6/7 links due to the limit of the RIP protocol

The RIP routing protocol is enabled on the radio side, D-external and V-BUS interfaces of SRAL. The RIP routing protocol on these interfaces is enabled by default and it cannot be disabled.


DCN COURSE


SRAL D-embedded Channel Configuration

This section describes the configuration of the D-Embedded channel when using the H Dual Q-Adapter.

The Cisco HDLC D-Embedded channel must be configured on both the SRAL and the Dual Q-Adapter.

This is the screenshot (figure 8a) with the settings for the local SRAL equipment. Note that SRAL and DualQ Adapter are seen from Netviewer as two different NEs.

From SRAL “Configuration Tribs RTM” menu, it’s necessary to enable one or more tributaries. One of them will be used for inserting, into a 64kb/s timeslot, the supervision traffic:

Figure 8a

From the “D1-Channel” configuration menu, it’s possible to select one of the tributaries (only 1-4 are allowed) and the timeslot dedicated to the D channel.

In this example we have selected Trib 1 and Timeslot 1.

D1ext and D2 ext channels must be disabled.


DCN COURSE


Here below details of network settings for the remote SRAL NE (figure 8b):

Figure 8b

Note that D1-Channel on remote SRAL must be disabled.


DCN COURSE


Here below details of network settings for DualQ-Adapter connected into local SRAL NE:

Figure 9

On Vbus interface RIPv1 has been enabled.

On D-Interface (D-Channel in Configuration menu), it’s configured the IP Address, NetMask, Rip Enabled and Cisco KeepAlive to 60 sec.

More in details:IP address: It’s the IP address of the D-embedded standard interface and must be unique inside all IP network. Network administrator must assign the IP address.Net-Mask: is the netmask associated with D embedded IP address.

Enabling/Disabling RIPv1: It’s possible to enable/disable the propagation/search of RIPv1 messages with D embedded channel standard; options are:


DCN COURSE


Figure 10

Disabled: disabling of propagation/receiving of RIPv1 messages through D embedded standard channel. Enabled: enabling of propagation/receiving of RIPv1 messages through D embedded standard channel.Enabled-wMR: enabling of propagation/receiving of RIPv1 messages through V interface with metric resetEnabled-wIfPrio: enabling of propagation/receiving of RIPv1 messages through D embedded channel standard with forcing priority interface.Enabled-wIfPrio-wMR: enabling of propagation/receiving of RIPv1 messages through D embedded channel standard with both forcing the priority interface for RIPv1 packets and metric reset.

KeepAlive: It’s the time intervals within KeepAlive packets are transmitted (seconds between one KeepAlive packet and another). The KeepAlive value settled on DualQ-Adapter must be in acceptance with the value settled on the router (e.g.: Cisco router) used for Netviewer connection. Note: KeepAlive value settled to “0” means disabling transmission of KeepAlive packets. In this case it’s not available the signaling of connection status (alarm of D embedded channel “disconnected” appears).


DCN COURSE


4. SRAL XD MANAGEMENT DESCRIPTION

The management of the radio networks is based upon IP networks that use the RIPv1 protocol for the distribution of the routing information.

Each equipment is a host of the IP network, that has to correctly perform the routing of the supervisory information as well as the propagation of the routing information towards other hosts and networks/sub-networks.

For this purpose, the user has to configure the network parameters for each of the management interfaces.

RIPv1 routing protocol is supported on each interface, and it can be switched On/Off by NetViewer.

Several communication channels are used in SRAL XD, for the transmission of information concerning the PDH network management and supervision:

F interface (RS-232 serial interface), used for

o Local Craft Terminal (LCT) connection

o Point - point connection to an equipment of SRAL family for the transmission of the supervision information.

When a LCT is connected via F-Interface, SRAL XD radio unit assigns automatically a predefined IP address (its address plus 1) to the PC through the support of PPP protocol for parameters exchange.

The following rules must be followed to use the F interface:

o Inter-working with SRAL via F interface requires the rate setting to 19200 b/s on F interface.

o Connection with SRAL via F interface is a very slow connection (19,2Kb/s) and cannot be used to manage more than 3 radio links.

o Inter-working with SRAL via F interface in the same IP subnet requires the disabling of LAN and V-BUS interfaces.

o Inter-working with SRAL via F interface requires upgrading the IDU BOOT software to version 2.0 or greater.


DCN COURSE


Figure 11

Q/V Ethernet interfaces :

o V interface: 10BaseT Ethernet interface used for the connection between the Controller units of equipment belonging to the same station and for the connection between the equipment Controller and a supervisory system (NetViewer)

o Q interface: 10/100BaseT Ethernet interface used for the connection between the Controller units of equipment belonging to the same station and for the connection between the equipment Controller and a supervisory system (NetViewer)

For the connection between the Controller units of equipment belonging to the same station each Q interface must be connected only to a V interface (i.e connections between Q and Q or V and V are not allowed).

The availability of duplicated Ethernet interfaces (Q and V) permits to connect in daisy chain more SRAL XD units placed in the same station, avoiding the usage of an external Hub. The external Hub must be used when more than 4 SRAL XD units are to be connected together in the same station.

The router ID is inherited by the Q/V Ethernet interface IP address (unique IP address).

The IP addresses of all Network Elements connected to the same Ethernet LAN shall belong to the same IP Sub-network.


SRALXD

SRALSRALDualQ-Ad.

SRALXD

F-Cable

Converter HUB

RJ45/BNC

BNC Cable

RJ 45 Cable

Router

To NetViewer

DCN COURSE


Figure 12

R1 and R2 interfaces (Radio Channel) : channels embedded into the radio frame, reserved for the transmission, via radio, of the supervisory information. Their capacity is 64 Kbit/s full duplex. For each radio system, a R embedded channel is present:

o in case of System Type (1+0), only one R channel is available, because the device is equipped with one radio system only

o in case of System Type (1+1) H/S and (1+1) FD, one R channel only is available; the other R channel ensures the redundancy

o in case of System Type 2x(1+0) and A/D-Rep, both the R1 and R2 channels are available (the R1 channel is reserved for the system 1 and the R2 channel is reserved for the system 2).

Figure 13


SRALXDSRALXDHUB RJ45

RJ45 Straight Through Cable

Router

To NetViewer

R Channel

SRALXD SRALXD

R ChannelQ Int

V Int

RJ45 Cross-Over Cable



RJ45 Cable

RJ 45 Cable

Router

To NetViewer

R Channel

DCN COURSE


D1 and D2 : They are two interfaces of the Controller that can be used for the transmission of the TMN supervision information through two different physical interfaces (these options are mutually exclusive):

o the D-External interfaces (User/D-Ext external interfaces of the Access Unit)

or

o the D channels embedded into the 2 Mbit/s tributary streams.

D-external channel is a 64 Kbps V.11 channel available through external interfaces of the Access unit (alternative to the D-embedded).

D-Embedded channel: it is a 64 Kbps channel using a Time Slot of a E1 line tributary side, software configurable. D-Embedded channel can be enabled only on the E1 line tributary configured to be transmitted over the radio frame. The Data link protocol is PPP.

By using the D channel, the supervision information can cross different transmission systems (e.g.: optical fiber systems) and reach other PDH networks.

Figure 14


R1 R2

F Int.

R1+User Ch. 1

R2+User Ch. 2

D-Ext /User

Int. 1

D-Ext/User

Int. 2.

V

Q

Tributaries (Embedded D1/D2

channel)

D1

D2

“HUB”

User

Channel 1

User

Channel 2User Ch. 1

User Ch. 2

V-BUS Int. (for XD Plugin

SVR 3. 5)

CONTROLLER

DCN COURSE


Figure 15

The availability and the using mode of the D interfaces depends on the type of tributary interface, on the System Type and on the configuration of the external interfaces of the Access unit:

o Access NxE1 unit :

System Type 2x(1+0) and A/D-Rep:

D1 interface: it can be connected to the external D1 interface or to the embedded D1 channel


System Type (1+0), (1+1) H/S and (1+1) FD:


D2 interface: it is always connected to the external D2 interface. In this configuration mode the User/D-Ext 2 external interface cannot be configured to transport the User Channel information, as described later in this chapter.


R

D-Ext/User

Int. 1

D-Ext /User

Int. 2

F Int.

Tributaries Int. (Embedded

D1/D2 channel)

D1

D2

User Ch

User Ch.

V-BUS Int. (for XD Plugin

SVR 3. 5)

Radio Redundancy

V

Q

“HUB”

CONTROLLER

DCN COURSE


o Access NxT1 :

System Type 2x(1+0) and A/D-Rep:

D1 interface: it can be connected to the external D1 interface


System Type (1+0), (1+1) H/S and (1+1) FD:


D2 interface: it is always connected to the external D2 interface (the User/D-Ext 2 external interface is preset as external D channel)

The embedded D channels are available only with Access NxE1 unit.

Figure 16

The external D channels of the User/D-Ext interfaces and the embedded D channels represent alternative solutions:

when the embedded D1 channel is enabled, the D-Ext and D-Ext SRAL Compatible options of the User/D-Ext 1 interface are deactivated

when the embedded D2 channel is enabled, the D-Ext and D-Ext SRAL Compatible options of the User/D-Ext 2 interface are deactivated


RJ 45 Cable

Router

NetViewer

Management Centre

E1 Cross-ConnectorE1

E1

E1

E1

E1

SRALXD

SRALXD

SRALXD

SRALXDSRALXD

SRALXDSRALXD

SRALXD

DCN COURSE


when the User/D-Ext 1 interface is configured as D-Ext or D-Ext SRAL Compatible, the embedded D1 channel is deactivated

when the User/D-Ext 2 interface is configured as D-Ext or D-Ext SRAL Compatible, the embedded D2 channel is deactivated.

V-BUS : V-Bus interface is a RS485 bus (128Kbps Half Duplex) used for the interconnection, by means of a daisy-chain structure, with equipment of the SRAL family located in the same station.

This interface is mutually exclusive with the Q/V LAN interface.

It is available only from SVR 3.5 onward for IDU Plug-in versions with new Controller Card.

User channel:

To extend the management visibility to NEs of other vendors, the User Channel interface could be used (alternatively to the configuration of the D-External).

The Fig.12 shows a typical solution of User Channel connection.

Figure 17

By using the User Channel, it is possible to carry a 64 Kbit/s channel over the radio frame. In the figure above, the Routers could be replaced with a 64kbit cross-connector.

The User Channel can be configured on the same interface used for the D-Ext channel. Thus, only one among the two options can be configured on the SRAL XD.

Moreover, the availability and the using mode of the User Channel depends on the System Type:

o System Type 2x(1+0) and A/D-Rep: two User Channel can be configured (one for each radio frame)

o System Type (1+0), (1+1) H/S and (1+1) FD: one User Channel is available (on the configured radio frame)

If both SRAL and SRALXD must be connected together in a station, it is possible to use the D-External to extend the management visibility. The Fig.11 shows a typical solution of D-External connection.


SRALXDSRALXD

Router

To Management System of other

Vendors

User Channel

Router

64k – V11 cable64k – V11 cable

To NEs of other Vendors

DCN COURSE


For connection through D-Ext channel, a V.11 cable (Siemens coded) should be used between the SRAL and the SRAL XD (the SRAL must be equipped with D-external card).

In the SRAL XD use one of the two D-Connectors (named “User/D-Ext”) available on the front of the shelf. The chosen channel must be configured via software using the “IP SRAL Compatible” option in the related “NE Parameters” field.

Figure 18




Router

To NetViewer

R Channel

SRAL SRAL

R Channel

D- External Cable (V11)


D-Ext

DCN COURSE


SRAL XD Network Configuration

Figure 19

Several network parameters can be configured for each interface:

Network Protocol: It is the network protocol of the interface. Possible options are:

o None (Interface disabled)

o IP (Default) (IP over PPP, IP over Standard HDLC)

o IP SRAL Compatible (IP over proprietary HDLC, for connection to previous SRAL family)

Three different configuration are allowed for RIPv1:

o Enabled : the interface is used both for sending and for receiving RIP messages in order to update its routing table.

o Disabled : no RIP messages are sent; RIP messages received from this interface are ignored.

o Silent : no RIP messages are sent; RIP messages received from this interface are used to update the routing table.

Static Route Propagation: It allows the enabling or disabling of the propagation of all the static routing information through the relative interface. It is enabled by default.

Border Gateway: it excludes the information relevant to the sub-network from the routing tables forwarded through this interface, but keeps the classful network


DCN COURSE


information (i.e. performing an automatic summarization); this function can be enabled only if the interface is used for the direct connection with a different IP network. It is highly recommended to leave the Border Gateway option disabled (default value).

Ingress Summarization: when this option is enabled, the system sees the IP addresses as network/sub-network addresses; if the option is disabled, the system sees the IP addresses as host addresses. It is advisable to enable always the Ingress Summarization option (default value).

Metric Override: It allows forcing, on transmission as well as on reception, the reset of the RIP metric on the relative interface. The reset of the metric is a function that allows exceeding the threshold of 15 hops foreseen by the RIP protocol.

Static Routes

For each radio unit, up to 20 Static Routes can be set.

The Static Routes take priority over Dynamic Route.

Static routes propagation can be enabled for each interface.

Even if the propagation is enabled, it will be automatically disabled each time the related physical layer fails.

Figure 20


DCN COURSE


SRALXD Addressing Rules

The SRAL XD controller acts as a Router that routes IP packets through R,F,D and Q/V (or V-BUS) interfaces. A single IP address among all the interfaces must be set: this address is used to identify the network element controller.

For each SRALXD two consecutive IP addresses must be reserved. The first IP must be assigned to the controller, while the second IP address will be automatic assigned to the LCT connected via F interface.

All subnet masks inside the same network must be chosen to be equal (due to the “classful” behavior of the RIPv1 routing protocol).

The number of dynamic entries that can take places on NE routing table without routing throughput degradation is 130.

The IP Addresses of SRALXDs connected through radio link must belong to different sub-networks

The SRALXDs connected through V/Q Ethernet (or V-BUS) interface must belong to same sub-networks.

The IP Addresses of SRALXD/SRALs connected through the V11 (D-external) cable must belong to different sub-networks as for the radio link rules.

The RIP routing protocol is enabled on radio side, D-external and Ethernet (or VBUS) interfaces of SRAL XD. It could be disabled.

The minimum bandwidth required to manage an island of 2 SRALXDs is 15 Kbit/s. Then the required bandwidth must be increased up to 64Kbit/sec in case of 128 SRAL XD belong the same island.

Up to 15 SRAL XD (7 radio links) can be connected in daisy chain, without metric-override feature, due to the maximum metric value of RIP protocol.

The metric-override feature can be used only in daisy chain topologies, where no ring connections are used for resiliency purpose (possible communication loops). It is strongly recommended to apply metric-override no more than 2 times consecutively (convergence protocol and delay problems)


DCN COURSE


5. SRA3/SRA4 MANAGEMENT DESCRIPTION

The equipment of the SRA series 3 and SRA series 4 family supports the TCP/IP (RIP routing protocol included).

Several communication channels are used in SRA series 3 and SRA series 4, for the transmission of information concerning the SDH network management and supervision:

Integrated channel R1/R2

The integrated R channel is a 64 Kbit/s synchronous data channel with TCP/IP protocol. It is a reserved channel in the radio frame and is used for the transmission of management information between two SRA3/SRA4 of two different stations via radio. In case of SRA3/SRA4 with 2x(1+0) there are two different integrated channels (R1 and R2). In case of SRA3/SRA4 with (1+1) configuration, the two channels R1 and R2 are used in protected mode; the redundancy is managed by SRA3/SRA4 hardware.

R-Channel interface is fully routed and routing protocol RIP v1 announcements are supported.

Figure 21

F Interface

The F interface is a 19.2 Kbit/s asynchronous data channel (RS-232C standard) for SRA3 and 38.4 Kbit/s for SRA4.

It is used for transmission of management information between the SRA3/SRA4 and LCT. It could to be used for transmission of management information between the SRA3/SRA4 and NetViewer Server through a router.

Ethernet Interface

Both SRA Series 3 and SRA 4 support the TCP/IP protocol on the Ethernet interface (10base2 for SRA3, 10/100baseT for SRA4)


SRA4SRA4HUB RJ45

RJ45 Cable

Router

To NetViewer

R Channel

DCN COURSE


The Figure 22 shows an example of connection between NetViewer and SRA3/SRA 4.

Figure 22


BNC Cable

HUB RJ45/BNC

NetViewer

SRA3 SRA3

SRA4 SRA4

RJ 45 Cable

DCN COURSE


SRA3 Addressing Rules:

All interfaces used for management topics, namely R, Q, and F, supports the RIPv1 routing protocol. For the Ethernet interface, two different configuration are allowed for RIPv1:

Enabled: the interface is used both for sending and for receiving RIP messages in order to update its routing table.

Disabled: no RIP messages are sent; RIP messages received from this interface are ignored.

The SRA3 controller acts as a Router that routes IP packets through R,F and Ethernet interfaces. A single IP address among all the interfaces must be set, this address is used to identify the network element controller.

For each SRA3 two consecutive IP address must be reserved. The first IP must be assigned to the controller the second IP address will be automatic assigned to the LCT connected via F interface.

The IP address of the remote radio unit connected via R-Channel must be addressed on different sub-network.

For each radio unit up to three Static Routes can be set.



The IP addresses of the SRA3 must be only even.

Here below an example of SRA3 DCN planning.

Figure 23


BNC Cable

HUB RJ45/BNC

NetViewer

SRA3 SRA3

SRA3 SRA3

10.10.10.2/24

10.10.10.4/24

10.10.20.2/24

10.10.21.4/24

10.10.10.1/24

DCN COURSE


SRA4 Addressing Rules:

All interfaces used for management topics, namely R, Q, and F, supports the routing protocol. For each interface, 3 different configuration are allowed for RIPv1:

Enabled: the interface is used both for sending and for receiving RIP messages in order to update its routing table.

Disabled: no RIP messages are sent; RIP messages received from this interface are ignored.

Silent: no RIP messages are sent; RIP messages received from this interface are used to update the routing table.

The SRA4 controller acts as a Router that routes IP packets through R,F and Ethernet interfaces. A single IP address among all the interfaces must be set, this address is used to identify the network element controller.

For each SRA4 two consecutive IP address must be reserved. The first IP must be assigned to the controller the second IP address will be automatic assigned to the LCT connected via F interface.

The IP addresses of all NEs connected with the radio unit via Q interface must be belong the same sub-network.

The IP address of the remote radio unit connected via R-Channel must be addressed on different sub-network.


The number of dynamic entries that can take places on NE routing table without routing throughput degradation is 200.

For each radio unit up to 16 Static Route can be set.

Static routes propagation can be enabled for each interface.


Figure 24


RJ45 Cable

HUB RJ45/BNC

NetViewer

SRA4 SRA4

SRA4 SRA4

10.10.10.2/24

10.10.10.4/24

10.10.20.2/24

10.10.21.4/24

10.10.10.1/24

DCN COURSE


6. SKYWEB MANAGEMENT DESCRIPTION

SkyWeb is a point-to-multipoint ATM wireless system.

A SkyWeb network is based on a sectored cellular topology composed of one or more cells that may overlap. Each cell provides a point to multipoint communications mechanism consisting of a Master Station (MS) that communicates with a number of Peripheral Station (PS). A cell can be split into a maximum of 4 sectors.

Figure 25

The available management mode are Out-of-Band or In-Band.

Peripheral Stations can be managed only if the In-band Management configuration has been formerly performed: this configuration allows the Master Station to assign a pre-set IP address to each peripheral station before the Out-of-band management is performed for the first time.

After the configuration of the In-band Management, for each Peripheral Station (PS) the management channel is configured in order to manage from a remote site. After this configuration the Peripheral Stations can be managed with either In-band or Out-of-band Management.

Using the Cell LCT, each Peripheral Station can be assigned an IP address without the former In-band configuration.

SkyWeb System SVR 2.4 can be managed through NetViewer 6.0 SP2. The roadmap foresees the management of the next release 2.5 with NetViewer 7.0.


DCN COURSE


SkyWeb Addressing Rules

An IP address is required for each peripheral station

If In-Band management channel is configured, the MS and PS can belong to the same IP sub-network, but it is not mandatory.

If Out-of-Band management channel is configured, the MS and PS cannot belong to the same IP sub-network

The PSs within the same sector can belong to different IP sub-network

The PSs within different sectors can belong to the same IP sub-network

Out-of-band management: NetViewer is directly connected to the Master Station by means of a dedicated Ethernet interface. From this interface NetViewer can access the configuration of the Master Station and the configuration of all the Terminal Stations as well. This “direct” connection can be made remote through an IP network or a serial link as described below.

Figure 26

Characteristics:

• NMS is located in a remote site

• Management via IP Network

• Data Traffic via ATM Network

• (Master and Terminals) managed via Out of Band Management Interface

Constraints:

• IP connectivity at the Master site

• Static routes functionality at the Master Station




DCNDCN

Router

Router

NetViewer

Management Centre

PSPSMS

DCN COURSE


In-band management: NetViewer is connected to the Master Station with a dedicated ATM connection through a selected network interface. A PVC channel (<VPI, VCI> pair) is dedicated for the in-band management channel. By means of this unique PVC in-band management channel, the NetViewer can access the configuration of the Master station and the configuration of all the Terminal stations.

Figure 27

Characteristics:

• NetViewer is located in a remote site

• Management via ATM Network

• Data Traffic via ATM Network

• Master and Terminals managed via In Band Management Interface

Constraints:

• IP/ATM Equipment is required.



Fiber Optical

ATM Network

ATM Network

Switch ATMr

Router

NetViewerManagement Centre

PSPSMS

Switch ATMr

ATMInterface

Payload and Management

DCN COURSE


7. BUILDING A DCN WITH MW RADIOS

7.1. INTER-WORKING SRALXD & SRAL

7.1.1. OVERVIEW

As a rule, the interfaces used to connect the SRAL XD to the SRAL are the “Dext” or the “Q-Lan / V-Lan” Ethernet interface (the SRAL must be provided with the D-External card or with a Dual-Q Adapter).

From SVR 3.4, the F interface can be also used to connect the SRAL XD to the SRAL, but it has the drawback of a lower connection speed compared to Ethernet and D-External interfaces.

For SRAL XD Plug-in SVR 3.5 and onwards, the VBUS interface can be also used to connect the SRAL XD to the SRAL.

The connection speed of the different interfaces is reported here below:


1. SRAL F Interface: 19,2 Kbit/s

2. SRALXD F Interface: 38,4 Kbit/s

3. D-External Interface: 64 Kbit/s

4. VBUS Interface: 128 Kbit/s (only for SRAL XD Plugin SVR 3.5 and onwards)

5. SRAL Ethernet Interface: 10 Mbit/s

6. SRALXD Ethernet Interface: 10/100 Mbit/s

In the common networks, the gateway/grooming stations are generally provided with Routers and Dual-Q Adapters, then the Ethernet Interface is used. In the remote stations no additional devices are commonly present, then the D-external Interface will be preferred.

F-interface is generally used for single spurs appended to existing Network Elements where no extra-hardware is required.

For connection through Ethernet interface a HUB/LAN-Switch with both RJ45 and BNC interfaces should be provided (the SRAL must be equipped with a Q-Adapter/DualQ-Adapter card).

For connection through D-Ext channel a V.11 cable (Siemens coded) should be used between the SRAL and the SRAL XD (the SRAL must be equipped with D-external card).

For connection through F-interface a RS232 cable (Siemens coded) should be used between the SRAL and the SRAL XD (no need for extra hardware).


DCN COURSE


Here below some examples of Network Topology about the requirement to use in case of a station with or without Router/DualQ-Adapter and a final example for a general network topology.

7.1.2. STATION WITH A ROUTER/DUALQ-ADAPTER

Figure 28

SRAL XD and SRAL are connected through a HUB/LAN-Switch with both RJ45 and BNC interfaces.

SRAL must be equipped with “Q-Adapter/DualQ-Adapter” card (or connected through V-Bus to a stand-alone DualQ-Adapter equipment).

The IP Addresses of SRAL XD, Router and DualQ-Adapter Ethernet interfaces must belong to the same sub-network.

The IP addresses of DualQ-Adapter V-Bus interface and SRAL controller must belong to the same sub-network, different from the Ethernet previous one.

The IP Addresses of NEs connected through radio link must belong to different subnetworks


SRALXD SRALXD

SRAL

Station 1

Station 2

Station 3

BNC Cable

RJ 45 Cable

RJ 45 Cable

Router

SRALDualQ-Ad.

MultiPort HUB / Converter RJ45/BNC

DCN COURSE


The following picture describes a connection through V-BUS cable that is not possible because of the use of the V-BUS and Ethernet Interfaces on the SRAL XD at the same time.

Figure 29

When no MultiPort HUB – RJ45/BNC Converters are available, it is still possible to connect SRAL and SRAL XD (rel. 3.5) devices through a V-BUS cable as described in the following picture.

This connection, however, is deprecated: SRAL directly connected to the RJ45/BNC Converter, in fact, must forward the traffic generated by the other device(s) and this could overload the SRAL.

Figure 30


SRAL

Station 1

RJ 45 Cable

Router

Station 3

SRALXD 3.5

Station 2

SRALXD 3.5

V-BUS Cable

SRAL

SRAL

Station 1BNC Cable

RJ 45 Cable

Router SRALDualQ-Ad.

Converter RJ45/BNC

Station 3

SRALXD 3.5

Station 2

SRALXD 3.5

V-BUS Cable

DCN COURSE


SRAL XD and SRAL are connected through a V-BUS cable (for SRAL XD 3.5 only).

SRAL must be equipped with “Q-Adapter/DualQ-Adapter” card (or connected through V-Bus to a stand-alone DualQ-Adapter equipment).

The IP addresses of Router and DualQ-Adapter Ethernet interfaces must belong to the same sub-network.

The IP Addresses of DualQ-Adapter V-Bus interface, SRAL and SRAL XD must belong to the same sub-network, different from the Ethernet previous one.



DCN COURSE


7.1.3. REMOTE STATION WITHOUT DUALQ-ADAPTER

7.1.3.1. USING THE D-EXTERNAL INTERFACE:

Figure 31

Connect SRAL XD and SRAL using a V11 cable (coded by Siemens).

The SRAL must be equipped with the optional “D-External” card. This optional card is housed in the same slot of the “DualQ-Adapter” card.

In the SRAL XD use one of the two D-Connectors (named “User/Dext”) available on the front of the shelf. The chosen channel must be configured via software using the “IP SRAL Compatible” option in the related “NE Parameters” field.

The IP Addresses of SRAL XD and SRAL connected through the V11 cable must belong to different sub-networks as for the radio link rules.

The IP Addresses of NEs connected through radio link must belong to different sub-networks.


SRALXD SRALXD

SRAL SRALD-External

V11 cable

Station 2

Station 1

Station 3

To Supervision System

DCN COURSE


7.1.3.2. USING THE F-INTERFACE:

Figure 32

Connect SRAL XD and SRAL using a F cable (coded by Siemens). The speed connection of F Interface on SRAL XD must be settled to 19,2 Kbit/sec (Identical to the default speed connection of F Interface on SRAL equipment).

The IP Addresses of the SRAL and SRAL XD connected by F-interface can belong to the same subnet (IP addresses optimization) or not. In the case the IP addresses belong to the same subnet, the IP Address of the SRAL XD must be equal to the SRAL IP Address plus one.

The SRAL XD using the F-interface must have the Ethernet interface disabled in the case the IP addresses belong to the same subnet.

The IP Addresses of NEs connected through radio link must belong to different subnets.

Static route to 0.0.0.0 (default route) should be used only to address IP networks different from the proper one.

Note:For the correct functioning of the F-interface connection the IDU Boot Software must be updated to release 2.0 (the old one is the 1.8).


SRALXD

SRAL SRAL

F cable

Station 2

Station 1

Station 3

To Supervision System SRALXD

DCN COURSE


7.1.3.3. USING THE V-BUS INTERFACE:

Figure 33

SRAL XD and SRAL are connected through a V-BUS cable (for SRAL XD 3.5 only).

The IP Addresses of SRAL and SRAL XD must belong to the same sub-network.



SRALXD 3.5

SRAL

V-BUS

cable

Station 2

Station 1

Station 3

To Supervision System

SRAL

SRALXD 3.5

DCN COURSE


7.1.4. GENERAL NETWORK SCENARIO

In a general network topology, it’s possible to have stations with or without DualQAdapter. Here below an example of inter-connections between SRAL XD and SRAL NEs using different interfaces (Ethernet, D-external or F-int).

Figure 34


DCNDCN

SRAL

Station 1

Station 2

Station 3

BNC Cable

RJ 45 Cable

Converter HUB

RJ45/BNC

RJ 45 Cable

Station 5Station 4

RJ 45 Cable

V11 cable

SRALXD SRALD-External

SRALDualQ-Ad.

SRALXD

Router

SRALXD SRALXD

SRAL

Router

NetViewer

Management Centre

SRAL

RJ 45 Cable

SRALSRAL XD 3.5SRAL XD 3.5

V-BUS cable

Station 7Station 6

F cable

SRALXD SRALXD SRAL

Station 9Station 8

SRAL

DCN COURSE


Summary

Management Centre: Default gateway or static routes are necessary on NetViewer server in order to manage the NEs.

Station 1: The IP Addresses of SRALXD, DualQ-Adapter (Eth. interface) and Router Ethernet interface must belong to the same sub-network.

Station 4: The IP Addresses of SRALXD and SRAL, connected through V11 cable, must belong to different sub-networks as for the radio link rules.

Station 6: The IP Address of the SRAL XD connected by F-interface to the SRAL must be equal to the SRAL IP Address plus one in case they are in same subnet. The Ethernet interface of the SRAL XD must be disabled. The speed of F interface must be set to 19.2 Kbit/s (both NEs).

Station 8: The IP Addresses of SRALXD (rel 3.5) and SRAL must belong to the same sub-network.


DCN COURSE


7.1.5. EXAMPLE OF NETWORK SCENARIOS

Here below some practical examples using IP addresses.

7.1.5.1. USING THE D-EXTERNAL INTERFACE:

Figure 35

IP addresses rules:

1. The NEs connected through VBUS must be on the same sub-network.

2. The NEs connected through D-external cable must belong to different sub networks.

3. The NEs connected through radio Link must belong to different sub networks.

4. The RIP routing protocol is enabled on radio side, D-external and Ethernet interfaces of SRAL XD. The RIP routing protocol on V-BUS interface and radio side of SRAL is enabled by default and it cannot be disabled.

Network Destination Gateway

20.20.20.0 20.20.10.1

20.20.30.0 20.20.10.1

20.20.50.0 20.20.10.1

20.20.90.0 20.20.10.1


Radio

V-bus

LAN

20.20.20.3/24 20.20.90.1/24

20.20.20.1/24 20.20.50.1/24

20.20.30.1/24

20.20.10.1/24

D-External Cable

NetViewer Server

20.20.10.3/24

DCN COURSE


7.1.5.2. USING THE ETHERNET INTERFACE (THROUGH DUAL Q-ADAPTER):

Figure 36

IP addresses rules:

1. The NEs connected through VBUS must be on the same subnetwork.

2. The NEs connected through Ethernet cable must belong to same subnetworks.

3. The NEs connected through radio link must belong to different subnetworks.

4. The RIP routing protocol is enabled on radio side and Ethernet interface of SRAL XD and on Ethernet and V-bus interfaces of DualQ-Adapter. The RIP routing protocol on V-BUS interface and radio side of SRAL is enabled by default and it cannot disabled.

5. Default gateway or static routes are necessary on NetViewer server in order to manage the NEs:


20.20.20.0 20.20.10.1

20.20.30.0 20.20.10.1

20.20.50.0 20.20.10.1

20.20.90.0 20.20.10.1


Radio

V-bus

LAN

20.20.90.1/24

20.20.50.1/24

NetViewer Server

20.20.20.5/24

20.20.10.1/24

20.20.20.3/24

20.20.20.1/24

20.20.30.3/24

20.20.30.1/24

20.20.10.3/24

DCN COURSE



DCN COURSE


7.1.5.3. USING THE F INTERFACE:

Figure 37

1. The IP Address of the SRAL XD connected by F-interface to the SRAL must be equal to the SRAL IP Address plus one (case of IP addresses belonging to the same subnet).

2. The Ethernet interface of the SRAL XD connected by F-interface to the SRAL must be disabled.

3. The IP Addresses of NEs connected through radio link must belong to different sub-networks.

4. The NEs connected through V-BUS must be on the same sub-network.

5. The RIP routing protocol is enabled on radio side and F interface of SRAL XD. The RIP routing protocol on F interface, V-BUS interface and radio side of SRAL is enabled by default and it cannot be disabled.



20.20.20.0 20.20.10.1

20.20.50.0 20.20.10.1

20.20.90.0 20.20.10.1


Radio

V-bus

LAN

20.20.20.3/24 20.20.90.1/24

20.20.20.1/24 20.20.50.1/24

20.20.20.2/24

20.20.10.1/24

F Cable

NetViewer Server

20.20.10.3/24

DCN COURSE


7.1.5.4. USING THE V-BUS INTERFACE (FOR SRAL XD SVR3.5):

Figure 38

1. The IP Addresses of NEs connected through radio link must belong to different sub-networks.

2. The NEs connected through V-BUS (the SRALs and the SRAL XD) must be on the same sub-network.

3. The RIP routing protocol is enabled on radio side and V-BUS interface of SRAL XD. The RIP routing protocol on F interface, V-BUS interface and radio side of SRAL is enabled by default and it cannot be disabled.



20.20.20.0 20.20.10.1

20.20.50.0 20.20.10.1

20.20.90.0 20.20.10.1


Radio

V-bus

LAN

20.20.20.3/24 20.20.90.1/24

20.20.20.1/24 20.20.50.1/24

20.20.20.2/24

20.20.10.1/24

F Cable

NetViewer Server

20.20.10.3/24

DCN COURSE


7.2. INTERWORKING SRA3 & SRA4

7.2.1. OVERVIEW

The interfaces used to connect the SRAL4 to the SRA3 is the Ethernet.


SRA3 Ethernet (10 base 2) Interface: 10 Mbit/s

SRA4 Ethernet (10/100 base T) Interface: 10/100 Mbit/s

In the common networks, the gateway/grooming stations are generally provided with Routers, then the Ethernet Interface is used. In the remote stations a HUB/LAN-Switch with both RJ45 and BNC interfaces should be provided.

Here below an examples of Network Topology.

Figure 39


BNC Cable

HUB RJ45/BNC

NetViewer

SRA3 SRA3

SRA4 SRA4

RJ 45 Cable

SRA4 SRA4

SRA4 SRA4

HUB RJ45/BNC

HUB RJ45Station 1 Station 2 Station 3

DCN COURSE


7.2.2. EXAMPLES OF NETWORK SCENARIOS

The DCN performs the OSPF routing protocol

Figure 40

The WAN interfaces of Router01, Router02 and Router03 are configured with the OSPF routing protocol.

The Ethernet interface of Router02 is configured with the RIP routing protocol in listening mode (passive interface is configured on Ethernet interface). The listening mode on Ethernet interface avoids that wasteful routing entries, coming from other network segment, are propagated to the SRA3/SRA4. The excessive number of routing entries on SRA3/SRA4 could bring to a standstill of management.

Static Route must be inserted on SRA3/SRA4 of “Grooming Node” toward NetViewer.

Equipment Network Destination

NetMask Gateway

SRA3 0.0.0.0 - 10.10.20.1

SRA4 0.0.0.0 0.0.0.0 10.10.20.1


DCNDCN

10.10.20.2/28

10.10.20.4/28

10.10.20.1/28

10.10.20.18/28 10.10.20.20/28

10.10.20.49/28 10.10.20.51/28

10.10.20.54/28

10.10.20.82/28

NetViewer

10.10.10.1/2410.10.10.2/24

10.10.11.1/30

10.10.11.2/30

Router01 Router02

Grooming Node

Router03

Other equipment

10.10.20.65/28

10.10.20.33/28

DCN COURSE


Default Gateway must be inserted on NetViewer toward NE.


DCN COURSE


The DCN is configured in bridged mode:

Figure 41

All the routers are configured in bridged mode.

On NetViewer, Default Gateway must be set to either the SRA 3 or SRA4 Gateway, to point to the NEs.


DCNDCN

10.10.20.8/28

10.10.20.5/28

10.10.20.18/28 10.10.20.19/28

10.10.20.49/28 10.10.20.51/28

10.10.20.54/28

10.10.20.82/28

Router01 Router02

Grooming Station

Router03

Other equipment

10.10.20.65/28

NetViewer

10.10.20.2/28

10.10.20.33/28

DCN COURSE


7.3. RING TOPOLOGY.

The ring topology is a particular network planning when we want to create a DCN protected.

Here below an example of ring topology:

Figure 42

The Ring Topology permits the supervision of every Radio Equipment also in state of radio link failure.

Figure 43


DCNDCN

10.10.20.2/28

10.10.20.4/28

10.10.20.1/28

10.10.20.18/28 10.10.20.20/28

10.10.20.49/28 10.10.20.51/28

10.10.10.1/24

10.10.11.1/30

10.10.11.2/30

Router01 Router02

10.10.20.35/28Ring Topology

10.10.20.33/28NetViewer

10.10.10.2/24

DCNDCN

10.10.20.2/28

10.10.20.4/28

10.10.20.1/28

10.10.20.18/28

10.10.20.20/28

10.10.20.49/28 10.10.20.51/28

10.10.10.1/24

10.10.11.1/30

10.10.11.2/30

Router01 Router02

10.10.20.33/28

Radio Link Failure

NetViewer

10.10.10.2/24

10.10.20.35/28

DCN COURSE


7.4. SRA3/SRA4 RING TOPOLOGY WITH THE METRIC LIMIT OF RIP.

To resolve the metric limit of RIP is possible to use the “Border Gateway” functionality of DualQ Adapter. The “Border Gateway” functionality allows forcing, as on transmission as on reception, the reset of the metric on the interface. The reset of the metric is a function that allows exceeding the threshold of 15 steps foreseen by the RIPv1 protocol. When the Metric Override option is enabled, the system applies the metric value equal to 1 to the RIPv1 information received and transmitted through the interface. The subject option is a significant one only if the RIPv1 protocol is enabled on the interface.

Here below two examples of SRA3 ring topology using the “Border Gateway functionality of DualQ Adapter.

Figure 44


DualQDualQ

DualQ

DualQNetViewer

Management Centre

Maximum

7 radio links

Maximum

7 radio links

Maximum

7 radio links

The Border gateway is enabled: “Metric forced to 1” for exceeding the metric limit of RIPv1 protocol

The RIP routing protocol must be enabled on every interface of all equipment.

Network: X.Y.1.0/24

Network: X.Y.9.0/24

Network: X.Y.10.0/24




Network: X.Y.21.0/24 Priority Interface

Lan Cable

VBus cable

DCN COURSE


Figure 45

Analogue dissertation are valid for SRA4.


DualQDualQDualQDualQ

DualQDualQ

DualQDualQ

NetViewer

Management Centre

Maximum

7 radio links

Maximum

7 radio links

Maximum

6 radio links

The Border gateway is enabled: “Metric forced to 1”for exceeding the metric limit of RIPv1 protocol

Network: X.Y.1.0/24

Network: X.Y.9.0/24






Point to point connection



The RIP routing protocol must be enabled on every interface of all equipment.

Priority Interface

Lan Cable

VBus cable

DCN COURSE


8. IMPLEMENTATION OF SDH AND PDH NETWORK

Here below an example of DCN planning:

Figure 46

The WAN interfaces of Router01, Router02 and Router03 are configured with the OSPF routing protocol.


DCNDCN

10.10.20.1/2810.10.10.1/24

10.10.11.1/30

11.10.11.5/30

10.10.11.2/30

Router01 Router02

Ring TopologyRouter03

10.10.20.2/28

10.10.20.4/28

10.10.20.18/28 10.10.20.20/28

10.10.20.33/28

10.10.20.35/28

10.10.20.49/28

10.10.20.51/28

10.10.20.65/2810.10.20.67/28

10.10.20.81/2810.10.20.83/2810.10.20.98/28

10.10.20.100/28

10.10.20.69/28

10.10.20.115/28

10.10.20.113/28

10.10.20.129/28

10.10.20.131/28

10.10.20.147/28

10.10.20.161/28

10.10.20.163/28

10.10.20.177/28

10.10.11.6/30 10.10.21.1/28

10.10.21.2/28

10.10.21.17/28

10.10.21.19/2810.10.21.21/28

10.10.21.33/28

10.10.21.49/28

Grooming Node

Grooming Node

The Border gateway is enabled: “Metric forced to 1” for exceeding the metric limit of RIPv1 protocol

NetViewer

10.10.10.2/24

10.10.20.145/28

DCN COURSE


The Ethernet interfaces of Router02 and Router03 are configured with the RIP routing protocol in listening mode (passive interface is configured on Ethernet interface). The listening mode on Ethernet interface avoids that wasteful routing entries, coming from other network segment, are propagated to the SRA3/SRA4. The excessive number of routing entries on SRA3, SRA4 and SRALXD could bring to a standstill of management.

Static Route must be inserted on SRA3, SRA4 and SRALXD of “Grooming Node” toward NetViewer.

Equipment Network Destination

NetMask Gateway

SRA3 0.0.0.0 - 10.10.20.1

SRA4 0.0.0.0 0.0.0.0 10.10.20.1

SRALXD 0.0.0.0 0.0.0.0 10.10.21.1

Default Gateway must be inserted on NetViewer toward NE.

Main configuration of Router01:

interface Ethernet0/0

ip address 10.10.10.1 255.255.255.240

half-duplex

interface Serial1/0

ip address 10.10.11.1 255.255.255.252

interface Serial1/1

ip address 10.10.11.5 255.255.255.252

router ospf 1

log-adjacency-changes

network 10.10.11.0 0.0.0.7 area 0


DCN COURSE





ip address 10.10.21.1 255.255.255.240

half-duplex

interface Serial1/0

ip address 10.10.11.6 255.255.255.252

router ospf 1


redistribute rip subnets

network 10.10.11.0 0.0.0.3 area 0

router rip

passive-interface Serial1/0

network 10.0.0.0



ip address 10.10.20.1 255.255.255.240

half-duplex

interface Serial1/0

ip address 10.10.11.2 255.255.255.252

router ospf 1


redistribute rip subnets

network 10.10.11.0 0.0.0.3 area 0

router rip

passive-interface Serial1/0

network 10.0.0.0

DCN COURSE


9. LABORATORIES

9.1. PDH/SDH NETWORKS INTERCONNECTION

An example of practical interconnection between NetViewer 6.1 and SRAL, SRAL XD, SRA 4 and SRA 3 follows.

Figure 47

The configurations of the DCN routers follow:

Router R_3640_1

[…]


ip address 10.10.50.1 255.255.255.0

!


Fa0/1:

10.10.40.1/24

Eth0/0: 10.10.30.1/24

Serial 0/0: 10.10.11.2/24

R_3640_2

R_3725

R_3640_1

Eth0/0: 10.10.50.1/24

10.10.50.4/24

10.10.52.4/24

Serial 3/0: 10.10.11.1/24

Serial0/0: 10.10.12.1/24

10.10.50.2/2410.10.51.2/24

NetViewer

10.10.30.2/24

Serial 3/1: 10.10.12.2/24

10.10.40.2/24

10.10.40.4/24

10.10.42.20/24

10.10.42.18/24

10.10.43.2/24

Eth0/1: 10.10.10.2/24

Fa0/0: 10.10.10.1/24

10.10.41.2/24

DCN COURSE


interface Serial0/0

ip address 10.10.12.1 255.255.255.0

encapsulation ppp

!


ip address 10.10.10.2 255.255.255.0

!

router rip

network 10.0.0.0

[…]

Router R_3640_2

[…]


ip address 10.10.30.1 255.255.255.0

!

interface Serial3/0

ip address 10.10.11.1 255.255.255.0

encapsulation ppp

clockrate 128000

!

interface Serial3/1

ip address 10.10.12.2 255.255.255.0

encapsulation ppp

clockrate 128000

!

router rip

network 10.0.0.0

[…]

Router 3725

[…]

interface FastEthernet0/0

ip address 10.10.10.1 255.255.255.0

!

interface Serial0/0

ip address 10.10.11.2 255.255.255.0

encapsulation ppp

!



DCN COURSE


ip address 10.10.40.1 255.255.255.0

!

router rip

network 10.0.0.0

!

[…]


DCN COURSE


9.2. D-EXTERNAL CONNECTIONS

In this section there is an example of management of a SRAL spur and a SRAL XD spur, through the use of a D-External interface.

Figure 48

The second device of the SRAL spur is provided with a D-External card, in order to connect to the second device of the SRAL XD spur.

The RIP routing protocol must be enabled on all the interfaces of the SRAL and SRAL XD devices.

The routers R_3640_2 and R_725 are configured as explained in the previous section.

The configuration of the router R_3640_1 follows:

Router R_3640_1

[…]

interface Serial0/0

ip address 10.10.12.1 255.255.255.0


Fa0/1:

10.10.40.1/24

Eth0/0:

10.10.30.1/24

Serial 0/0: 10.10.11.2/24

R_3640_2 R_3725

R_3640_1

10.10.50.4/24 10.10.52.4/24

Serial 3/0: 10.10.11.1/24

Serial0/0: 10.10.12.1/24

10.10.50.2/2410.10.51.2/24

NetViewer

10.10.30.2/24

10.10.40.2/24

10.10.40.4/24

10.10.41.2/24

10.10.42.20/24

10.10.42.18/24

10.10.43.2/24

Eth0/1: 10.10.10.2/24

Fa0/0: 10.10.10.1/24

D-Ext

Serial 3/1: 10.10.12.2/24

DCN COURSE


encapsulation ppp

!


ip address 10.10.10.2 255.255.255.0

!

router rip

network 10.0.0.0

[…]


DCN COURSE


9.3. D-EMBEDDED CHANNELS

In this section there is an example of management of a SRAL spur and a SRAL XD spur, through the use of the D-embedded and D-External channels.

The D-Embedded channel is configured in the SRAL XD to use the PPP protocol for the management information.

Figure 49

The slots #1 of the first E1 tributary of the SRAL XD gateway (10.10.50.4) is configured for the transport of the management information. This tributary, however, must be configured to be transmitted over the radio frame.

The second device of the SRAL spur is provided with a D-External card, in order to connect to the second device of the SRAL XD spur.

The RIP routing protocol must be enabled on all the interfaces of the SRAL and SRAL XD devices.


Eth0/0: 10.10.30.1/24

Serial 0/0: 10.10.11.2/24

Cisco 3640_2 Cisco 3725

Cisco 3640_1

10.10.50.4/24 10.10.52.4/24

Serial 3/0: 10.10.11.1/24

Serial0/0: 10.10.12.1/24

10.10.50.2/2410.10.51.2/24

NetViewer

10.10.30.2/24

10.10.40.4/24

10.10.41.2/24

10.10.42.20/24

10.10.42.18/24

Eth0/1: 10.10.10.2/24

Fa0/0: 10.10.10.1/24

D-Ext

Serial 3/1: 10.10.12.2/24

E1

10.10.40.4/24

E1 0/4: 10.10.50.101/24

10.10.43.2/24

DCN COURSE


The configuration of the Cisco 3725 router follows:

Router 3725

[…]

controller E1 0/4

channel-group 0 timeslots 1 speed 64

!


ip address 10.10.10.1 255.255.255.0

!

interface Serial0/0

ip address 10.10.11.2 255.255.255.0

encapsulation ppp

!

interface Serial0/4:0

ip address 10.10.50.101 255.255.255.0

encapsulation ppp

!

router rip

network 10.0.0.0

[…]


DCN COURSE


9.4. INTERWORKING BETWEEN CISCO ROUTERS AND RAD FCD/IP

In the following example an E1 link is available for the communication between a network of SRAL and SRA 3 and a Cisco 3725 router.

For interconnecting these two networks a pair of RAD FCD/IP devices is used in bridging mode.

Figure 50

The routers R_3640_1 and R_3640_2 are configured as explained in the previous section.

The configurations of the Cisco 3725 router and the RAD FCD-IP follow:

Router 3725

[…]


ip address 10.10.10.1 255.255.255.0

!

interface Serial0/0


Eth0/0: 10.10.30.1/24

Serial 0/0: 10.10.11.2/24

Cisco 3640_2Cisco 3725

Cisco 3640_1

10.10.50.4/24 10.10.52.4/24

Serial 3/0: 10.10.11.1/24

Serial0/0: 10.10.12.1/24

10.10.50.2/2410.10.51.2/24

NetViewer

10.10.30.2/24

10.10.40.4/24

10.10.41.2/24

10.10.42.20/24

10.10.42.18/24

Eth0/1: 10.10.10.2/24

Fa0/0: 10.10.10.1/24

D-Ext

Serial 3/1: 10.10.12.2/24

10.10.40.4/24

Fa0/1: 10.10.40.1/24

Bridging Mode

10.10.43.2/24

DCN COURSE


ip address 10.10.11.2 255.255.255.0

encapsulation ppp

!


ip address 10.10.40.1 255.255.255.0

!

router rip

network 10.0.0.0

!

[…]

RAD FCD-IP

ROUTING/BRIDGING MODE: LINK 1 ( Device name - FCD-IP )

-----------------------------

1. Link type - BRIDGE

2. Link protocol - PPP

3. PPP settings

*******************************************************

TYPE: LINK 1 ( Device name - FCD-IP )

------------

1. Bridge: [Enabled ]

2. IP Router: [Disabled]

3. IPX Router: [Disabled]

*******************************************************

ROUTING/BRIDGING MODE: LINK 1 ( Device name - FCD-IP )

-----------------------------

1. Link type - BRIDGE

2. Link protocol - PPP

3. PPP settings

*******************************************************

PROTOCOL: LINK 1 ( Device name - FCD-IP )


DCN COURSE


----------------

1. PPP

2. NATIVE

*******************************************************

PPP SETTINGS: LINK 1 ( Device name - FCD-IP )

--------------------

1. Header and Control Field Compression - [NO ]

2. Protocol Field Compression - [NO ]

3. IP Compression (V.Jacobsen - RFC 1144) - [YES]

*******************************************************

IP INTERFACE ADDRESS ( Device name - FCD-IP )

--------------------

*******************************************************

RIP MODE SETUP ( Device name - FCD-IP )

----------------

1. LINK 1 RIP mode: [NO RIP]

2. LAN 1 RIP mode: [NO RIP]

*******************************************************

CONFIGURATION SETUP: LINK 1 ( Device name - FCD-IP )

----------------------------

CURRENT NEW

------- ---

1. Status Enabled [Enabled ]

2. Type Synchronous Synchronous

3. Connection type Answer & Originate [Answer&Originate]

4. Connection timeout (sec) 30 30

5. Control signals mode Ignore [Ignore]

*******************************************************


DCN COURSE


E1 SETUP: LINK 1 ( Device name - FCD-IP )

----------------

1. Clock master : [Link 1]

2. Multiplier : [64 kbps]

3. Time slots mapping

4. Loopback

5. E1 parameters

6. Sub link E1 parameters

7. Alarms filter

8. Advanced setup

*******************************************************

E1 TIME SLOTS MAPPING: LINK 1 ( Device name - FCD-IP )

-----------------------------

TS1 [DATA LINK1] TS17 [DATA LINK1]















TS16 [NC ]

*******************************************************


DCN COURSE


E1 PARAMETERS: LINK 1 ( Device name - FCD-IP )

---------------------

1. Frame type : [G732S]

2. CRC-4 : [ON]

3. Sync : [FAST]

4. Idle code (hex) : 7C

5. Rx gain : [30 dB]

6. Remote Alarm Indication : [ON]

*******************************************************

LAN SETTINGS ( Device name - FCD-IP )

1. LAN Full Duplex: [Disable]


DCN COURSE


9.5. IP/OSI TUNNELLING

In the following example a DCC-R channel is available for the management of a remote site with an SPS-E device.

This DCC-R has been configured between a pair of two SRT1C.

For the management of the remote SPS-E through IP routing, an IP/OSI tunnel has been configured on two Dual Q-Adapters,:

The DQA attached to the LAN of NetViewer

The DQA attached to the SPS-E

Moreover, the RIPv1 protocol must be enabled on the IP/OSI tunnel in order to forward the IP routing information between the router R_3725 and the SPS-E network.

Figure 50

The NSAP addresses used in this scheme are:

NSAP_1: 47.00991538001001AAAA000000.0090AE00C65D.01 NSAP_2: 47.00991538001001AAAA000000.0800060C1201.01 NSAP_3: 47.00991538001001AAAA000000.0800060C1301.01 NSAP_4: 47.00991538001001AAAA000000.08003E010203.01


NetViewer

10.10.40.101/24

10.10.40.4/24 NSAP_1

NSAP_2

NSAP_3

10.10.69.10/24 NSAP_4

10.10.69.20/24

OSI

DCN COURSE


IP/OSI Tunnel Configuration on Dual Q-Adapters

The configuration of the IP and OSI addresses of the local Dual Q-Adapter

Figure 51

The configuration of the IP and OSI addresses of the remote Dual Q-Adapter is described in the picture below:

Figure 52


DCN COURSE


Finally, the configuration of the IP/OSI tunnel is done, as described in the next two pictures (the first one refers to the configuration of the local Dual Q-Adapter, the second picture to the remote one):

Figure 53a


DCN COURSE


Figure 53b

- End of document -
