Node B Command Line

Interface
Lazy Guide to Common Commands
Ebrahim Jakoet
Lin Voigt

Whats covered?

This presentation provides a basic guideline for using the command line
interface to the Node B available in OSS for UMTS. The following items are
covered:

Logging into the Node B using NSA or telnet

Unix command line editing commands

LED status on boards

Node B and Board restarts

Working with configuration versions

Remote Shell login and Linkhandler paths

Printing VSWR, TMA current, Faults on sectors

Printing Board error logs

Printing active alarms on site

Parameter value get and set commands

Commercial in confidence 2

NCLI

2007-11-07

Login to the Node B using NSA

Click here
to login to
site

Commercial in confidence 3

Click and drag here to

increase window size

NCLI

2007-11-07

Telnet to the site

Click on Sun Tools -> Terminal to

open a terminal.

On customer lan you can also use

the dos command prompt by
clicking Start -> Run and then type
cmd.

telnet to the Node B by typing

telnet and the ip address of the
Node B.

The username and passwords are

all standardized to rbsxxxx where
xxxx is the site id.

Commercial in confidence 4

NCLI

2007-11-07

Editing commands

cursor-up: recall previous command

cursor-down: next command in history

CTRL-a: go to beginning of command line

CTRL-e: go to end of command line

CTRL-h: backspace

CTRL-d: delete (character to the right)

CTRL-k: delete to end of line

CTRL-u: delete to beginning of line

NB: These commands assume the Unix shell is used

Commercial in confidence 5

NCLI

2007-11-07

vii command

When you login you are on the CBU board.

Use vii to display the status of visual (optical) indicators on the

board that the command is executed on. The command returns
the status of the visual (optical) indicators, also known as the
Light Emitting Diodes (LED), together with a list of registered
clients.

Commercial in confidence 6

NCLI

2007-11-07

LED Indications
Fault LED (red)
Priority

State

Red LED behaviour

1 (highest)

Fault

(Steady Light)

No Fault

(Out)

Priority

State

Green LED behaviour

1 (highest)

Power not present

(Out)

Initial boot test

(16 Hz)

Load/Test in progress

(2 Hz)

Dependent Resource Missing

(0.5 Hz)

Power present

(Steady Light)

Priority

State

Yellow LED behaviour

1 (highest)

Board Locked

(Steady Light)

Shutdown in progress

(0.5 Hz)

Board Busy

(16 Hz)

Board Unlocked

(Out)

Operation LED (green)

Information LED (yellow)

Commercial in confidence 7

NCLI

2007-11-07

Node B Restart

On the CBU board, you can restart the Node B using the reload command
as follows:

Options

none: Warm restart. The operating system is restarted and all load
modules are restarted with conditional reload (reloaded if found faulty).

cold: Hardware on this board is reset and all load modules are
unconditionally reloaded.

coldwtest: Hardware on this board is reset and all load modules are
unconditionally reloaded. Hardware tests are performed and the results
reported.

refresh: All load modules on this board are unconditionally reloaded and
only a minimal set of initial tests are executed.

Commercial in confidence 8

NCLI

2007-11-07

Get the PIU ID

To get the Plug In Unit identities,

use the command getAttrObj piu
<piu-id>.

Try 1, 2, 3 if you dont know the

numbers and how they
correspond to the PIUs.

Instead of using piu, the following

objects can also be used in a
similar way:

me, piu, pgm, rpu, slot, or

subrack.

Commercial in confidence 9

NCLI

2007-11-07

Restart Node B or PIU

To restart the Node B,

use the command
restartObj me

To restart a specific
PIU use the command
restartObj piu <piu-id>
where the piu-id is
found as shown in the
previous slide

Use llog to see a log of

the restarts on a
board, llog l for a
more detailed printout.

Commercial in confidence 10

NCLI

2007-11-07

Configuration Versions

Use the command cv cu to see the

currently loaded configuration
version.

To list the last 50 available CVs,

use cv ls.

Use cv set <name> to make this CV

startable on the next reload
(restart).

Use cv mk <name> to save the

current configuration to <name>

Commercial in confidence 11

NCLI

2007-11-07

Remote Shell Login -lhsh

This command enables remote access to the command shell in another processor. The command uses the link
handler for the communication. The command can specify an optional command that is executed on the remote side.
If no such command is specified, a new interactive command shell session starts.

The command opens a connection to another processor through a link handler. <lnhpath> is used as a link
handler path to find the other side of the link. Depending on the given parameters, either:

A prompt is presented and you can execute commands as if you are logged in directly to <lnhpath>.

If a command is specified, only that command is executed and then the shell session terminates.

When a new command shell is started, the prompt is replaced by a prompt that tells you on what processor the shell
executes.

Commercial in confidence 12

NCLI

2007-11-07

Typical Node B Linkhandler Paths

Board BoardType

Swallocation

000100 CBU1

Main_CBU

000700 RAX13

RBS_RAXB

000800 RAX

RBS_RAXB

000900 RAX13

RBS_RAXB

001100 TX6HS-04

RBS_TXB

001200 RUIF

RBS_RUIFB

001200/port_0_dev_8

RU

001200/port_4_dev_9

RU

001200/port_8_dev_10

RU

**NB RAX boards start from Slot 09, then 08, 07 etc.
Commercial in confidence 13

NCLI

2007-11-07

List processes on board

The lhsh command uses the

address of the board you
want to connect to that
follows the format mmnn00,
where mm is the Subrack ID
and nn is the Slot ID / APN.

To see the port-dev numbers

on the RUIF board, use the
command lhsh 001200 ps
port*.

Commercial in confidence 14

NCLI

2007-11-07

LED status on RU and FU boards

To see the LED status on the RU boards, use the
following command:
lhsh 001200/port_x_dev_y vii

To see the LED status on the FU boards, use the

following command:
lhsh 001200/port_x_dev_y au3vii

Commercial in confidence 15

NCLI

2007-11-07

VSWR, TMA currents, Temp

Use the command

lhsh
001200/port_x_dev_
y fui get vswr to see
the VSWR reading.

Instead of vswr, use

devstat, faults, temp
to get the TMA
currents, faults and
temperature
respectively

Commercial in confidence 16

NCLI

2007-11-07

Error log for PIU

Use the command te log read to see the error log for a
particular board

Commercial in confidence 17

NCLI

2007-11-07

Working with Log files

Use the loglist command to see a complete list of

log files stored on the Node B.

The logattributes command gives more details for

each log file, including the path name that can be
used to printout the log contents.

Use the Unix cat command with the filename to

see the contents of a log file.

Commercial in confidence 18

NCLI

2007-11-07

Dump command

If a program crashes
(board restarts),
information about the error
is saved in the Post
Mortem Dump (PMD)
area, and then saved on a
file. This information can
be analyzed using the
dump command.

Using the pathname from

the list of .pmd files, enter
dump error i <filename>
to see more details about
the program crashes

Commercial in confidence 19

NCLI

2007-11-07

More Commands
help: See a full list of commands
Use ? <cmd> to print syntax and description
man <cmd> detailed description

te log read: Print the error logs

readclock: Read system clock [unix date format]
pboot show para: print the board and flash parameters
e.g. board type, revision, serial number, product
number and revision of the container software.
who: prints all users who are logged on

Commercial in confidence 20

NCLI

2007-11-07

Node Command Line Interface

To enter a special Node Command Line Interface enter ncli and you
will notice that the prompt changes to [ManagedElement=1]>

Type help to see a list of commands available in this shell.

Commercial in confidence 21

NCLI

2007-11-07

Current Alarms
Enter alarms to print all active alarms on the site.
Enter help alarms for more options

Commercial in confidence 22

NCLI

2007-11-07

Search for MO

Use the search command to find one or more MOs in the MO tree.
Command Syntax:

search <moAddress> [ <searchLevel> ] <MOtype> [ <filter> ]

Enter help search for more options

Commercial in confidence 23

NCLI

2007-11-07

Jump to MO

Use the jump command to change the working MO. It is

possible to traverse the Managed Object Model (MOM) in the
same manner as in a directory structure, using different operands.

The Relative Distinguished Name (RDN) of the new working MO

is displayed in the prompt.

Commercial in confidence 24

NCLI

2007-11-07

Reading parameter values

Use the get command to
retrieve the attributes
(parameters) and children of
an MO
Enter help get for a more
detailed description

Commercial in confidence 25

NCLI

2007-11-07

Changing parameter values

Use the set command to set attribute values for an
instance of an MO.
Enter help set for a more detailed description

Commercial in confidence 26

NCLI

2007-11-07

No of active Radio links

To see the
number of active
radio links, jump
to the
RadioLinks MO
on the sector
and use the get
command to
printout the
value of the
noOfRadioLinks
attribute.

Commercial in confidence 27

NCLI

2007-11-07

Understanding MOM

The Managed Object Model (MOM) defines

the information model with regard to node
management. It presents a view of all the
manageable resources in the node, and all
the parameters and actions associated with
these resources.

MOs form a tree-hierarchy, starting from the

root "Managed Element"

An MO represents a resource in the node,

either a physical resource such as a plug-in
unit, or a logical resource such as a software
program or a protocol. Each MO has
parameters associated with the resource,
called MO attributes.

An MO can be configured by setting values

for the MO attributes.

Shown below is the attribute OperState of the

T1PhysPathTerm MO, and the diagram on
the right shows where this MO fits in the MO
tree.

Commercial in confidence 28

NCLI

2007-11-07

Q&A

Commercial in confidence 29

NCLI

2007-11-07

Commercial in confidence 30

NCLI

2007-11-07