DCN Adapter User Guide

8/12/2019 DCN Adapter User Guide

http://slidepdf.com/reader/full/dcn-adapter-user-guide 1/40

DN01174856 © Nokia Corporation 1 (40)

Issue 1-0 en Nokia Proprietary and Confidential

DCN Adapter C3.0 User Guide




2 (40) © Nokia Corporation DN01174856

Nokia Proprietary and Confidential Issue1-0en

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 2003. All rights reserved.





Contents

Contents 3

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

2 Overview of DCN Adapter C3.0 92.1 About DCN Adapter C3.0 92.1.1 Rack shelf 92.1.2 DCN Adapter units 92.2 Applications 102.2.1 Network management 102.2.2 System connections 11

2.3 Functional description 122.3.1 Unit functions 122.3.2 Interfaces 132.4 Management 132.4.1 Command line interface (CLI) 142.4.2 Node managers 14

3 Using DCN Adapter C3.0 153.1 Starting up 153.2 Working with the command line interface 163.2.1 List of commands 173.3 Command descriptions 193.3.1 CLI session 19

3.3.2 DCN Adapter C3.0 settings 213.3.3 IP settings 243.3.4 Commissioning 313.4 Using node managers with DCN Adapter C3.0 33

4 Troubleshooting 354.1 Password 354.2 IP settings 354.3 Time settings 36

Glossary 37

Index 39










Software licenses

Copyright notices

DCN Adapter C3.0 uses 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 be

used 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 manual

This manual describes DCN Adapter C3.0 and its operation.

This manual is intended for teleoperators who use DCN Adapter C3.0 with Q1Agent for collecting fault management information from Nokia Q1 network elements.

1.1 Summary of changes

Changes in OSS3.1 Enhancement Delivery 1

This is a new document.

1.2 Where to find more information

DCN Adapter C3.0 installation

For information on installing and configuring DCN Adapter C3.0, refer to DCN Adapter C3.0 Installation Guide.

Q1 Agent

For information on Q1 Agent, refer to the following documents:

• Q1 Agent Installation Guide

• Q1 Agent Help.

Nokia NetAct

For information on how to integrate Q1 Agent with Nokia NetAct, refer toAppendix A of Q1 Agent Installation Guide.

For further information on DCN Adapter C3.0 and Q1 Agent in NetAct, see theNetAct document Cellular Transmission Management Principles.






Network elements and node managers

For information on individual Nokia network elements and their node managers,consult the relevant User Manual for the network element or node manager

concerned.



Overview of DCN Adapter C3.0



2 Overview of DCN Adapter C3.0

This chapter provides an overview of DCN Adapter C3.0.

2.1 About DCN Adapter C3.0

DCN Adapter C3.0 is a remote poller used with Q1 Agent. DCN Adapter C3.0collects Q1 alarms and other messages from Nokia’s Q1-managed nodes,including microwave radio and PDH/PRE equipment, and delivers thisinformation to Q1 Agent. Q1 Agent passes the fault management information toa network management platform, such as Nokia NetAct, for further alarmmonitoring.

Each Q1 Agent supports 100 DCN Adapters.

2.1.1 Rack shelf

Physically DCN Adapter C3.0 consists of a rack shelf and a number of DCNAdapter units. The rack shelf, containing the DCNA units, is 1,5 U high and canbe mounted on a standard 19-inch rack or on a 500-mm ETSI rack. The rack shelf has been designed to ease the installation and maintenance of DCN Adapters.

For instructions on mounting the rack, refer to DCN Adapter C3.0 InstallationGuide.

2.1.2 DCN Adapter units

The rack shelf is scalable with DCN Adapter units. Each rack shelf can containup to six DCN Adapter units. One DCN Adapter unit supports 600 functionalentities. Thus each rack shelf, with six DCN Adapters, can support up to 3600functional entities.

Each DCN Adapter unit supports 3 x V.11 Q1 buses. The buses can operate atdifferent data rates and can support up to 200 network elements. Both TMS4 Q1and Nokia Q1 connections are available on different buses.

Each DCN Adapter unit has a TCP/IP connector.






The CPU of the DCN Adapter unit runs Linux Operating System. The CommandLine Interface (CLI) is based on Linux.

For information on installing the DCN Adapter units, refer to DCN Adapter C3.0

Installation Guide.

2.2 Applications

DCN Adapter C3.0 is designed to facilitate connection of Nokia Q1-managedequipment such as FlexiHopper and DN2 to upper-level management systems.Q1 Agent is used together with the DCN Adapter to allow connection to NokiaNetAct or 3rd-party NMS platforms.

DCN Adapter can be used to connect Nokia transmission equipment in the

following environments:

• Nokia 3G network when Nokia AXC is not present.

• Nokia 3G network when hub sites exist with large concentrations of network elements.

• 3rd party 2G and 3G networks where Nokia cellular transmissionequipment is deployed.

• Nokia narrowband access networks.

DCN Adapter is a robust and fault-tolerant device that does not require daily

supervision or maintenance after it has been initially installed and configured. Awatchdog timer in the device provides automatic recovery from possible softwarefailures. Thus, DCNA can be located at remote network sites.

The capacity of the DCNA is three management buses containing a total numberof 600 Functional Entities (FEs). Each bus should contain no more than 200 FEs.Six DCNA units can be installed in a 19-inch 1,5 U rack shelf. Each of the DCNAdapter units requires an individual TCP/IP address.

2.2.1 Network management

DCN Adapter together with Q1 Agent allow connecting Nokia Q1-managedequipment to Nokia NetAct or 3rd-party NMS. DCN Adapter connects to thenetwork elements using oneof the three available RS422 (V.11)buses.TheNokiaQ1 protocol is used for communications between the DCN Adapter and thenetwork elements. The Q1 protocol is a master slave protocol with each network element being polled in cycle by the DCN Adapter for a change in fault status.The fault data is transmitted to the Q1 Agent with the IP network being used asthe bearer. The Q1 Agent processes the fault data and converts this into SNMPformat prior to forwarding to NetAct or 3rd-party NMS.






Figure 1. Network management with DCN Adapter and Q1 Agent

2.2.2 System connections

DCN Adapter has an LMI port, which is used for initial configurations. This portis a V.24 port, which is used for configuring the TCP/IP settings of the DCNAdapter in order that communications with the Q1 Agent can be established.

DCN Adapter and Q1 Agent communicate using the TCP/IP network for whichthe DCN Adapter has an Ethernet (RJ45) connector.

DCN Adapter has three RS422 (V.11) buses for connecting Nokia Q1-managednetwork elements. The elements to be connected each contain one or more Q1management ports.

Thedetermination of the management busconfiguration is made in order to createa reasonable bus structure. The goal is to minimize the need of additionalcomponents such as modems and branching units. The reliability and theperformance of a transmission management network must also be taken intoconsideration.

3rd Party 3G BTS Site3rd Party RNC Site

Operator Seats

Node B

NodeManagerServer

Q1 Elements

OMCSite

IP

IP

RNC

STM-1

or E1

DCNA in Node B orin Site Support cabinet

SNMP

Q1 polling

IP

FlexiHopper

DCN Adapter C3.0

NokiaQ1 Agent






The first step is to find out what are the available data channels for thetransmission management network provided by existing transmission equipment.Those channels are based on direct sampling in the free bits of available framestructures and they are accessible via the service interfaces. In the network

elements there are two kinds of serial interfaces: service interfaces (MI) and datainterfaces (DI). The service interface is for connecting the equipment to amanagement bus. The data interface can be used for extending a management bus.

The next step is to select the data channels for the management buses and todetermine what are the access points of the selected channels.

Before determining howservice interface points of the equipment are allocated tomanagement buses, you should consider the following:

• The number of different addresses on a management bus sets a limit to thenumber of service interfaces, which can be connected to the same bus. Thenumber of management buses must be determined so that every network element can be connected to a management bus with a unique address.

• If pieces of transmission equipment cannot provide the required number of data channels for the management buses, additional components areneeded. A compromise between costs and reliability may be necessary toget a reasonable bus structure.

For detailed information about DCN Adapter installation options, refer to DCN Adapter C3.0 Installation Guide.

2.3 Functional description

2.3.1 Unit functions

DCN Adapter connects to Q1 elements through a Q1 bus. The DCN Adapter pollsall activated Q1 addresses and reads the alarm status from the selected devices. If the DCN Adapter detects an alarm, it forwards data over the IP network to the Q1Agent which in turn generates a Simple Network Management Protocol (SNMP)trap, which is sent to Nokia NetAct or a 3rd-party NMS.

Command line interface (CLI) is used for configuring the DCN Adapter itself.

The CLI is available through LMI and is used to set the network settings of theDCN Adapter.

Front panel leds

The front panel leds work as follows:

• lower led green - power on

• lower led yellow - writing to disk






• upper led green - ethernet link connected

• upper led flashing - packet received or sent.

2.3.2 Interfaces

Ethernet interface

The Ethernet interface is used for connecting the DCN Adapter to a local Ethernetmanagement network, or to a bridge or a router providing a gateway to a remotemanagement network. The Ethernet interface is standard 10 Mbit/s half duplex10Base-T interface. The physical connector is an 8-pin RJ-45 connector.

Local management interface (LMI)

The local management interface is used for the local management or

commissioning of the DCN Adapter and Q1 elements at the site. The LMI has tobe used to configure the basic IP address related configuration to the DCNAdapter.

The LMI is an asynchronous V.24 serial interface with a fixed operation speed of 9600 bits/s. The character format is 8 data bits with no parity and 1 stop bit. Thephysical connector is an 8-pin RJ-45 connector.

Q1 interface

DCN Adapter contains three Q1 interfaces to facilitate connection of the network elements. Each interface is a separate Q1 bus and the elements connected to thebus must have a unique Q1 address.

Nokia Q1 Management pipe

The Nokia Q1 Management pipe allows the use of node managers forcommunicating with the Q1-managed network elements connected to the DCNAdapter.

The node managers use General Communication Service (GCS) as thecommunication stack. GCS is connectedto the Nokia Q1 Management pipe of theDCN Adapter. The Nokia Connection Tool, which is a part of GCS, allows youto define Q1 connections that are saved in the node manager address database.These connections are required to enable a node manager to connect to a node via

the DCN Adapter.

2.4 Management

The DCN Adapter supports two management mechanisms:






• Command Line Interface (CLI)

• Nokia Q1 Management pipe (node managers).

2.4.1 Command line interface (CLI)

Using the CLI in the DCN Adapter, the user can give text string commands froma terminal or a terminal emulator. The CLI is used to commission the DCNAdapters initial settings. These settings include the TCP/IP address and otherrelated network settings.

For a detailed description of CLI commands, see Chapter 3 of this manual.

2.4.2 Node managers

Nokia node managers are used to allow configuration and testing of the network elements under the DCN Adapter. The node managers reside on a Node ManagerServer PC. The DCN Adapter provides an interface known as the Nokia Q1Management pipe which is used to transport the node manager traffic through theDCN Adapter to the network element in question.



Using DCN Adapter C3.0



3 Using DCN Adapter C3.0

This chapter instructs how to:

• start up

• work with the command line interface (CLI)

• use node managers with DCN Adapter C3.0.

3.1 Starting up

Once the power cable is connected, DCN Adapter C3.0 starts up with thefollowing prompt:

LILO boot:

You have two options:

a. automatic startup - you can wait for the system to start up automatically

b. controlled startup - you can by-pass the automatic startup and control thestartup settings.

Automatic startup

After a few seconds, the system starts up automatically with default settings.Unless you want to change these settings, DCN Adapter C3.0 is ready to be usedafter the startup sequence has completed.

Controlled startup

If you want to by-pass the automatic startup, you can type any character beforethe few seconds’ timeout. This allows you to change the default startup settings,if desired.

The following table explains the options available for controlling the startup.






Backing up the software

Primary and secondary software options give you the possibility to ensurebackups.

For instance, after you have upgraded the DCN Adapter C3.0 software, thesystem starts up with the kernel parameters defined in the upgrade. If the startupis successful, the upgraded software becomes the default option (e.g., secondary).However, if the system fails to boot, then the previous default option (primary)will be loaded instead, so the system may revert to the existing software version.

3.2 Working with the command line interface

The command line interface (CLI) is locally available over Local ManagementInterface (LMI). Remotely, the CLI can be accessed through a telnet session.

The CLI can be used to commission and configure DCN Adapter C3.0.

Table 1. Options for controlling the startup

Command Explanation<enter> Pressing <enter> skips the timeout sequence. This can be used

for quickening the startup, if you do not want to change the

default settings. DCN Adapter C3.0 starts up with the default

software (primary) defined in the factory.

1 Typing 1 loads the primary software.

2 Typing 2 loads the secondary software.

primary Typing primary and pressing <enter> loads the primary

software. This equals to the quick command 1 but allows more

kernel options to be added.

secondary Typing secondary and pressing <enter> loads the secondary

software. This equals to the quick command 2 but allows more

kernel options to be added.

single Typing this kernel option and pressing <enter> after the

primary or secondary command gives you the root

privileges. As the user root, you can access the CLI without

being asked for the password. For example: primary

single

? This quick command shows the options available.










• Service Terminal Emulation

• Set first character timeout

3.3 Command descriptions

The following sub-sections illustrate how to use the CLI commands.

3.3.1 CLI session

The commands related to the CLI session are described below.

Table 2. Exit

Command Exit

Description The command terminates the CLI session.

Syntax exit

Arguments None

Examples # exit

DCNA C3.0

192.122.23.5 login:

Table 3. Help

Command Help

Description This command shows the CLI commands and their syntaxes.






Syntax help

Arguments None

Example $ help

CLI commands:

set

delete

show

enable

disable

download

save

ste

Usage: set ethernet ipaddress <ipadd> <ipmask>

set iproute <ipdest> <ipmask> <gw>

set iproute 0.0.0.0 0.0.0.0 <gw> (for default gateway)

set ipfilter <ipadd> <ipmask>

set time YYYY-MM-DD hh:mm[:ss]

set ntp <NTP server>

set fcTmo <channel> <timeout>

Usage: delete iproute <ipadd>

delete ipfilter <ipadd> <ipmask>

delete ntp

Usage: show stat [ethernet|ip|iproute|ipfilter|arp]

show time

show software

show log

show ntp

Usage: enable bus <channel> <speed>

channel = 0, 1 or 2

speed = 300, 600, 1200, 2400, 4800, 9600, 19200

Usage: disable bus <channel>

channel = 0, 1 or 2

...

$

Table 3. Help (Continued)

Command Help






3.3.2 DCN Adapter C3.0 settings

The commands related to the DCN Adapter C3.0 settings are described below.

Table 4. Open CLI session

Command Open CLI sessionDescription The user presses the ENTER key in the LMI session or connects over the network using telnet.

You need to log in by giving the username and password.

NOTE: If you are using telnet, remember to log out after you have finished your session. The

sessions remain open until they are closed by logging out. To see the open sessions use the

ps command. To kill unnecessary sessions use the command kill -9 ‘pid’.

Syntax -

Arguments None

Examples DCNA C3.0

192.122.23.5 login: root

Password:#

Table 5. Switch to other user

Command Switch to other user

Description Starts a new CLI session as the indicated user. If the user entering su is unprivileged, the

password for the indicated user is asked. Exit will return to the prior CLI session of the previous

user.

Syntax su <user>

Arguments Optional parameter: user. The default user is root.

Examples $ su guest

Password:

# su guest

$ exit

# exit

$






Table 6. Set time

Command Set timeDescription Sets time settings as defined in ISO 8601. Note: if you have an NTP server, you should

configure the DCN Adapter to use it instead of using this command. If you use this command,

you will need to check the time regularly.

Syntax set time <new time>

Arguments Time in ISO 8601 format. The time has to be set in UTC time, not local time.

Examples # set time 2002-03-14 09:47:00

Fri Apr 26 09:47:00 UTC 2002

#

Table 7. Download DCNA software

Command Download DCNA software

Description Downloads DCN Adapter C3.0 software from http, ftp, or tftp servers.

Syntax a) download <http_URL>

b) download <ftp_URL>

c) download <IP_address> <file_name>

Arguments The http URL or the ftp URL of the file server. In the case of tftp server, the IP address and the

file name.

Examples # download http://172.172.172.172/dcna_C30.img

release=C30_A0

buildtime=”Thu Mar 14 12:31:38 UTC 2002”

mke2fs 1.19, 13-Jul-2000 for EXT2 FS 0.5b, 95/08/09

Installing new software, please wait...

Added primary (alias 1)*

Added secondary (alias 2)

Download complete. Please reboot.

#

Table 8. Password

Command Password

Description Changes the user password.






Syntax passwd [username]

Arguments Username is optional.

Examples # passwd guest

Changing password for guest

Enter the new password (minimum of 5, maximum of 8 characters)

Please use a combination of upper and lower case letters and

numbers.

Enter new password:

Re-enter new password:

Password changed.

#

Table 8. Password (Continued)

Command Password

Table 9. Reboot

Command Reboot

Description Reboots the system.

Syntax reboot

Arguments None

Examples # reboot

Broadcast message from root (ttyS0) Thu Apr 11 12:44:47 2002.

The system is going down for reboot NOW !!

Table 10. Show time

Command Show time

Description Displays the current date and time.

Syntax show time

Arguments None

Examples $ show time

2002-08-22 10:25:15 UTC

$






3.3.3 IP settings

The commands related to IP settings are described below.

Table 11. Show DCNA software version

Command Show DCNA software versionDescription Displays the DCN Adapter C3.0 software version.

Syntax show software

Arguments None

Examples $ show software

Currently running <primary/secondary> software

Primary software is release C3.0_A0 compiled on Fri

Apr 26 10:39:06 UTC 2002

Secondary software is release c3.0 compiled on Fri

Apr 26 10:21:03 UTC 2002

$

Table 12. Show internal log

Command Show internal log

Description Displays the internal log of DCN Adapter C3.0.

The listing can be interrupted by pressing CTRL-C, paused by CTRL-S, and resumed by

pressing CTRL-Q.

Syntax show log

Arguments None. Pressing SPACE displays the next page of text.

Examples # show log

Apr 22 15:35:23 172 daemon.warn klogd: VFS: Mounted root (ext2

filesystem) readonly

Apr 22 15:35:23 172 daemon.warn klogd: Freeing unused kernel

memory: 68k freed

Apr 22 15:35:24 172 cron.info /sbin/cron[89]: (CRON) INFO

(pidfile fd = 3)

Apr 22 15:35:24 172 cron.info /sbin/ cron[91]: (CRON) STARTUP

(fork ok)

Apr 22 15:35:24 172 auth.info login[93]: root login on ‘pst/0’

from ‘172.16.1.3’#






Table 13. Delete IP filter

Command Delete IP filterDescription Deletes the filter from incoming IP packets.

Syntax delete ipfilter <IP_address> <IP_mask>

Arguments Both arguments are IP strings consisting of four decimal numbers separated by dots with

values between 0 and 255.

Examples Example 1

# delete ipfilter 192.122.23.0 255.255.255.0

Confirm setting? y/n y

#

Example 2

# delete ipfilter 192.122.23.0 255.255.255.0

Confirm setting? y/n n

Setting cancelled

#

Table 14. Delete IP route

Command Delete IP route

Description Deletes static IP route.

Syntax delete iproute <IP_route>

Arguments The argument is an IP string consisting of four decimal numbers separated by dots with values

between 0 and 255.

Examples Example 1

# delete iproute 192.168.23.4


#

Example 2

# delete iproute 192.168.23.4


Setting cancelled#






Table 15. Delete NTP settings

Command Delete NTP settingsDescription Deletes the existing NTP settings.

Syntax delete ntp

Arguments None

Examples # delete ntp

#

Table 16. Display ARP (Address Resolution Protocol) table

Command Display ARP (Address Resolution Protocol) table

Description Displays ARP table.

Syntax show stat arp

Arguments None

Examples $ show stat arp

Address Hwtype HWaddress Flags Mask Iface

172.16.1.3 ether 00:B0:D0:18:40:15 C eth0

172.16.1.21 ether 00:B0:D0:FA:97:B9 C eth0

$

Table 17. Display Ethernet interface statistics

Command Display Ethernet interface statistics

Description Displays Ethernet interface statistics.

Syntax show stat ethernet

Arguments None

Examples $ show stat ethernet

eth0 Link encap:Ethernet HWaddr 00:04:A7:02:80:B2inet addr:172.16.1.2 Bcast:172.16.1.255 Mask:255.255.0.0

UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

RX packets:3306 errors:0 dropped:0 overruns:0 frame:0

TX packets:2322 errors:0 dropped:0 overruns:0 carrier:0

collisions:77 txqueuelen:100

Interrupt:10 Base address:0x320

$






Table 18. Display filtering table

Command Display filtering tableDescription Displays the filtering table.

There are filters that accept (a) ICMP, (b) the incoming NTP traffic, (c) localhost, (d) all packets

by default.

a) ICMP is used for ping, notifications for IP failures, etc. It is recommended that you set the

filtering to accept ICMP, although this is not essential for the IP to work.

b) the incoming NTP traffic is filtered through the UDP port used for this purpose.

c) Localhost is required for the STE command to contact the poller.

d) NOTE: You need to remove the default filter that accepts all packets, before any of the

added IP filters restrict the IP traffic to the specified addresses. This is because the filter chainhas a DROP policy that will discard all packets that are not accepted. The default filter can be

seen in the "show stat ipfilter" listing as line:

xxx xxx ACCEPT all -- any any anywhere anywhere

To remove the default filter the source address "anywhere" is given in the delete ipfilter

command as in:

# delete ipfilter 0.0.0.0 0.0.0.0

The source address for host n.n.n.n is given in the set and delete ipfilter commands with

netmask 255.255.255.255:

# set ipfilter 10.10.10.10 255.255.255.255

# show stat ipfilterChain INPUT (policy DROP 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

...

0 0 ACCEPT all -- any any 10.10.10.10 anywhere

Source subnets are displayed with the number of bits set in the mask:

# set ipfilter 10.10.10.0 255.255.255.0

# show stat ipfilter

Chain INPUT (policy DROP 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination...

0 0 ACCEPT all -- any any 10.10.10.0/24 anywhere






Syntax show stat ipfilter

Arguments None

Examples # show stat ipfilter

Chain INPUT (policy DROP 0 packets, 0 bytes)

pkts bytes target prot opt in out source destination

1 92 ACCEPT icmp -- any any anywhere anywhere

15 1140 ACCEPT udp -- any any anywhere anywhere

udp spt:ntp dpt:ntp

0 0 ACCEPT all -- lo any anywhere anywhere

673 1555K ACCEPT all -- any any anywhere anywhere

#

Table 18. Display filtering table (Continued)

Command Display filtering table

Table 19. Display IP interface statistics

Command Display IP interface statistics

Description Displays IP interface statistics.

Syntax show stat ip

Arguments None

Examples $ show stat ip

Ip:

4976 total packets received

0 forwarded

0 incoming packets discarded

2876 incoming packets delivered

1990 requests sent out

Icmp:

23 ICMP messages received

0 input ICMP message failed.

ICMP input histogram:echo requests: 23

32 ICMP messages sent

0 ICMP messages failed

ICMP output histogram:

destination unreachable: 9

echo replies: 23

...

$






Table 20. Display routing table

Command Display routing tableDescription Displays routing table.

Syntax show stat iproute

Arguments None

Examples $ sh stat iproute

Kernel IP routing table

Destination Gateway Genmask Flags Metric Ref Use Iface

127.0.0.0 * 255.0.0.0 U 0 0 0 Io

default 192.168.23.3 0.0.0.0.0 UG 0 0 0 eth0

$

Table 21. Save IP filter settings

Command Save IP filter settings

Description Saves the IP filter settings. This command is only needed if IP filters have been directly edited

by using the iptables Linux command (see iptables -h) .

Syntax save ipfilter

Arguments None

Examples # save ipfilter#

Table 22. Save IP route settings

Command Save IP route settings

Description Saves the IP route settings.This command is only needed if IP routes have been directly edited

by using the route Linux command (see route -h)

Syntax save iproute

Arguments None

Examples # save iproute

#






Table 23. Set Ethernet IP configuration

Command Set Ethernet IP configurationDescription Sets the Ethernet IP configuration. The IP address and the IP mask must be supplied.

Syntax set ethernet ipaddress <IP_address> <IP_mask>



Examples Example 1

# set ethernet ipaddress 192.168.12.1 255.255.255.0


#

Example 2

# set ethernet ipaddress 192.168.12.1 255.255.255.0


Setting cancelled

#

Table 24. Set IP filter

Command Set IP filter

Description Sets a filter to Incoming IP packets.

Syntax set ipfilter <IP_address> <IP_mask>



Examples # set ipfilter 192.122.23.0 255.255.255.0

#

Table 25. Set IP route

Command Set IP route

Description Sets a static IP route.

Syntax set iproute <IP_address> <IP_mask> <gateway>

Arguments All arguments are IP strings consisting of four decimal numbers separated by dots with values

between 0 and 255.

Examples # set iproute 0.0.0.0 0.0.0.0 192.168.23.3

#






3.3.4 Commissioning

The commands related to commissioning are described below.

Table 26. Set NTP settings

Command Set NTP settingsDescription Sets the NTP server IP address. At the same time this command sets the DCN Adapter clock

to the NTP time.

Syntax set ntp <IP address>

Arguments The argument is an IP string consisting of four decimal numbers separated by dots with values

between 0 and 255.

Examples # set ntp 192.100.130.244

22 May 09:48:14 ntpdate[573]: adjust time server 192.100.130.

244 offset -0.000087 sec

#

Table 27. Show NTP settings

Command Show NTP settings

Description Shows the NTP server settings

Syntax show ntp

Arguments None

Examples $ show ntp

server 127.127.1.0 # local clockfudge 127.127.1.0 stratum 10

driftfile /etc/ntp/drift

multicastclient # listen on default 224.0.1.1

broadcastclient

broadcastdelay 0.008

authenticate no

server 131.228.20.25 prefer

$






Table 28. Enable bus

Command Enable busDescription Enables bus. NOTE: You should disable the bus, before adding the bus in the Q1 Agent.

Syntax enable bus <channel> <speed>

Arguments The channel values are: 0, 1, 2. The channel number is used as the number for the bus being

enabled. The speed values are: 300, 600, 1200, 2400, 4800, 9600, 19200.

Examples # enable bus 0 9600

#

Table 29. Disable bus

Command Disable bus

Description Disables bus.

Syntax Disable bus <bus>

Arguments The bus values are: 0, 1, 2.

Examples # disable bus 1

#

Table 30. Service Terminal Emulation

Command Service Terminal Emulation

Description The DCN Adapter executes a service terminal command with a specified network element.

Syntax ste <bus> <address> <command>

Arguments The bus values are 0, 1, 2. The address is identified with numbers in the range 0-4094. The

command is either m:<menu> or F<n>m:<menu> for FE <n>.

Examples Example 1

# ste 1 233 m:4,1

DN2#

Example 2

# ste 0 200 F3m:4,1

FlexiHopper

#






Note

3.4 Using node managers with DCN Adapter C3.0

The Nokia Q1 Management pipe allows you to use node managers with DCNAdapter C3.0. By using node managers you can communicate with the Q1-managed network elements connected to the DCN Adapter.

The Nokia Q1 Management Pipe works only after being set up by Q1 Agent. Forcommissioning, the CLI has commands for doing the basic setup of the interface.

See Section 3.3.4 ‘Commissioning’ above.

GCS

The node managers use General Communication Service (GCS) as thecommunication stack. The Nokia Connection Tool, which is a part of GCS,allows you to define Q1 connections that are saved in the node manager addressdatabase. These connections are required to enable a node manager to connect toa node via the DCN Adapter C3.0. A connection type, Nokia Q1 Connection Pipe,must be selected for communicating with the DCN Adapter C3.0. (Nokia Q1Connection Pipe refers to the LAN connection to the DCN Adapter C3.0.)

GCS is connected to the Nokia Q1 Management pipe of the DCN Adapter C3.0.When you create Q1 connections (of the type Nokia Q1 Connection Pipe), theusername and password are ‘PAM’.

Table 31. Set first character timeout

Command Set first character timeoutDescription Sets the first character timeout in the specified channel. The first character timeout specifies in

milliseconds the time to elapse between transmitting a Q1 command packet to a network

element and receiving the first character of the response packet.

Syntax set fcTmo <channel> <timeout>

Arguments The channel values are 0, 1, 2. The timeout value is given in milliseconds.

Examples # set fcTmo 1 20

#





Troubleshooting



4 Troubleshooting

This chapter describes how to overcome problems that you may face while usingDCN Adapter C3.0.

4.1 Password

Problem

You have lost the password for the user root.

Solution

Connect to LMI. Reboot by enteringreboot as the username to the login prompt.Wait for the LILO boot. Prompt, press TAB to see the list of choices, and take‘primary’ or ‘secondary’ as shown first on the listing: type primary single orsecondary single and press ENTER. At the # prompt, give the commandpasswd and set the new password.

After changing the password, ‘telinit 3’ will continue booting up normally, or youcan execute the command reboot.

4.2 IP settings

Problem

The connection to Q1 Agent, the node managers, or the network does not work.

Reason

You have a wrong IP address or IP filter, or the IP route to the client is missing.

Solution

Connect to LMI. Login as root. Set a valid IP address, IP filter, or IP route.






4.3 Time settings

Problem

The NTP server does not update the DCN Adapter clock time.

Reason

Your time setting in DCN Adapter differs too much from the one in the NTPserver.

Solution

Execute the set ntp CLI command. This sets the DCN Adapter time tocorrespond with the NTP server.





Glossary

Alarm An event, generated by a node (or other object), that represents a fault or otheroccurrence that may adversely affect the performance of the network.

ARP Address Resolution Protocol

ASCII American Standard Code for Information Interchange

BTS Base Transceiver Station

CLI Command Line Interface

CPU Central Processing Unit

DCNA See DCN Adapter C3.0.

DCN Adapter C3.0 A remote poller used between Q1 Agent and network elements.

ETSI European Telecommunications Standards Institute

Fault Management(FM)

Viewing fault management status of a node, enabling and disabling faultmanagement of a node, viewing current alarms list and viewing internal alarmslist.

GCS General Communication Service

LMI Local Management Interface

MetroHub Nokia’s transmission node for the Nokia MetroSite solution

Network Element(NE)

Telecommunication system belonging to the telecommunications environmentthat can be managed, monitored, and controlled in a telecommunications network and that has one or more standard interfaces and is identified by a uniquemanagement address.

NMS Network Management System

Node See Network Element (NE).

Node manager A program that understands the specific details of a particular type or family of nodes 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 allowsnetwork 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

OMC Operation and Maintenance Centre

PDH Plesiochronous Digital Hierarchy

Q1 Nokia proprietary management protocol

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

STE Service Terminal Emulation

STM Synchronous Transport Module

TCP/IP Transmission Control Protocol/Internet Protocol

Telnet Standard terminal emulation protocol defined in RFC 854

UTC Universal Time Coordinates. Internationally recognised accurate time derivedfrom atomic clocks distributed world-wide.

10Base-T 10 Mbit/s Ethernet specification



DN01174856 ©Nokia Corporation 39 (40)


Index

B

backups 16

buses 34

C

CLI command descriptions

CLI session 19

commissioning 31

DCN Adapter settings 21

IP settings 24

CLI command list 17

CLI commands

delete IP filter 25

delete IP route 25

delete NTP settings 26

disable bus 32

display ARP table 26

display ethernet interface statistics 26

display filtering table 27

display IP interface statistics 28

display routing table 29

download DCNA software 22

enable bus 32

exit 19

help 19

open CLI session 21

password 22

reboot 23

save IP filter settings 29

save IP route settings 29

set ethernet IP configuration 30

set first character timeout 33

set IP filter 30

set IP route 30

set NTP settings 31

set time 22

show date and time 23

show DCNA software version 24

show internal log 24

show NTP settings 31

STE 32

switch to other user 21

CLI session 19

command line interface (CLI) 16

D

DCN Adapter applications 10

DCN Adapter functional description 12

DCN Adapter interfaces 13

DCN Adapter overview 9

DCN Adapter settings 21

DCN Adapter unit 9

DCN Adapter unit functions 12

E

ethernet interface 13

G

GCS 13, 33

IIP settings 24, 35

L

LMI interface 13

N

NetAct 7

network elements 8

network management 10

node managers 8

, 13

, 33

Nokia Q1 Management pipe 13, 33

P

password 22, 35

port 34

Q

Q1 Agent 7

Q1 buses 9

Q1 connections 33

Q1 interface 13

R

rack shelf 9

S

startup 15




T

time settings 22, 36

troubleshooting 35

Documents

DCN Adapter User Guide