Sie sind auf Seite 1von 64

1

2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17

Content
Checking Alarm
HARDWARE STATUS
RESTART HW UNIT
LOCK&UNLOCK HW UNIT
CHECKING FINGERPRINT NO
RESTART NODEB-EMAS
LOGIN NODEB-HYPERTEMINAL
RESET NODEB-HYPERTEMINAL
RESET NODEB PASSWORD-HYPERTEMIN
Create CV Backup
Check Alarm log from EM
Check VSWR Check VSWR using Hyperteminal
Check VSWR using Putty
Clear Alarm Refer ALEX Document
Check IPRAN Status using EMAS
Check Local Status Using EMAS
Check Cell ID using EMAS

FOR CHECK CURRENT ALARM ON SITE > Alarm > Alarm List

Main Page

CHECK HARDWARE STATUS ON SITE> Equipment>Equipment>Sector Antenna=1>AuxPlug


CHECK HARDWARE STATUS ON SITE> Equipment>Equipment>Sector Antenna=1>AuxPlug

or Antenna=1>AuxPlugInUnit=2<FOR
Main Page
or Antenna=1>AuxPlugInUnit=RRUW-1< FOR RRUW UNIT

BELOW ARE SHOW YOU HOW TO RESTART RRUW UNIT> RIGHT CLICK ON >AuxPlu
BELOW ARE SHOW YOU HOW TO RESTART RET UNIT> RIGHT CLICK ON >AuxPlugI

restartAuxUnit ( );
Restarts the corresponding auxiliary plug-in unit.
The XP program with startState = ENABLED is reloaded from flash memory (forced reload).
Disturbances: This action can affect traffic. The auxiliary unit will be restarted.
Transaction required: No

T CLICK ON >AuxPlugInUnit=RRUW-1>restartAuxUnit
CLICK ON >AuxPlugInUnit=2> restartAuxUnit

ed reload).

Main Page

BELOW ARE SHOW YOU HOW TO LOCK & UNLOCK RET UNIT> RIGHT CLICK ON A
BELOW ARE SHOW YOU HOW TO LOCK & UNLOCK RRUW UNIT> RIGHT CLICK ON

After Select LOCK[0] or UNLOCK[1] Click on Apply and Set

OPERATING INSTRUCTIONS

144/1543-LZA 701 6003 Uen B

Additional Information

When a board is locked (Hard lock), that is, the administrativeState is set to LOCKED, the traffic on the board

When a board is shut down (Soft lock), that is, the administrativeState is set to SHUTTING_DOWN, the traffic o
another board. When all traffic has moved to another board, or after a maximum of ten seconds, the administr
remaining traffic on the board is interrupted.

When the board is LOCKED, no new alarms are issued and all alarms issued earlier by the board are ceased auto
maintenance on the board, provided the board is still in the subrack and is included in the current configuration

If the board is handling traffic, such as AAL2 and AAL5, shut down (Soft lock) is preferable, as there is little or n
faulty, it can be locked directly (Hard lock) without any further disturbance to traffic.

> RIGHT CLICK ON AuxPlugInUnit=2>Lock/Unlock


T> RIGHT CLICK ON AuxPlugInUnit=RRUW-1> Lock/Unlock

Main Page

ED, the traffic on the board ceases immediately.

HUTTING_DOWN, the traffic on the board ceases gradually and is transferred to


en seconds, the administrativeState is set to LOCKED automatically and any

the board are ceased automatically. It is possible to perform operation and


n the current configuration.

erable, as there is little or no disturbance to the traffic. However, if the board is

CHECK FINGERPRINT NUMBER

The LKF and the node are a pair. This means that when the LKF is installed in a node, you must verify

You can see the node fingerprint in the name of the LKF. The fingerprint is the string in the beginning o
fingerprint, date and time. If the file name is X1234567890_20060426_110803, the fingerprint for the
LKF generation are 26 April 2006 at 11:08:03. You can also read the fingerprint in the file itself. This fin
seen by reading it from the node itself.
To read the fingerprint from the node and verify it, do the following:
Find the Licensing MO where the attribute fingerprint indicates the licensing fingerprint of the node
Verify that the fingerprint string is the same as the fingerprint in the license key file.

Main Page

a node, you must verify that the LKF is intended for that node.

string in the beginning of the file name. The file name consists of:
3, the fingerprint for the node is X1234567890 and the date and time for
nt in the file itself. This fingerprint must be the same as the fingerprint

fingerprint of the node

RESTART NODE-B USING EMAS > SELECT >Equipment>ManagedElement=1>right click>manualResta

0
1
2
3

RESTART_WARM

Restarts the MO with the same software. The software is not reloaded from the disk. The traffic is a
RESTART_REFRESH

Reloads the software from the disk, restarts the MO, and resets parts of the hardware. The traffic i
RESTART_COLD

Reloads the software from the disk, restarts the MO, and resets all hardware. The traffic is affected
RESTART_COLDWTEST

Reloads the software from the disk, restarts the MO, and resets and tests the hardware. The traffic

right click>manualRestart

Main Page

om the disk. The traffic is affected least.

the hardware. The traffic is affected more than for a warm restart.

ware. The traffic is affected more than for a refresh restart.

s the hardware. The traffic is affected most.

Login using HyperTeminal

user name : rbs


password: rbs

Main Page

RESTART NODE B USING HYPERTEMINAL > COMMAND AS > reload

Main Page

RESET NODE B PASSWORD USING HYPERTEMINAL > COMMAND AS > passwd

Enter new password : rbs


Re-enter new password: rbs

Main Page

Create CV Backup

Only the characters "A - Z", "a -z", "0 - 9", "-" and "_" are allowed.
White spaces are allowed within the strings for the fields, comment and operatorName.
Each of the following fields has a string format with a maximum length of 40 characters:
- configurationVersionName
- identity
- operatorName
- comment
Transaction required: No

Parameters

Name: configurationVersionName
Description: One ASCII text string. It must be possible to create a directory with string. Do not use stri

Name: type
Default value: STANDARD
Description: Type of the configuration version [ STANDARD | TEST | OTHER ].
Name: operatorName
Description: The operator's name.
Name: comment
Description: The operator's comment.

Main Page

atorName.
characters:

th string. Do not use string "autocreated1" and "autocreated2" as CV name. They are used by the system.

sed by the system.

Check Alarm log from EM

Main Page

Check VSWR using Hyperteminal Command as >


for 3 Sector command
lhsh 000100/port_0_dev_6 fui get vswr
lhsh 000100/port_1_dev_7 fui get vswr
lhsh 000100/port_2_dev_8 fui get vswr
for 6 Sertor command
lhsh 000100/port_0_dev_12
lhsh 000100/port_1_dev_13
lhsh 000100/port_2_dev_14
lhsh 000200/port_0_dev_15
lhsh 000200/port_1_dev_16
lhsh 000200/port_2_dev_17

fui
fui
fui
fui
fui
fui

get
get
get
get
get
get

vswr
vswr
vswr
vswr
vswr
vswr

Main Page

Check VSWR using Putty over Telnet > Command as >


for 3 Sector command
lhsh 000100/port_0_dev_6 fui get vswr
lhsh 000100/port_1_dev_7 fui get vswr
lhsh 000100/port_2_dev_8 fui get vswr
for 6 Sertor command
lhsh 000100/port_0_dev_12
lhsh 000100/port_1_dev_13
lhsh 000100/port_2_dev_14
lhsh 000200/port_0_dev_15
lhsh 000200/port_1_dev_16
lhsh 000200/port_2_dev_17

fui
fui
fui
fui
fui
fui

get
get
get
get
get
get

vswr
vswr
vswr
vswr
vswr
vswr

Main Page

Clear Alarm Refer ALEX Document

Main Page

Check IPRAN Status using EMAS

Main Page

Check Local Status Using EMAS

Main Page

Check Cell ID using EMAS

Main Page

Das könnte Ihnen auch gefallen