Home > Documents > DCN Course

DCN Course

Date post: 19-Feb-2015
Category:
Author: loihut
View: 70 times
Download: 2 times
Share this document with a friend
Embed Size (px)
of 102 /102
s DCN Course Siemens Radio IP Equipment Issue 2 IMC 6032 AEDG
Transcript

s

DCN Course

Siemens Radio IP EquipmentIssue 2

IMC 6032 AEDG

DCN COURSESiemens Radio IP Equipment

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

Issued by Technical Assistance Department S.S. 11 Padana Superiore, km 158 I-20060 Cassina de Pecchi MI Technical modifications are possible. Technical specifications and features are binding only insofar as they are specifically and expressly agreed upon in a written contract. Authors: Authorized: A. Auditore, A. Costa, P. Cuccaro, M.Grandi Andrea Baldini

Documento IMC 6032 AEDG Issue 2, April 2005

- 2/76 -

DCN COURSESiemens Radio IP Equipment

INDICEDCN COURSE.......................................................................................................................................1 SIEMENS RADIO IP EQUIPMENT ISSUE 2.........................................................................................1 IMC 6032 AEDG.....................................................................................................................................11. OVERVIEW...........................................................................................................................................................................................................................6 2. DUALQ-ADAPTER MANAGEMENT DESCRIPTION............................................................................................................................................................7 3. SRAL MANAGEMENT DESCRIPTION...............................................................................................................................................................................10 4. SRAL XD MANAGEMENT DESCRIPTION.........................................................................................................................................................................20 5. SRA3/SRA4 MANAGEMENT DESCRIPTION.....................................................................................................................................................................31 6. SKYWEB MANAGEMENT DESCRIPTION.........................................................................................................................................................................35 7. BUILDING A DCN WITH MW RADIOS...............................................................................................................................................................................38 7.1. INTER-WORKING SRALXD & SRAL...............................................................................................................................................................................38 7.1.1. OVERVIEW...................................................................................................................................................................................................................38 7.1.2. STATION WITH A ROUTER/DUALQ-ADAPTER..........................................................................................................................................................39 7.1.1. REMOTE STATION WITHOUT DUALQ-ADAPTER......................................................................................................................................................42 7.1.1.1. USING THE D-EXTERNAL INTERFACE:..................................................................................................................................................................42 7.1.1.2. USING THE F-INTERFACE:.......................................................................................................................................................................................43 7.1.1.3. USING THE V-BUS INTERFACE:..............................................................................................................................................................................44 7.1.2. GENERAL NETWORK SCENARIO...............................................................................................................................................................................45 7.1.3. EXAMPLE OF NETWORK SCENARIOS.......................................................................................................................................................................47 7.1.3.1. USING THE D-EXTERNAL INTERFACE:..................................................................................................................................................................47 7.1.3.2. USING THE ETHERNET INTERFACE (THROUGH DUAL Q-ADAPTER):................................................................................................................48 7.1.3.3. USING THE F INTERFACE:.......................................................................................................................................................................................50 7.1.3.4. USING THE V-BUS INTERFACE (FOR SRAL XD SVR3.5):......................................................................................................................................51 7.2. INTERWORKING SRA3 & SRA4.....................................................................................................................................................................................52 7.2.1. OVERVIEW...................................................................................................................................................................................................................52 7.2.2. EXAMPLES OF NETWORK SCENARIOS....................................................................................................................................................................53 7.3. RING TOPOLOGY............................................................................................................................................................................................................55 7.4. SRA3/SRA4 RING TOPOLOGY WITH THE METRIC LIMIT OF RIP...............................................................................................................................56 8. IMPLEMENTATION OF SDH AND PDH NETWORK..........................................................................................................................................................58 9. LABORATORIES.................................................................................................................................................................................................................61 9.1. PDH/SDH NETWORKS INTERCONNECTION................................................................................................................................................................61 9.2. D-EXTERNAL CONNECTIONS........................................................................................................................................................................................64 9.3. D-EMBEDDED CHANNELS.............................................................................................................................................................................................66 9.4. INTERWORKING BETWEEN CISCO ROUTERS AND RAD FCD/IP..............................................................................................................................68 9.5. IP/OSI TUNNELLING.......................................................................................................................................................................................................73

Documento IMC 6032 AEDG Issue 2, April 2005

- 3/76 -

DCN COURSESiemens Radio IP Equipment

RevisionEdition01 02

DataJuly 2004 April 2005

AuthorAgostino Auditore Antonio Costa Pietro Cuccaro Mauro Grandi

CapitolsAll All

CauseNew Document New Document

MutationNA New Course

Acronym ATM BTS CLNP DCN DQA IP LAN LCT MS NB NE NMS OSI PDH PMP PS PVC RBE SDH SRAL TMN VCI VPI Asynchronous Transfer Mode Base Terminal Station ConnectionLess Network Protocol Data Communication Network Dual Q Adapter Internet Protocol Local Area Network Local Craft Terminal Master Station Node B Network Element Network Management System Open Standard Interconnection Plesyochronous Digital Hierarchy Point-to-MultiPoint Peripheral Station Permanent Virtual Circuit Routed Bridge Encapsulation Synchronous Digital Hierarchy System Radio Access Low Capacity Telecommunication Management Network Virtual Channel Identifier Virtual Path Identifier

Documento IMC 6032 AEDG Issue 2, April 2005

- 4/76 -

DCN COURSESiemens Radio IP Equipment

WLL

Wireless Local Loop

Documento IMC 6032 AEDG Issue 2, April 2005

- 5/76 -

DCN COURSESiemens Radio IP Equipment

1.

OVERVIEWThis 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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 6/76 -

DCN COURSESiemens Radio IP Equipment

2.

DUALQ-ADAPTER MANAGEMENT DESCRIPTIONThe 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 o Ethernet 10base2: NetViewer side V-bus: SRAL side.

NetViewerRJ45 Cable

HUB RJ45/BNC

BNC Cable

DualQVBUS Cable

SRAL

SRAL

Documento IMC 6032 AEDG Issue 2, April 2005

- 7/76 -

DCN COURSESiemens Radio IP EquipmentFigure 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 subnetwork, without distinguishing if the NEs belong or not to the same IP subnetwork of NetViewer. In this mode, the DualQ-Adapter uses the Ethernet 10base2 interface.

NetViewer

HUB RJ45/BNC

SRALVBUS Cable

SRAL

IP

DualQIPBNC Cable

OSI

DualQ

OSI

IP

OSIBNC Cable

SRA3

SRA3

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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 8/76 -

DCN COURSESiemens Radio IP Equipment

SRALDualQ-Ad.

SRAL

E1 Time Slot 1

SRALDualQ-Ad. E1 Time Slot 2

SRAL

Eth. TCP/IPRouter

E1 Cross-Connector

E1 Time Slot 3

E1 Time Slots 1,2,3,4

SRALE1 Time Slot 4 DualQ-Ad.

SRAL

SRALDualQ-Ad.

SRAL

Figure 3

Documento IMC 6032 AEDG Issue 2, April 2005

- 9/76 -

DCN COURSESiemens Radio IP Equipment

3.

SRAL MANAGEMENT DESCRIPTIONThe 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 DExternal 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

Documento IMC 6032 AEDG Issue 2, April 2005

- 10/76 -

DCN COURSESiemens Radio IP Equipment

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

User Channel To Management System of other Vendors Router 64k V11 cable 64k V11 cable

SRAL

SRALRouter

To NEs of other Vendors

Figure 4

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 11/76 -

DCN COURSESiemens Radio IP Equipment

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).

Router Router

DCNRJ 45 Cable Converter HUB RJ45/BNC

NetViewer Management CentreBNC Cable

SRALDualQ-Ad.

SRAL

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 crossconnector; 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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 12/76 -

DCN COURSESiemens Radio IP Equipment

SRALDualQ-Ad.

SRAL

E1

SRALDualQ-Ad. E1

SRAL

RJ 45 Cable E1 Router

E1 Cross-ConnectorE1

NetViewer Management CentreE1

SRALDualQ-Ad.

SRAL

SRALDualQ-Ad.

SRAL

Figure 6

Documento IMC 6032 AEDG Issue 2, April 2005

- 13/76 -

DCN COURSESiemens Radio IP Equipment

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.

RJ 45 Cable

To NetViewer Router

Converter HUB RJ45/BNC

SRALDualQ-Ad.

SRAL

BNC Cable

V-Bus Daisy-Chain

SRAL

SRAL

SRALFigure 7

SRAL

Documento IMC 6032 AEDG Issue 2, April 2005

- 14/76 -

DCN COURSESiemens Radio IP Equipment

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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 15/76 -

DCN COURSESiemens Radio IP Equipment

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, its 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, its 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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 16/76 -

DCN COURSESiemens Radio IP Equipment

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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 17/76 -

DCN COURSESiemens Radio IP Equipment

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), its configured the IP Address, NetMask, Rip Enabled and Cisco KeepAlive to 60 sec. More in details: IP address: Its 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: Its possible to enable/disable the propagation/search of RIPv1 messages with D embedded channel standard; options are:

Documento IMC 6032 AEDG Issue 2, April 2005

- 18/76 -

DCN COURSESiemens Radio IP Equipment

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 reset Enabled-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: Its the time intervals within KeepAlive packets are transmitted (seconds between one KeepAlive packet and another). The KeepAlive value settled on DualQAdapter 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 its not available the signaling of connection status (alarm of D embedded channel disconnected appears).

Documento IMC 6032 AEDG Issue 2, April 2005

- 19/76 -

DCN COURSESiemens Radio IP Equipment

4.

SRAL XD MANAGEMENT DESCRIPTIONThe 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: o F interface (RS-232 serial interface), used for 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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 20/76 -

DCN COURSESiemens Radio IP EquipmentRJ 45 Cable

To NetViewer Router

Converter HUB RJ45/BNC

SRALDualQ-Ad.

SRAL

BNC Cable F-Cable

SRALXDFigure 11

SRALXD

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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 21/76 -

DCN COURSESiemens Radio IP Equipment

RJ45 Straight Through Cable

R Channel

To NetViewer Router

HUB RJ45

SRALXDQ Int RJ45 Cross-Over Cable

SRALXDR Channel

RJ45 Straight Through Cable

SRALXDV Int

SRALXD

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).

RJ 45 Cable

R Channel

To NetViewer Router

HUB RJ45

SRALXD

SRALXD

RJ45 Cable

Figure 13

Documento IMC 6032 AEDG Issue 2, April 2005

- 22/76 -

DCN COURSESiemens Radio IP Equipment

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.

R1 User Channel 1 R1+User Ch. 1 User Ch. 1 User Ch. 2 D1 D2 CONTROLLER HUB Q Tributaries (Embedded D1/D2 channel)Figure 14

R2 R2+User Ch. 2

User Channel 2

D-Ext /User Int. 1 D-Ext/User Int. 2.

F Int. V

V-BUS Int. (for XD Plugin SVR 3. 5)

Documento IMC 6032 AEDG Issue 2, April 2005

- 23/76 -

DCN COURSESiemens Radio IP Equipment

R User Ch User Ch. D-Ext/User Int. 1 D-Ext /User Int. 2 Tributaries Int. (Embedded D1/D2 channel)Figure 15

Radio Redundancy

D1 D2 CONTROLLER HUB Q V-BUS Int. (for XD Plugin SVR 3. 5) F Int. V

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 D2 interface: it can be connected to the external D2 interface or to the embedded D2 channel System Type (1+0), (1+1) H/S and (1+1) FD: D1 interface: it can be connected to the external D1 interface or to the embedded D1 channel 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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 24/76 -

DCN COURSESiemens Radio IP Equipment

o

Access NxT1: System Type 2x(1+0) and A/D-Rep: D1 interface: it can be connected to the external D1 interface D2 interface: it can be connected to the external D2 interface System Type (1+0), (1+1) H/S and (1+1) FD: D1 interface: it can be connected to the external D1 interface

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.

SRALXD

SRALXD

E1

SRALXDRJ 45 Cable Router E1 E1 Cross-Connector E1 E1

SRALXD

NetViewer Management CentreE1

SRALXD

SRALXD

SRALXDFigure 16

SRALXD

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 25/76 -

DCN COURSESiemens Radio IP Equipment

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.

User Channel To Management System of other Vendors Router 64k V11 cable 64k V11 cable

SRALXD

SRALXDRouter

To NEs of other Vendors

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 o System Type 2x(1+0) and A/D-Rep: two User Channel can be configured (one for each radio frame) System Type (1+0), (1+1) H/S and (1+1) FD: one User Channel is available (on the configured radio frame)

Documento IMC 6032 AEDG Issue 2, April 2005

- 26/76 -

DCN COURSESiemens Radio IP Equipment

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. 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.

RJ45 Straight Through Cable

R Channel

To NetViewer Router

HUB RJ45

SRALXD

SRALXDR Channel

RJ45 Straight Through Cable

D- External Cable (V11)

SRALD-Ext

SRAL

Figure 18

Documento IMC 6032 AEDG Issue 2, April 2005

- 27/76 -

DCN COURSESiemens Radio IP Equipment

SRAL XD Network Configuration

Figure 19

Several network parameters can be configured for each interface: o o Network Protocol: It is the network protocol of the interface. Possible options are: None (Interface disabled) 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 information (i.e. performing an automatic summarization); this function can be enabled only if theDocumento IMC 6032 AEDG Issue 2, April 2005

- 28/76 -

DCN COURSESiemens Radio IP Equipment

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 29/76 -

DCN COURSESiemens Radio IP Equipment

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 metricoverride 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)

Documento IMC 6032 AEDG Issue 2, April 2005

- 30/76 -

DCN COURSESiemens Radio IP Equipment

5.

SRA3/SRA4 MANAGEMENT DESCRIPTIONThe 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.R Channel

To NetViewer Router

HUB RJ45

SRA4

SRA4

RJ45 Cable

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)

Documento IMC 6032 AEDG Issue 2, April 2005

- 31/76 -

DCN COURSESiemens Radio IP Equipment

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

HUB RJ45/BNC

NetViewer

BNC Cable

SRA3RJ 45 Cable

SRA3

SRA4Figure 22

SRA4

Documento IMC 6032 AEDG Issue 2, April 2005

- 32/76 -

DCN COURSESiemens Radio IP Equipment

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 Static Routes take priority over Dynamic Route. All subnet masks inside the same network must be chosen to be equal. The IP addresses of the SRA3 must be only even.

Here below an example of SRA3 DCN planning.

HUB RJ45/BNC 10.10.10.1/24

NetViewer

10.10.10.2/24

SRA3BNC Cable

SRA310.10.20.2/24

10.10.10.4/24

SRA3

SRA310.10.21.4/24

Figure 23

Documento IMC 6032 AEDG Issue 2, April 2005

- 33/76 -

DCN COURSESiemens Radio IP Equipment

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. All subnet masks inside the same network must be chosen to be equal. 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. The Static Routes take priority over Dynamic Route.

HUB RJ45/BNC 10.10.10.1/24

NetViewer

10.10.10.2/24

SRA4RJ45 Cable

SRA410.10.20.2/24

10.10.10.4/24

SRA4Figure 24

SRA410.10.21.4/24

Documento IMC 6032 AEDG Issue 2, April 2005

- 34/76 -

DCN COURSESiemens Radio IP Equipment

6.

SKYWEB MANAGEMENT DESCRIPTIONSkyWeb 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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 35/76 -

DCN COURSESiemens Radio IP Equipment

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.

PS

MS

PS

Router Router RJ45 Straight Through Cable

DCN

RJ45 Straight Through Cable

NetViewer Management Centre 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

Documento IMC 6032 AEDG Issue 2, April 2005

- 36/76 -

DCN COURSESiemens Radio IP Equipment

In-band management: NetViewer is connected to the Master Station with a dedicated ATM connection through a selected network interface. A PVC channel ( 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.

PS

MSSwitch ATMr

PS

Switch ATMr

ATM Network RJ45 StraightThrough Cable

Payload and Management

ATM Interface Fiber Optical

Router

NetViewer Management Centre

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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 37/76 -

DCN COURSESiemens Radio IP Equipment

7.

BUILDING A DCN WITH MW RADIOS

7.1.

INTER-WORKING SRALXD & SRAL

7.1.1. OVERVIEWAs 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 DExternal 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: The connection speed of the different interfaces is reported here below: 1. 2. 3. 4. 5. 6. SRAL F Interface: 19,2 Kbit/s SRALXD F Interface: 38,4 Kbit/s D-External Interface: 64 Kbit/s VBUS Interface: 128 Kbit/s (only for SRAL XD Plugin SVR 3.5 and onwards) SRAL Ethernet Interface: 10 Mbit/s 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/DualQAdapter 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).

Documento IMC 6032 AEDG Issue 2, April 2005

- 38/76 -

DCN COURSESiemens Radio IP Equipment

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

Router RJ 45 Cable RJ 45 Cable

Station 2

SRALXDMultiPort HUB / Converter RJ45/BNC

SRALXD

SRALStation 1BNC Cable DualQ-Ad.

SRALStation 3Figure 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

Documento IMC 6032 AEDG Issue 2, April 2005

- 39/76 -

DCN COURSESiemens Radio IP Equipment

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.

Router

RJ 45 Cable

SRALXD 3.5

SRALXD 3.5 Station 2

V-BUS Cable

SRALStation 1Figure 29

SRALStation 3

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.

SRALXD 3.5V-BUS Cable

SRALXD 3.5 Station 2

Converter RJ45/BNC Router RJ 45 Cable BNC Cable

SRALDualQ-Ad.

SRALStation 3

Station 1

Figure 30

Documento IMC 6032 AEDG Issue 2, April 2005

- 40/76 -

DCN COURSESiemens Radio IP Equipment

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. The IP Addresses of NEs connected through radio link must belong to different subnetworks

Documento IMC 6032 AEDG Issue 2, April 2005

- 41/76 -

DCN COURSESiemens Radio IP Equipment

7.1.1. REMOTE STATION WITHOUT DUALQ-ADAPTER

7.1.1.1.

USING THE D-EXTERNAL INTERFACE:Station 1

SRALXD

SRALXD

To Supervision System

V11 cable

SRALD-External

SRALStation 3Figure 31

Station 2

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 subnetworks.

Documento IMC 6032 AEDG Issue 2, April 2005

- 42/76 -

DCN COURSESiemens Radio IP Equipment

7.1.1.2.

USING THE F-INTERFACE:Station 1

SRALXD

SRALXD

To Supervision System

F cable

SRALStation 2

SRALStation 3Figure 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).

Documento IMC 6032 AEDG Issue 2, April 2005

- 43/76 -

DCN COURSESiemens Radio IP Equipment

7.1.1.3.

USING THE V-BUS INTERFACE:Station 1

SRALXD 3.5

SRALXD 3.5

To Supervision System

V-BUS cable

SRALStation 2

SRALStation 3Figure 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.

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 44/76 -

DCN COURSESiemens Radio IP Equipment

7.1.2. GENERAL NETWORK SCENARIOIn a general network topology, its 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).

Router Router

Station 2

DCNRJ 45 Cable

RJ 45 Cable

SRALXD

SRALXD

Converter HUB RJ45/BNC

NetViewer Management CentreBNC Cable

Station 3

SRALDualQ-Ad.

SRAL

Station 4RJ 45 Cable

Station 5

SRALXD

SRALXDV11 cable

SRALD-External

SRALStation 7

Station 1 Station 6RJ 45 Cable

SRALXD

SRALXDF cable

SRAL

SRAL

Station 8

Station 9

SRAL XD 3.5

SRAL XD 3.5V-BUS cable

SRAL

SRAL

Figure 34

Documento IMC 6032 AEDG Issue 2, April 2005

- 45/76 -

DCN COURSESiemens Radio IP Equipment

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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 46/76 -

DCN COURSESiemens Radio IP Equipment

7.1.3. EXAMPLE OF NETWORK SCENARIOSHere below some practical examples using IP addresses.

7.1.3.1.

USING THE D-EXTERNAL INTERFACE:Radio V-bus20.20.20.3/24 20.20.90.1/24

D-External Cable LAN

20.20.20.1/24

20.20.50.1/24

20.20.30.1/24

20.20.10.1/24 20.20.10.3/24 Figure 35

NetViewer Server

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 20.20.20.0 20.20.30.0 20.20.50.0 20.20.90.0

Gateway 20.20.10.1 20.20.10.1 20.20.10.1 20.20.10.1

Documento IMC 6032 AEDG Issue 2, April 2005

- 47/76 -

DCN COURSESiemens Radio IP Equipment

7.1.3.2. USING THE ETHERNET INTERFACE (THROUGH DUAL QADAPTER):

Radio20.20.20.5/24 20.20.90.1/24

V-bus LAN

20.20.20.3/24 20.20.20.1/24 20.20.30.3/24

20.20.50.1/24

20.20.30.1/24

20.20.10.1/24 20.20.10.3/24 Figure 36

NetViewer Server

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:

Network Destination 20.20.20.0 20.20.30.0 20.20.50.0

Gateway 20.20.10.1 20.20.10.1 20.20.10.1

Documento IMC 6032 AEDG Issue 2, April 2005

- 48/76 -

DCN COURSESiemens Radio IP Equipment

20.20.90.0

20.20.10.1

Documento IMC 6032 AEDG Issue 2, April 2005

- 49/76 -

DCN COURSESiemens Radio IP Equipment

7.1.3.3.

USING THE F INTERFACE:Radio V-bus20.20.20.3/24 20.20.90.1/24

F Cable LAN

20.20.20.1/24

20.20.50.1/24

20.20.20.2/24

20.20.10.1/24 20.20.10.3/24 Figure 37

NetViewer Server

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 subnetworks. 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. 6. Default gateway or static routes are necessary on NetViewer server in order to manage the NEs:

Network Destination 20.20.20.0 20.20.50.0 20.20.90.0

Gateway 20.20.10.1 20.20.10.1 20.20.10.1

Documento IMC 6032 AEDG Issue 2, April 2005

- 50/76 -

DCN COURSESiemens Radio IP Equipment

7.1.3.4.

USING THE V-BUS INTERFACE (FOR SRAL XD SVR3.5):Radio V-bus20.20.20.3/24 20.20.90.1/24

F Cable LAN

20.20.20.1/24

20.20.50.1/24

20.20.20.2/24

20.20.10.1/24 20.20.10.3/24 Figure 38

NetViewer Server

1. The IP Addresses of NEs connected through radio link must belong to different subnetworks. 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. 4. Default gateway or static routes are necessary on NetViewer server in order to manage the NEs:

Network Destination 20.20.20.0 20.20.50.0 20.20.90.0

Gateway 20.20.10.1 20.20.10.1 20.20.10.1

Documento IMC 6032 AEDG Issue 2, April 2005

- 51/76 -

DCN COURSESiemens Radio IP Equipment

7.2.

INTERWORKING SRA3 & SRA4

7.2.1. OVERVIEWThe interfaces used to connect the SRAL4 to the SRA3 is the Ethernet. The connection speed of the different interfaces is reported here below: 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.

HUB RJ45/BNC

HUB RJ45/BNC

NetViewer

BNC Cable

SRA3RJ 45 Cable

SRA3

SRA4

SRA4

SRA4

SRA4

SRA4

SRA4

Station 1HUB RJ45

Station 2

Station 3

Figure 39

Documento IMC 6032 AEDG Issue 2, April 2005

- 52/76 -

DCN COURSESiemens Radio IP Equipment

7.2.2. EXAMPLES OF NETWORK SCENARIOSThe DCN performs the OSPF routing protocol

10.10.11.1/30 10.10.11.2/30

NetViewerRouter01 Router02

10.10.20.2/28

10.10.20.18/28

10.10.20.20/28

10.10.20.33/28

DCN10.10.10.2/24 10.10.10.1/24 10.10.20.1/28 Router03 10.10.20.49/28 10.10.20.51/28

10.10.20.4/28

10.10.20.65/28

Other equipment

Grooming Node

10.10.20.54/28

10.10.20.82/28

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 SRA3 SRA4 Network Destination 0.0.0.0 0.0.0.0 NetMask 0.0.0.0 Gateway 10.10.20.1 10.10.20.1

Default Gateway must be inserted on NetViewer toward NE.

Documento IMC 6032 AEDG Issue 2, April 2005

- 53/76 -

DCN COURSESiemens Radio IP Equipment

The DCN is configured in bridged mode:

NetViewerRouter01 Router02

10.10.20.8/28

10.10.20.18/28

10.10.20.19/28

10.10.20.33/28

DCN

10.10.20.2/28 Router03 10.10.20.49/28 10.10.20.51/28

10.10.20.5/28

10.10.20.65/28

Other equipment

Grooming Station

10.10.20.54/28

10.10.20.82/28

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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 54/76 -

DCN COURSESiemens Radio IP Equipment

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:

10.10.11.1/30 10.10.11.2/30

10.10.20.2/28

10.10.20.18/28

10.10.20.20/28 10.10.20.33/28

NetViewerRouter01 Router02

DCN10.10.10.2/24 10.10.10.1/24

10.10.20.1/28

Ring Topology

10.10.20.4/28

10.10.20.49/28

10.10.20.51/28 10.10.20.35/28

Figure 42

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

Radio Link Failure

10.10.11.1/30 10.10.11.2/30

10.10.20.2/28

10.10.20.20/28

10.10.20.33/28

NetViewerRouter01 Router02

10.10.20.18/28

DCN10.10.10.2/24 10.10.10.1/24

10.10.20.1/28

10.10.20.4/28

10.10.20.49/28

10.10.20.51/28

10.10.20.35/28

Figure 43

Documento IMC 6032 AEDG Issue 2, April 2005

- 55/76 -

DCN COURSESiemens Radio IP Equipment

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.Network: X.Y.10.0/24 DualQ Network: X.Y.11.0/24

Network: X.Y.9.0/24Maximum 7 radio links

DualQ

Maximum

The Border gateway is enabled: Metric forced to 1 for exceeding the metric limit of RIPv1 protocol Network: X.Y.1.0/24 DualQNetViewer Management Centre

7 radio links

Network: X.Y.19.0/24 DualQ Network: X.Y.20.0/24

Maximum 7 radio links

Network: X.Y.21.0/24

Priority Interface Lan Cable

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

VBus cable

Figure 44

Documento IMC 6032 AEDG Issue 2, April 2005

- 56/76 -

DCN COURSESiemens Radio IP Equipment

Network: X.Y.10.0/24 Network: X.Y.9.0/24

DualQ

DualQNetwork: X.Y.11.0/24

Maximum 7 radio links MaximumNetViewer Management Centre

Network: X.Y.1.0/24 The Border gateway is enabled: Metric forced to 1 for exceeding the metric limit of RIPv1 protocol

7 radio links

Network: X.Y.19.0/24

DualQ DualQPoint to point connection

Network: X.Y.20.0/24

Maximum 6 radio links Network: X.Y.21.0/24

Network: X.Y.29.0/24

Network: X.Y.28.0/24Priority Interface

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

Lan Cable VBus cable

Figure 45

Analogue dissertation are valid for SRA4.

Documento IMC 6032 AEDG Issue 2, April 2005

- 57/76 -

DCN COURSESiemens Radio IP Equipment

8.

IMPLEMENTATION OF SDH AND PDH NETWORKHere below an example of DCN planning:

10.10.11.1/30 11.10.11.5/30 10.10.11.2/30 Grooming Node 10.10.20.33/28

NetViewerRouter01 Router02

10.10.20.2/28

10.10.20.18/28

10.10.20.20/28

DCN10.10.10.2/24 10.10.10.1/24 Router03 10.10.11.6/30

10.10.20.1/28

10.10.20.35/28

10.10.21.1/28 Grooming Node

10.10.20.4/28

Ring Topology10.10.20.49/28

10.10.21.2/28 10.10.20.100/28

10.10.20.51/28

10.10.21.17/28

10.10.20.67/28

10.10.20.65/28

10.10.20.98/28 10.10.21.33/28 10.10.21.19/28

10.10.20.83/28

10.10.20.81/28

10.10.20.69/28 10.10.20.115/28

10.10.21.21/28 The Border gateway is enabled: Metric forced to 1 for exceeding the metric limit of RIPv1 protocol

10.10.20.113/28

10.10.21.49/28

10.10.20.129/28

10.10.20.131/28

10.10.20.145/28 10.10.20.163/28 10.10.20.147/28

10.10.20.177/28

10.10.20.161/28

Figure 46

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 58/76 -

DCN COURSESiemens Radio IP Equipment

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 SRA3 SRA4 SRALXD Network Destination 0.0.0.0 0.0.0.0 0.0.0.0 NetMask 0.0.0.0 0.0.0.0 Gateway 10.10.20.1 10.10.20.1 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

Documento IMC 6032 AEDG Issue 2, April 2005

- 59/76 -

DCN COURSESiemens Radio IP Equipment

Main configuration of Router02:

interface Ethernet0/0 ip address 10.10.20.1 255.255.255.240 half-duplex interface Serial1/0 ip address 10.10.11.2 router ospf 1 log-adjacency-changes redistribute rip subnets network 10.10.11.0 router rip passive-interface Serial1/0 network 10.0.0.0 0.0.0.3 area 0 255.255.255.252

Main configuration of Router03:interface Ethernet0/0 ip address 10.10.21.1 255.255.255.240 half-duplex interface Serial1/0 ip address 10.10.11.6 router ospf 1 log-adjacency-changes redistribute rip subnets network 10.10.11.0 router rip passive-interface Serial1/0 network 10.0.0.0 0.0.0.3 area 0 255.255.255.252

Documento IMC 6032 AEDG Issue 2, April 2005

- 60/76 -

DCN COURSESiemens Radio IP Equipment

9. 9.1.

LABORATORIES PDH/SDH NETWORKS INTERCONNECTIONAn example of practical interconnection between NetViewer 6.1 and SRAL, SRAL XD, SRA 4 and SRA 3 follows.

Serial 3/0: 10.10.11.1/24 NetViewer

Serial 0/0: 10.10.11.2/24 10.10.40.2/24 10.10.41.2/24

Fa0/1: R_3640_2 Eth0/0: 10.10.30.1/24 10.10.40.1/24 R_3725 Fa0/0: 10.10.10.1/24 Serial 3/1: 10.10.12.2/24 R_3640_1 Serial0/0: 10.10.12.1/24 Eth0/0: 10.10.50.1/24

10.10.30.2/24

10.10.40.4/24 Eth0/1: 10.10.10.2/24 10.10.42.20/24

10.10.42.18/24

10.10.50.2/24 10.10.51.2/24 10.10.50.4/24 10.10.43.2/24

10.10.52.4/24

Figure 47

The configurations of the DCN routers follow: Router R_3640_1[] interface Ethernet0/0 ip address 10.10.50.1 255.255.255.0 !

Documento IMC 6032 AEDG Issue 2, April 2005

- 61/76 -

DCN COURSESiemens Radio IP Equipment interface Serial0/0 ip address 10.10.12.1 255.255.255.0 encapsulation ppp ! interface Ethernet0/1 ip address 10.10.10.2 255.255.255.0 ! router rip network 10.0.0.0 []

Router R_3640_2[] interface Ethernet0/0 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 ! interface FastEthernet0/1

Documento IMC 6032 AEDG Issue 2, April 2005

- 62/76 -

DCN COURSESiemens Radio IP Equipment ip address 10.10.40.1 255.255.255.0 ! router rip network 10.0.0.0 ! []

Documento IMC 6032 AEDG Issue 2, April 2005

- 63/76 -

DCN COURSESiemens Radio IP Equipment

9.2.

D-EXTERNAL CONNECTIONSIn 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.

Serial0/0: 10.10.12.1/24 R_3640_1 Serial 3/1: 10.10.12.2/24 NetViewer R_3640_2 Eth0/0: 10.10.30.2/24 10.10.30.1/24 Serial 3/0: 10.10.11.1/24 Serial 0/0: 10.10.11.2/24

Eth0/1: 10.10.10.2/24

Fa0/0: 10.10.10.1/24 R_3725 Fa0/1: 10.10.40.1/24

10.10.40.2/24

10.10.41.2/24

10.10.40.4/24 10.10.42.20/24

D-Ext

10.10.42.18/24

10.10.51.2/24

10.10.50.2/24

10.10.50.4/24

10.10.52.4/24 10.10.43.2/24 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

Documento IMC 6032 AEDG Issue 2, April 2005

- 64/76 -

DCN COURSESiemens Radio IP Equipment encapsulation ppp ! interface Ethernet0/1 ip address 10.10.10.2 255.255.255.0 ! router rip network 10.0.0.0 []

Documento IMC 6032 AEDG Issue 2, April 2005

- 65/76 -

DCN COURSESiemens Radio IP Equipment

9.3.

D-EMBEDDED CHANNELSIn 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.

Serial0/0: 10.10.12.1/24 Cisco 3640_1 Serial 3/1: 10.10.12.2/24 NetViewer Cisco 3640_2 Eth0/0: 10.10.30.1/24 Serial 3/0: 10.10.11.1/24 Serial 0/0: 10.10.11.2/24

10.10.41.2/2 4 Eth0/1: 10.10.10.2/24

Fa0/0: 10.10.10.1/24 Cisco 3725 E1 0/4: 10.10.50.101/24

10.10.40.4/24

10.10.30.2/24

10.10.40.4/24

E1

10.10.42.20/24

D-Ext10.10.51.2/24 10.10.50.2/24 10.10.50.4/24 10.10.52.4/24 10.10.42.18/24 10.10.43.2/24

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.

Documento IMC 6032 AEDG Issue 2, April 2005

- 66/76 -

DCN COURSESiemens Radio IP Equipment

The configuration of the Cisco 3725 router follows: Router 3725[] controller E1 0/4 channel-group 0 timeslots 1 speed 64 ! 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 ! interface Serial0/4:0 ip address 10.10.50.101 255.255.255.0 encapsulation ppp ! router rip network 10.0.0.0 []

Documento IMC 6032 AEDG Issue 2, April 2005

- 67/76 -

DCN COURSESiemens Radio IP Equipment

9.4.

INTERWORKING BETWEEN CISCO ROUTERS AND RAD FCD/IPIn 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.

Serial0/0: 10.10.12.1/24 Cisco 3640_1 Serial 3/1: 10.10.12.2/24 NetViewer Cisco 3640_2 Eth0/0: 10.10.30.1/24 Serial 3/0: 10.10.11.1/24 Serial 0/0: 10.10.11.2/24

10.10.41.2/2 4 Eth0/1: 10.10.10.2/24 Fa0/0: 10.10.10.1/24 10.10.40.4/24 Cisco 3725

Bridging Mode

10.10.30.2/24

Fa0/1: 10.10.40.1/24 10.10.40.4/24

10.10.42.20/24

D-Ext10.10.51.2/24 10.10.50.2/24 10.10.50.4/24 10.10.52.4/24 10.10.42.18/24 10.10.43.2/24

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[] interface FastEthernet0/0 ip address 10.10.10.1 255.255.255.0 ! interface Serial0/0

Documento IMC 6032 AEDG Issue 2, April 2005

- 68/76 -

DCN COURSESiemens Radio IP Equipment ip address 10.10.11.2 255.255.255.0 encapsulation ppp ! interface FastEthernet0/1 ip address 10.10.40.1 255.255.255.0 ! router rip network 10.0.0.0 ! []

RAD FCD-IPROUTING/BRIDGING MODE: LINK 1 ----------------------------1. 2. 3. Link type - BRIDGE ( Device name - FCD-IP )

Link protocol - PPP PPP settings

******************************************************* TYPE: LINK 1 -----------1. 2. 3. Bridge: IP Router: [Enabled ] [Disabled] ( Device name - FCD-IP )

IPX Router: [Disabled]

******************************************************* ROUTING/BRIDGING MODE: LINK 1 ----------------------------1. 2. 3. Link type - BRIDGE ( Device name - FCD-IP )

Link protocol - PPP PPP settings

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 69/76 -

DCN COURSESiemens Radio IP Equipment ---------------1. 2. PPP NATIVE

******************************************************* PPP SETTINGS: LINK 1 -------------------1. 2. 3. Header and Control Field Compression Protocol Field Compression IP Compression (V.Jacobsen - RFC 1144) - [NO ] - [NO ] - [YES] ( Device name - FCD-IP )

******************************************************* IP INTERFACE ADDRESS ( Device name - FCD-IP -------------------******************************************************* RIP MODE SETUP ( Device name - FCD-IP ---------------1. 2. LINK 1 LAN 1 RIP mode: [NO RIP] RIP mode: [NO RIP] ) )

******************************************************* CONFIGURATION SETUP: LINK 1 ---------------------------CURRENT ------1. 2. 3. 4. 5. Status Type Connection type Connection timeout (sec) Control signals mode Enabled Synchronous Answer & Originate 30 Ignore NEW --[Enabled Synchronous [Answer&Originate] 30 [Ignore] ] ( Device name - FCD-IP )

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 70/76 -

DCN COURSESiemens Radio IP Equipment E1 SETUP: LINK 1 ---------------1. 2. 3. 4. 5. 6. 7. 8. Clock master : [Link 1] Multiplier : [64 kbps] ( Device name - FCD-IP )

Time slots mapping Loopback E1 parameters Sub link E1 parameters Alarms filter Advanced setup

******************************************************* E1 TIME SLOTS MAPPING: LINK 1 ----------------------------TS1 TS2 TS3 TS4 TS5 TS6 TS7 TS8 TS9 [DATA LINK1] [DATA LINK1] [DATA LINK1] [DATA LINK1] [DATA LINK1] [DATA LINK1] [DATA LINK1] [DATA LINK1] [DATA LINK1] TS17 [DATA LINK1] TS18 [DATA LINK1] TS19 [DATA LINK1] TS20 [DATA LINK1] TS21 [DATA LINK1] TS22 [DATA LINK1] TS23 [DATA LINK1] TS24 [DATA LINK1] TS25 [DATA LINK1] TS26 [DATA LINK1] TS27 [DATA LINK1] TS28 [DATA LINK1] TS29 [DATA LINK1] TS30 [DATA LINK1] TS31 [DATA LINK1] ( Device name - FCD-IP )

TS10 [DATA LINK1] TS11 [DATA LINK1] TS12 [DATA LINK1] TS13 [DATA LINK1] TS14 [DATA LINK1] TS15 [DATA LINK1] TS16 [NC ]

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 71/76 -

DCN COURSESiemens Radio IP Equipment

E1 PARAMETERS: LINK 1 --------------------1. 2. 3. 4. 5. 6. Frame type CRC-4 Sync Idle code (hex) Rx gain

( Device name - FCD-IP

)

: [G732S] : [ON] : [FAST] : 7C : [30 dB]

Remote Alarm Indication : [ON]

******************************************************* LAN SETTINGS ( Device name - FCD-IP )

1. LAN Full Duplex: [Disable]

Documento IMC 6032 AEDG Issue 2, April 2005

- 72/76 -

DCN COURSESiemens Radio IP Equipment

9.5.

IP/OSI TUNNELLINGIn 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.

10.10.40.4/24 NSAP_1

NetViewer

10.10.40.101/24

NSAP_2

NSAP_3

10.10.69.10/24 NSAP_4 10.10.69.20/24

OSI

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 73/76 -

DCN COURSESiemens Radio IP Equipment

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 74/76 -

DCN COURSESiemens Radio IP Equipment

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

Documento IMC 6032 AEDG Issue 2, April 2005

- 75/76 -

DCN COURSESiemens Radio IP Equipment

Figure 53b

- End of document -

Documento IMC 6032 AEDG Issue 2, April 2005

- 76/76 -


Recommended