DCNA Inst Guide

DCN Adapter C4.0 InstallationGuide

DN01174805 © Nokia Corporation 1 (38)Issue 3-0 en Nokia Proprietary and Confidential

DCN Adapter C4.0 Installation Guide

The information in this documentation is subject to change without notice and describes onlythe product defined in the introduction of this documentation. This documentation is intendedfor the use of Nokia's customers only for the purposes of the agreement under which thedocumentation is submitted, and no part of it may be reproduced or transmitted in any form ormeans without the prior written permission of Nokia. The documentation has been prepared tobe used by professional and properly trained personnel, and the customer assumes fullresponsibility when using it. Nokia welcomes customer comments as part of the process ofcontinuous development and improvement of the documentation.

The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However, Nokiahas made all reasonable efforts to ensure that the instructions contained in the documentationare adequate and free of material errors and omissions. Nokia will, if necessary, explain issueswhich may not be covered by the documentation.

Nokia's liability for any errors in the documentation is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL(INCLUDING MONETARY LOSSES), that might arise from the use of this documentation orthe information in it.

This documentation and the product it describes are considered protected by copyrightaccording to the applicable laws.

NOKIA logo is a registered trademark of Nokia Corporation.

Other product names mentioned in this documentation may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright © Nokia Corporation 2007. All rights reserved.

2 (38) © Nokia Corporation DN01174805Nokia Proprietary and Confidential Issue 3-0en

Contents

Contents 3

1 About this manual 71.1 Summary of changes 71.2 Where to find more information 7

2 Overview of the installation 92.1 Installation options 102.1.1 Management bus cabling 112.1.2 Protected Q1 bus cabling 14

3 Installing DCN Adapter C4.0 153.1 Mounting the rack shelf 153.1.1 Mounting the rack shelf to an ETSI rack 153.1.2 Mounting the rack shelf to a 19-inch rack 163.2 Installing the DCN Adapter units 173.3 Attaching cable trays 183.4 Cabling 193.5 Pin outs 203.5.1 Ethernet connector (8-pin RJ-45), 10Base-T 213.5.2 LMI connectors (8-pin RJ-45) 213.5.3 Q1 connectors 223.5.4 Power connector 23

4 Configuring DCN Adapter C4.0 254.1 Configuring the basic settings 254.1.1 IP address 254.1.2 IP route 254.1.3 Time settings 264.1.4 Checking the buses 26

5 Reference 295.1 Technical specifications 295.1.1 Interfaces 295.1.2 Power 305.1.3 Ambient conditions 315.1.4 EMC 31

Appendix A. Protected bus cabling 33A.1 RJ45 / 2x7 Euroconnector used with PDH network elements 33A.2 RJ45 / TQ used with FIU19 33A.3 RJ45 / RJ45 used with FIU19E 34

Glossary 35

Index 37


Software licenses

Copyright notices

DCN Adapter C4.0 contains licensed software not produced by Nokia.

ASH

Copyright (c) 1991, 1993

The Regents of the University of California. All rights reserved.

This code is derived from software contributed to Berkeley by Kenneth Almquist.

Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this listof conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, thislist of conditions and the following disclaimer in the documentation and/or othermaterials provided with the distribution.

3. All advertising materials mentioning features or use of this software mustdisplay the following acknowledgement: This product includes softwaredeveloped by the University of California, Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may beused to endorse or promote products derived from this software without specificprior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS ANDCONTRIBUTORS ‘‘AS IS’’ AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THEREGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCEOR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

Netkit-telnet

Copyright (c) 1991 The Regents of the University of California.



All rights reserved.

Redistribution and use in source and binary forms, with or without modification,are permitted provided that the following conditions are met:

1. Redistributions of source code must retain the above copyright notice, this listof conditions and the following disclaimer.

2. Redistributions in binary form must reproduce the above copyright notice, thislist of conditions and the following disclaimer in the documentation and/or othermaterials provided with the distribution.

3. All advertising materials mentioning features or use of this software mustdisplay the following acknowledgement: This product includes softwaredeveloped by the University of California, Berkeley and its contributors.

4. Neither the name of the University nor the names of its contributors may beused to endorse or promote products derived from this software without specificprior written permission.

THIS SOFTWARE IS PROVIDED BY THE REGENTS ANDCONTRIBUTORS ‘‘AS IS’’ AND ANY EXPRESS OR IMPLIEDWARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIEDWARRANTIES OF MERCHANTABILITY AND FITNESS FOR APARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THEREGENTS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT,INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, ORCONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO,PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE,DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVERCAUSED AND ON ANY THEORY OF LIABILITY, WHETHER INCONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCEOR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THISSOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCHDAMAGE.

Ntp

Copyright (c) David L. Mills 1992-2000Permission to use, copy, modify, anddistribute this software and its documentation for any purpose and without fee ishereby granted, provided that the above copyright notice appears in all copies andthat both the copyright notice and this permission notice appear in supportingdocumentation, and that the name University of Delaware not be used inadvertising or publicity pertaining to distribution of the software without specific,written prior permission. The University of Delaware makes no representationsabout the suitability this software for any purpose. It is provided "as is" withoutexpress or implied warranty.


About this manual

1 About this manualDCN Adapter C4.0 is a remote poller used with Q1 Agent.

This manual describes how to:

• mount the rack shelf

• install the DCN Adapter units

• attach the cable trays

• attach the cables

• configure the basic DCN Adapter C4.0 settings.

1.1 Summary of changes

Changes in the DCN Adapter C4.0 release

DCN Adapter C4.0 supports the use of protected buses.

In fixed networks, it is recommended to use the maximum of 1200 FEs per eachDCN Adapter (400 x 400 x 400), as long as there are no more than 200 NEsconnected to a bus.

DCN Adapter C4.0 is supported by Q1 Agent C2.1. Used together these twoproducts support the Network Test feature.

1.2 Where to find more information

DCN Adapter C4.0

For information on how to use DCN Adapter, see DCN Adapter C4.0 User Guide.

Q1 Agent

See the following documents:



• Q1 Agent C2.1 User Manual

• Q1 Agent C2.1 Help.

Network elements and node managers

For information on individual Nokia network elements and their node managers,consult the relevant user document for the network element or node managerconcerned.

Nokia NetAct

For information on DCN Adapter C4.0 and Q1 Agent in NetAct, see CellularTransmission Management Principles and Fixed Network ManagementPrinciples.

For instructions on integrating Q1 Agent to Nokia NetAct, see 1ntegratingTransmission Agents to NetAct.


Overview of the installation

2 Overview of the installationDCN Adapter C4.0 is a remote poller used with Q1 Agent.

Mechanically, DCN Adapter C4.0 consists of a number of plug-in units and a rackshelf. There can be up to six DCNA units in each rack shelf. The rack shelf is 1.5U high and can be installed in a standard 19-inch rack or in a 500-mm ETSI rack.

The following figure illustrates one DCN Adapter unit.

Figure 1. DCN Adapter C4.0 unit

The following figure illustrates the rack shelf.



Figure 2. The rack shelf (without DCN Adapter units)

The installation of the DCN Adapter is done in the following phases:

• mounting the rack shelf

• installing the DCN Adapter units

• attaching the cable trays

• attaching the cables.

These phases are described in detail in Chapter 3.

DCN Adapter unit starts automatically once the power cable is connected.

After the installation, you will need to configure the basic IP and time settings.Refer to Chapter 4.

2.1 Installation options

DCN Adapter is installed in a 1.5 U 19-inch rack shelf. Each rack shelf can housesix DCN Adapter units. Each of the six DCN Adapter units requires an individualTCP/IP address.



DCN Adapter is flexible in design allowing installation either on the equipmentsite or centrally with the Q1 Agent at the network management centre.

Installation of the DCN Adapter centrally with the Q1 Agent

This option requires that the Q1 buses are routed from the central managementstation to the equipment sites. The transportation of these buses can be done in avariety of ways and the final solution will depend on the operator’s network.Possible solutions for this scenario are:

• use of leased-line modems

• overheads within the microwave radio frame

• overheads within timeslot 0 (bits 5, 6, 7, 8) of Nokia primary rateequipment

• overheads within the frame of Nokia PDH equipment

• overheads with the frame of Nokia optical line equipment (DF2-8, DF34,DF140)

• overheads within an SDH frame

• use of traffic channels.

Installation of the DCN Adapter at each equipment site

This option removes the need for transporting the Q1 buses and thereforesimplifies the DCN design. The connection to the network element is a local on-site connection. The connection to the Q1 Agent and NetAct or 3rd-party NMS isestablished via TCP/IP.

Installation of the DCN Adapter at selected equipment sites with one DCNAdapter serving multiple sites

This option combines the previous two and can provide a cost effective solutionto the operator. The DCN Adapter can be located at central sites and the Q1 busescan be transported to surrounding sites using any of the methods described above.

2.1.1 Management bus cabling

There are two variants of the Q1 protocol in use within Nokia equipment: the"Classic or TMS4 Q1" and the newer "Nokia Q1". The newer Nokia Q1 protocolsupports additional functionality and allows features such as software downloadremotely. The FIU19 and MetroHub are two examples of network elements thatuse the Nokia Q1 protocol.

With equipment supporting the "Classic Q1" protocol, service interfaces (MI) areused to connect the processor to the management (service) bus by means of aserial interface.



The service interface can be connected to the data channel via the data hybrid bygiving the data hybrid activation command. The service interfaces (MI) of theNEs are connected in parallel.

The maximum number of MIs to be connected in parallel is 32.

Connection to NEs that run the Classic Q1 protocol

The following principles should be applied when making management busconnections to network elements running the TMS4 Q1 protocol (e.g. DM2,ACM2, DNT2M, DN2 and DF140).

Connection to NEs that run the Nokia Q1 protocol

The following principles should be applied when making management busconnections to network elements running the Nokia Q1 protocol (e.g. FIU19 andMetroHub).

Table 1. Management bus connection to the Classic Q1 protocol networkelements

DCNA Direction NE1 NE2 NE3........NE32

In- <- MOA MOA MOA

In+ <- MOB MOB MOB

Out- -> MIA MIA MIA

Out+ -> MIB MIB MIB

Table 2. If the management bus is to be extended via the overhead in NE3,the connection should be made as follows

DCNA DirectionNE3 (DataHybrid On)

Direction NE1 NE2

In- <- MOA / DIA <- MOA MOA

In+ <- MOB / DIB <- MOB MOB

Out- -> MIA / DOA -> MIA MIA

Out+ -> MIB / DOB -> MIB MIB



Caution

Nokia Q1 elements usually have two management ports. OUTx signals of one ofthe ports go to the INx signals of one of the ports in the next element and viceversa, and thus the elements form a chain. The DCN Adapter or other bus masteris connected in the same way to the free port of the last element at either end ofthe chain.

Connecting DI port signals in parallel may inhibit all traffic and might causeinternal damage to the elements. Nokia Q1 elements should always be chained.For doing so, observe the rules below in Section Chaining Nokia Q1 elements.

Chaining Nokia Q1 elements

When chaining Nokia Q1 elements, observe the following rules:

• Use only point-to-point cables with Nokia Q1 elements.

• If a Nokia Q1 element does not have a second management port, the Q1element must be placed at the end of the chain.

• If both Nokia Q1 and classic Q1 elements are connected to the same bus,the Nokia Q1 elements must be connected first and the classic Q1 elementsmust then be connected behind the Nokia Q1 elements.

Management bus interface characteristics

The management bus interface has the following characteristics:

• ITU-T (CCITT) standard V.11 (EIA RS-422)

• 4-wire cabling (2 twisted pairs)

• Output is never in hi-impedance state (always active)

• Data rate: selectable up to 19200 bit/s

Table 3. Connection to the Nokia Q1 network elements

DCNA Direction Management port

In- <- Out -

In+ <- Out +

Out- -> In -

Out+ -> In +



• Maximum bus length:

- 0.5 mm cable: 1.0 km- 0.4 mm cable: 0.7 km

• With the Classic Q1 protocol, maximum of 32 interfaces can be connectedin parallel.

2.1.2 Protected Q1 bus cabling

The DCN Adapter C4.0 management buses can be protected against breakage onthe transmission path through a ring configuration.

Buses can be polled in either protected or unprotected mode. In the unprotectedmode, polling is only done in the primary polling direction. In the protected mode,polling is done in both the primary and secondary direction.

If the polled NE does not answer to the poll in specified direction, DCNA C4.0generates a Loss of Supervision Connection In Primary/Secondary Directionalarm. The alarm may be noticed either in primary or secondary pollingdirections. If neither direction answers, the alarm is notified as Loss ofSupervision Connection.

For instructions on the protected bus cabling, see Appendix A Protected buscabling.


Installing DCN Adapter C4.0

3 Installing DCN Adapter C4.0This chapter instructs how to:

• mount the rack shelf

• install the DCN Adapter units

• attach the cable trays

• attach the cables.

3.1 Mounting the rack shelf

You can mount the rack shelf to an ETSI rack or to a 19-inch rack. For mounting,four screws and cage nuts are provided.

Each rack shelf has two mounting brackets - one on each side. The purpose of themounting brackets is to enable mounting the rack shelf into the rack. By defaultthe mounting brackets are pre-set for the ETSI rack.

3.1.1 Mounting the rack shelf to an ETSI rack

The mounting brackets are pre-set for the ETSI rack. To mount the shelf, fix thecage nuts to the desired position in the ETSI rack, and fasten the rack shelf withfour screws.



Figure 3. The rack shelf to be mounted in an ETSI rack

3.1.2 Mounting the rack shelf to a 19-inch rack

For the 19-inch rack you need to reverse the pre-set position of the mountingbrackets: instead of the long ends facing the front, you must have the short endsof the mounting brackets facing the front.

To do this, remove the screws that hold the mounting brackets in their place. Turnthe mounting brackets the other way round. Fasten the screws so as to fix themounting brackets in their place.

Once you have re-attached the mounting brackets, you can place the rack shelfinto the rack. Fix the rack shelf in its place with four cage nuts and screws.



Figure 4. The rack shelf to be mounted in an 19-inch rack

3.2 Installing the DCN Adapter units

There can be up to six DCN Adapter units in a rack shelf.

To install a DCNA unit, insert the unit to the rack shelf. Push until you feel thespring’s resistance. Open the slide latch with your thumb. Push the DCNA unit asfar as it goes. Release the slide latch so it locks.

Screws

Mounting bracketwith the short endfacing front



Figure 5. DCN Adapter unit to be installed in a rack shelf

3.3 Attaching cable trays

Two cable trays are provided for keeping the cabling in good order. The followingfigure illustrates the position of the cable trays in a rack shelf (without DCNAdapter units).



Figure 6. Upper and lower cable trays

Cable trays can be attached to the top or bottom front of the shelf, or both:

a. In case you have DCNA units in the upper row of the rack shelf, positionthe cable tray to the top front of the rack shelf. Fasten the screws so as tofix the cable tray firmly in its place.

b. In case you have DCNA units in the lower row of the rack shelf, positionthe cable tray to the bottom front of the rack shelf. Fasten the screws so asto fix the cable tray firmly in its place.

c. In case you have DCNA units in both the lower and upper rows of the rackshelf, you need to attach two cable trays, one up and another one down, asinstructed in (a) and (b).

3.4 Cabling

To operate the DCN Adapter units you need to attach the cables:

The cable trays

Screws

Screws



• power cable

• bus cables

• Ethernet cable.

Figure 7. The front panel of the DCN Adapter C4.0 unit

The power cable connects the DCNA power connector to the power supply. Oncethese are connected, the DCN Adapter unit starts up automatically.

The bus cables connect the DCN Adapter unit to nodes.

Ethernet cables are needed for the LAN connections.

Once you have attached the cables, you can use the cable trays for keeping thecabling in good order: put the cables from the upper DCNA units to the uppercable tray and, similarly, put the cables from the lower DCNA units to the lowercable tray. Guide the cables along the cable trays to bring them out from eitherside, or tie the cables in the middle area of the cable tray to bring them out frombehind.

For instructions on protected bus cabling, see Appendix A Protected bus cabling.

3.5 Pin outs

This section illustrates the pin outs for the following connectors:

• Ethernet

• LMI

• Q1 bus

• Power.



3.5.1 Ethernet connector (8-pin RJ-45), 10Base-T

Figure 8. Ethernet connector pin numbering (RJ-45)

3.5.2 LMI connectors (8-pin RJ-45)

Figure 9. LMI connector pin numbering (RJ-45)

18

Table 4. Pin configuration for the Ethernet connector

Pin SignalDirection

DCNA-Ethernet MDI signal

1 TX+ -> Transmit data +

2 TX- -> Transmit data -

3 RX+ <- Receive data +

4 -

5 -

6 RX- <- Receive data -

7 -

8 -

18



Figure 10. Connecting the DCN Adapter to Terminal

3.5.3 Q1 connectors

Figure 11. Q1 connector pin numbering (RJ-45)

For instructions on the protected Q1 bus cabling, see Appendix A Protected buscabling.

3 RxD 2 TxD 3 TxD

6 TxD4 Gnd

3 RxD7 Gnd

2 RxD5 Gnd

DCN AdapterRJ-45

Terminal (DTE)DB-25M

Terminal (DTE)DB-9M

18

Table 5. Pin configuration for the Q1 connectors

Pin Signal

1

2

3 OUT+

4 IN+

5 IN-

6 OUT-

7

8



3.5.4 Power connector

Figure 12. Pin configuration for the power connector

12

34

Table 6. Pin configuration for the power connector

Pin Signal

1 VPB + (Positive supply voltage)

2 VNB - (Negative supply voltage)

3

4 GND (Ground)


Configuring DCN Adapter C4.0

4 Configuring DCN Adapter C4.0This chapter instructs how to configure the basic DCN Adapter C4.0 settings.

4.1 Configuring the basic settings

After you have installed the DCN Adapter unit and plugged in the power cable,the DCN Adapter starts up automatically. You will need to configure the basic IPand time settings in order to enable the DCN Adapter to connect to the network.This is done by working with the command line interface (CLI).

For further information about the startup and the CLI commands, refer to DCNAdapter C4.0 User Guide.

4.1.1 IP address

To configure the IP address, execute the following CLI command:

# set ethernet ipaddress <IP_address> <IP_mask>

For example:

# set ethernet ipaddress 192.0.2.5 255.255.255.0

4.1.2 IP route

To configure the IP route, execute the following CLI command:

# set iproute <IP_address> <IP_mask> <gateway>

For example:

# set iproute 0.0.0.0 0.0.0.0 192.0.2.1



Tip

4.1.3 Time settings

There are two alternatives for setting the time:

a. If you have an NTP server, you can set the DCN Adapter time tocorrespond to the NTP server with the following CLI command:

# set ntp <IP_address>

For example:

# set ntp 192.0.2.10

b. In case there is no NTP server available, you can set the time by executingthe following CLI command:

# set time <new_time>

For example:

# set time 2007-01-12 11:09:00

The time needs to be set in ISO 8601 format.

Using the set time command with DCN Adapter, you will need to check thetime regularly. Using the set ntp command instead, which configures the DCNAdapter to use a Network Time Protocol (NTP) server, you do not need regulartime checks.

4.1.4 Checking the buses

You can check the DCN Adapter buses with Q1 Agent. See Q1 Agent Help formore information.

If you cannot check the buses with Q1 Agent, you can execute the followingcommands.

To check a bus

1. Execute the following CLI command:

$ enable bus <channel> <speed> [<protection>]

2. Execute the following command:


Configuring DCN Adapter C4.0

$ ste <bus> <address> m:4.1

The bus number here (Step 2) equals the channel number of the commandabove (Step 1).

3. If there is no answer from the network element, try increasing the value forfirst character timeout:

$ set fcTmo <channel> <200_ms_default>

where <200_ms_default> stands out for one number, which is thenumber of milliseconds before timeout.

Check the bus again (see Step 2).

4. Once you have checked that the bus works, disable the bus:

$ disable bus <channel>


Reference

5 ReferenceThis chapter describes the technical details of the DCN Adapter.

5.1 Technical specifications

This section describes the technical specifications of the DCN Adapter:

• interfaces

• power

• ambient conditions

• electromagnetic compatibility (EMC).

5.1.1 Interfaces

Table 7. Local management interface (LMI)

Local management interface (LMI)

Connector RJ45

Electrical specifications V.24/V.28

Supported circuits TxD, RxD, GND

Bit rate 9600 bit/s

Character format 8, no parity, 1 stop

Flow control None

Supported protocol Command line interface (CLI)



5.1.2 Power

Table 8. Ethernet interface

Ethernet interface

Connector RJ45

Electrical/physical link specifications IEEE 802.3

Signals TxD+, TxD-, RxD+, RxD-

Bit rate 10 Mbit/s, half duplex

Supported protocols IP, ARP, telnet/CLI, TFTP (client), ntp, http,ftp, Nokia Q1 Management pipe

Table 9. Q1 interfaces

Q1 interfaces

Connector 3 x RJ45

Electrical specifications V.11

Operation mode Bus master

Supported circuits Out+, Out-, In+, In- (for each interface)

Bit rate 300, 600,1200, 2400, 4800, 9600, 19200bit/s

Supported protocols Nokia Q1, Nokia Q1 Management pipe

Bus timeout 10 ms ... 10s

Table 10. Power feed

Power feed

Connector Molex Micro-Fit 4-pin

Operating voltage -20 to -75 VDC

Power consumption 10W


Reference

5.1.3 Ambient conditions

5.1.4 EMC

The electromagnetic compatibility (EMC) of the DCN Adapter complies with thefollowing specifications provided that special EMC structures (for example,subrack) and shielded cables and cabling practices required by these structuresare used.

Table 11. Climatic and mechanical requirements

Climatic and mechanicalrequirements

Transportation ETSI ETS 300 019-2-1 class 2.3 ETSIETS 300 019-2-2 class 2.3

Storage ETSI ETS 300 019-1-1 class 1.3E ETSIETS 300 019-2-1 class 1.3E

Operation ETSI ETS 300 019-1-3 class 3.1

Table 12. Installation environment

Installation environment

Unit's operating temperature range +5 to +40 ºC

Relative humidity 5% - 85% (non-condensing)

Table 13. EMC

EMC

EN 50081-1 (1992) Generic emission, residential,commercial, light industry

EN 50082-1 (1997) Generic immunity, residential,commercial, light industry



EN 61000-6-2:2001 Generic standards, immunity for industrialenvironments

ETS 300386-2 (1997) EMC requirements, telecommunicationnetwork equipment

C.I.S.P.R. 22 Class B Emission, information technologyequipment

Table 13. EMC (Continued)

EMC


Protected bus cabling

Appendix A. Protected bus cabling

This appendix describes the protected Q1 bus cables.

A.1 RJ45 / 2x7 Euroconnector used with PDH network elements

The following figure illustrates the cabling needed with PDH network elementssuch as DN2, ACL2, and ACN2.

Figure 13. RJ45 / 2x7 Euroconnector used with PDH network elements

A.2 RJ45 / TQ used with FIU19

The following figure illustrates the cabling needed with FIU19.

3 Out +4 In +5 In -6 Out -

DCNA 2x7 Euroconnectora6 MIB +c6 MOB +c7 MOA -a7 MIA

1 Out +2 In +7 In -8 Out -

RJ45 = One ConnectorBus 0Primary Dir

a6 MIB +c6 MOB +c7 MOA -a7 MIA

Bus 0Secondary Dir



Figure 14. RJ45 / TQ used with FIU19

A.3 RJ45 / RJ45 used with FIU19E

The following figure illustrates the cabling needed with FIU19E.

Figure 15. RJ45 / RJ45 used with FIU19E

3 Out +4 In +5 In -6 Out -

TQ

1 Q1 In +3 Q1 out +4 Q1 Out -2 Q1 In -

1 Out +2 In +7 In -8 Out -

RJ45 = One Connector

Bus 0Primary Dir

Bus 0Secondary Dir

TQ

FIU19

FIU191 Q1 In +3 Q1 out +4 Q1 Out -2 Q1 In -

3 Out +4 In +5 In -6 Out -

RJ45

4 Q1 In +3 Q1 out +6 Q1 Out -5 Q1 In -

1 Out +2 In +7 In -8 Out -

RJ45 = One Connector

Bus 0Primary Dir

Bus 0Secondary Dir

RJ45

FIU19E

FIU19E4 Q1 In +3 Q1 out +6 Q1 Out -5 Q1 In -


GlossaryARP Address Resolution Protocol

ASCII American Standard Code for Information Interchange

CD-ROM Compact Disc-Read-Only Memory

CLI Command Line Interface

DCN Data Communications Network

EMC Electromagnetic Compatibility

ETSI European Telecommunications Standards Institute

FIU 19 FlexiHopper Indoor Unit

GND, gnd Ground

HW Hardware

IP Internet Protocol

LAN Local Area Network

LMI Local Management Interface

MetroHub Nokia’s transmission node for the Nokia MetroSite solution

NMS Network Management System

Node manager A program that understands the specific details of a particular type or family ofnodes and supports the configuration and maintenance of these nodes.

Node manager serv-er

A Windows-based server which groups node managers into one system.

Nokia FlexiHopper Nokia’s family of Flexbus-compatible microwave radios for the 13, 15, 18, 23,26, and 38 GHz frequency bands. The Nokia FlexiHopper outdoor unit can beused with different indoor units (FIU 19, RRIC, FC RRI, and FXC RRI).

Nokia MetroHopper Nokia’s family of Flexbus-compatible radio for the 58 GHz frequency band. TheNokia MetroHopper outdoor unit can be used with different indoor units (FIU 19,RRIC, FC RRI, and FXC RRI).



Nokia NetAct Nokia’s NetAct Framework is an operations support system for managingnetworks and services. The open modular framework allows network operators tointegrate other operations support systems or IT systems and applications into asingle tailorable solution. Nokia NetAct consists of functionality areas, such asMonitor, which are grouped together according to the most relevant operatorprocesses. The functionality areas comprise functionality modules that can beprovided either by Nokia or a 3rd party.

NTP Network Time Protocol

PDH Plesiochronous Digital Hierarchy

Q1 Nokia proprietary management protocol

Q1 Agent Application used for supervising the network elements under DCN Adapter C4.0and Nokia AXC and for mediating between these and an upper-level managementsystem, such as Nokia NetAct.

RxD Received Data

SDH Synchronous Digital Hierarchy

STE Service Terminal Emulation

TCP/IP Transmission Control Protocol/Internet Protocol

Telnet Standard terminal emulation protocol defined in RFC 854.

TFTP Trivial File Transfer Protocol

TxD Transmitted Data

U Unit of height, 44.5 mm (in mechanics)

10Base-T 10 Mbit/s Ethernet specification.


IndexA

ACM2 12ambient conditions 31

B

basic settings 25bus cable 20buses 26

C

cable trays 18cabling 11, 19Classic Q1 protocol 11, 12command line interface 25configuring 25

D

DCN Adapter unit 9, 17DF140 12DM2 12DN2 12DNT2M 12

E

EMC 31ethernet connector 21ethernet interface 30

F

FIU19 11, 12

I

installation options 10interfaces 29IP address 25IP route 25

L

LMI 29LMI connector 21

M

management bus 11management bus interface 13management port 13MetroHub 11, 12MI 11mounting brackets 15

N

NetAct 8node managers 8Nokia Q1 protocol 11, 12

P

pin outs 20power 30power cable 20power connector 23

Q

Q1 Agent 7Q1 connector 22Q1 interfaces 30

R

rack shelf 9

S

service interface 11startup 25

T

TCP/IP address 10technical specifications 29time settings 26TMS4 Q1 protocol 12

DN01174805 ©Nokia Corporation 37 (38)Issue 3-0 en Nokia Proprietary and Confidential

DCNA Inst Guide

Documents

Transcript of DCNA Inst Guide