Prepared By Abhishek Jain
Prepared By Abhishek Jain
(45007) and Amit Akshantal (45783).
(45007) and Amit Akshantal (45783).
NM
The iManager M2000 V2 system (M2000) is a cThe iManager M2000 V2 system (M2000) is a centralized networkentralized network
management (NM) product
management (NM) product developed by uawei! "s a wirelessdeveloped by uawei! "s a wireless
NM solution# the M2000 per$orms centralized NM to all the
NM solution# the M2000 per$orms centralized NM to all the
wireless products o$ uawei!
wireless products o$ uawei!
This document comprises the overview# system architecture#This document comprises the overview# system architecture#
typical con$iguration# and networking o$ t
This helps you to $amiliarize yoursel$ with%
This helps you to $amiliarize yoursel$ with%
&verview o$ the M2000&verview o$ the M2000
'ystem architecture o$ the M2000'ystem architecture o$ the M2000
TyTypical system con$iguration pical system con$iguration o$ the o$ the M2000M2000
M2000 roduct escription
*hapter + &verview o$ the M2000
*hapter + &verview o$ the M2000
*hapter 2 'ystem "rchitecture o$ the M2000
*hapter 2 'ystem "rchitecture o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter - Networking o$ the M2000
*hapter - Networking o$ the M2000
The iManager M2000 Mobile .lement Management 'ystem (M2000) is a
centralized mobile network management plat$orm developed by uawei
The M2000 can per$orm centralized management on mobile N.s provided by
uawei! These N.s include N.s on the /MT'# 'M# *M"# 1iM"# and core
networks! 3n addition# the M2000 manages the 3 networking devices (uawei
device) used in the mobile network!
.M4
.M4
NM4
NM4
iManaer M000 *N /M M'* 'N * ''N 4 5 +,!AN RNC NodeB -B BSC BTS M M*6 7*6 '8*'*6 1"'N/ima7T' P de%i#e 4answitch 5outer 1M, 2ata #enter n#ti'ns eatresN.4
N.4
'thb'nd inter"a#e NM N'rthb'nd inter"a#eN* itar Messae,ra#e
iManaer M000
M PM *M ,M M /M 6M NB
*M i/eb
NM nter"a#es
NM
1
N.
iManaer M000
N.
N.
NMP
*$!BA
A*
Ⅱ nner inter"a#eN'rthb'nd inter"a#e
'thb'nd inter"a#e
tandard *$!BA inter"a#e *'mplyin &ith the 3-PP !
pp'rtin the manaement '" alarm9 per"'rman#e9 and #'n"irati'n
ile inter"a#e
n#ldin #'n"irati'n "ile inter"a#e9 per"'rman#e "ile inter"a#e9 alarm "ile inter"a#e9 and in%ent'ry "ile inter"a#e
A* alarm streamin inter"a#e pp'rtin real:time alarm
Pr'%idin me#hanism "'r alarm syn#hr'ni;ati'n and "'r dete#tin the #'nne#ti'n stats '" alarm links
NMP inter"a#e
pp'rtin real:time alarm rep'rtin9 <ery '" #rrent alarms9 and heartbeat n'ti"i#ati'n
pp'rtin the NMP%=9 NMP%#9 and NMP%3 pr't'#'ls
MM1 ,ransmissi'n inter"a#e
pp'rtin #'n"irati'n and per"'rman#e manaement
,he iManaer M000 > 'lti'n
9UMTS
NodeB
RNC
SGSN
GGSN
MSC
Server
MG
!"R
CG
9GSM
MSC
BSC
BTS
#C$
!"R
9CDMA
MSC
MSC Server
MG
#%SN
!"R
BSC
BTS
RAC
RA$
TSC
Pr'%idin s'lti'ns "'r the a&ei +M,?-M?*2MA?/iMA@ pr'd#ts
9WiMAX
BS
ASN&G
eatres '" the iManaer M000 >
9
ireless&net'or(&)ased NM solution
Together with the 4MT# the M2000 per$orms centralized maintenance and NM to N.s at the server and client levels!
The M2000 provides the NM' with multiple Northbound inter$aces $or communicating with the NM': thus managing networks at di$$erent levels!
9
Centrali*ed management
The M2000 per$orms centralized &;M $or N.s!
The M2000 supports topology management# centralized con$iguration# centralized per$ormance# centralized $ault# log management# and security management!
+le,i)le net'or( architecture
The M2000 is connected to N.s through the T*<3 protocol!
9
Reasona)le system architecture
The M2000 $eatures a modular design: thus enabling smooth network e=pansion!
,'p'l'y '" the M000 Net&'rk
Area =
Area = Area Area
1M, 1M,
P '%er thernet9
=922N and @.5
*lient Alarm b' Area = Area = *lient Alarm b' *lient = Area Area NM
NM
!em'te terminal M000 ser%er *lient NM #enter P Bearin Net&'rk RNC MG W MSC HLR MG W N'rthb'nd inter"a#e NodeB*hapter + &verview o$ the M2000
*hapter + &verview o$ the M2000
*hapter 2 'ystem "rchitecture o$ the M2000
*hapter 2 'ystem "rchitecture o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter - Networking o$ the M2000
M2000 server software
M2000 client software: providing a graphical ser interface !G"#$% perfor&ing '(M on
&anaged N)s
N) &ediation software: connecting the N)s of the M2000 *2 to the &ediation la+er
Hardware of the M2000
M2000 servers
M2000 clients
,lar& -o.es and networ/ing devices
ystem Ar#hite#tre '" the M000
M000 '"t&are M'dles
NM
er%er s'"t&are
'laris
ybase
M000 ser%er
N mediati'n
s'"t&are =
N mediati'n
s'"t&are
N mediati'n
s'"t&are n
N
=
N
N n
*lient
s'"t&are
Northbound NM' inter$ace *&57" *&57"Physi#al Ar#hite#tre '" the M000
,ypi#al #'n"irati'n '" the M000 system (sinle:ser%er system)
n the #'n"irati'n
'" the sinle:ser%er
system (e#ept the
N40)9 disk arrays
are #'ntained.
Physi#al Ar#hite#tre '" the M000
Physi#al Ar#hite#tre '" the M000
*hapter + &verview o$ the M2000
*hapter + &verview o$ the M2000
*hapter 2 'ystem "rchitecture o$ the M2000
*hapter 2 'ystem "rchitecture o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter - Networking o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
,!+
,!+ 'ystem *on$iguration o$ the M2000
'ystem *on$iguration o$ the M2000
,!2 &verview o$ the 'un 'ervers
,!2 &verview o$ the 'un 'ervers
,!, &verview o$ the isk "rrays
,!, &verview o$ the isk "rrays
,ypi#al *'n"irati'n '" the M000
(inle:er%er ystem)
n Netra 40 n ire >80 n ire 400 *P+ *P+s? =.5 -; *P+s ?=.5 -; 4 *P+s ?=.5 -; 8 *P+s ?=.5 -; 4 *P+s ?=.5 -; 8 *P+s ?=.5 -; = *P+s ?=.5 -; Mem'ry 4 -B 8 -B = -B 3 -B = -B 3 -B 3 -B ard disk =4 -B =4 -B =4 -B2isk array N'ne $ne =40 disk array (==4 -B ?per =40)
,&' =40 disk arrays (==4 -B ?per =40)
A##ess'ries 2>2 !$M?Net&'rk #ard?2A,A 7 tape dri%e?nlish d'#mentati'n $peratin system 'laris =0 2atabase ybase =5.0. Appli#ati'n s'"t&are
*'n"irati'n n ire >80 n ire 400
Nmber '" *P+s 4 8 4 8
=
*l'#k "re<en#y =.5 -; =.5 -; =.5 -; =.5 -; =.5 -;
=.5 -;
Mem'ry 8 -B = -B 3 -B = -B 3 -B
3 -B
ard disk =4-B =4 -B
2isk array ,&' =40 disk arrays (==4 -B ?per =40)
,&' =40 disk arrays (==4 -B ?per =40)
A##ess'ries 2>2 !$M?2A,A 7 tape dri%e?nlish d'#mentati'n $peratin system 'laris =0?nlish d'#mentati'n
2atabase ybase =5.0.
Appli#ati'n s'"t&are M000 er%er appli#ati'n s'"t&are 2isk manaement
s'"t&are
n *lster
,ypi#al *'n"irati'n '" the M000 (A
ystem)
*'n"irati'n n Netra 40 n ire >80 n ire 400
Nmber '" *P+s 8 8
*l'#k "re<en#y =.5 -; =.5 -; =.5 -;
Mem'ry 4 -B 3-B 3-B
ard disk =4 -B =4 -B =4 -B
2isk array N'ne $ne =40 disk array
(==4 -B ?per =40)
$ne =40 disk arrays (==4 -B ?per =40)
A##ess'ries 2>2 !$M?Net&'rk #ard?2A,A 7 tape dri%e?nlish d'#mentati'n $peratin system 'laris =0? nlish d'#mentati'n
2atabase ybase =5.0.
Appli#ati'n s'"t&are
M000 er%er appli#ati'n s'"t&are
2isk manaement s'"t&are
>*
,ypi#al *'n"irati'n '" the M000 (1
ystem)
tem !e#'mmended *'n"irati'n
*P+ Pentim .8 -; 'r "aster
Mem'ry 5= MB
ard disk 80 -B
,ypi#al *'n"irati'n '" the M000 *lient
tem !e#'mmended *'n"irati'n
A##ess'ry 2>2!/?22?net&'rk #ard?adi' #ard?s'nd b'?=7CC 1*2 m'nit'r
$peratin system
/ind'&s @P Pr'"essi'nal P0 (*hinese %ersi'n) 'r later
Appli#ati'n s'"t&are
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
,!+ 'ystem *on$iguration o$ the M2000
,!+ 'ystem *on$iguration o$ the M2000
,!2 &verview o$ the 'un 'ervers
,!2 &verview o$ the 'un 'ervers
,!, &verview o$ the isk "rrays
,!, &verview o$ the isk "rrays
N ,ype Nmber '" <i%alent Ns
!N*DN'deB 50 #ells E =e>uivalent N.
M* er%er
M* (M'bile er%i#e &it#hin
*enter) =
-N (er%in -P! pp'rt
N'de)
M-/ (Media ate&ay) =.4 1! ('me 1'#ati'n !eister) 0.= --N (-ate&ay -P! pp'rt
N'de) 0.=
*- (*harin ate&ay) 0.04 / (nter/'rkin "n#ti'n) 0.04 - (inalin ate&ay) 0.5
Appli#ati'n #enari' '" the er%er
'un 6ire .-?00 (@ */s) 00 e>uivalent N.s 'un 6ire V@?0 (@ */s) =0 e>uivalent N.s 5 'un 6ire .-?00 (- */s) ==0 e>uivalent N.s 4 'un 6ire V@?0 (-*/s) 85 e>uivalent N.s 3 'un 6ire V@?0 (2 */s) 45 e>uivalent N.s 'un Netra 2-0 (2 */s) =5 e>uivalent N.s = er%er ,ype *apability N'.
*hapter , Typical 'ystem *on$iguration o$ the M2000
*hapter , Typical 'ystem *on$iguration o$ the M2000
,!+ 'ystem *on$iguration o$ the M2000
,!+ 'ystem *on$iguration o$ the M2000
,!2 &verview o$ the 'un 'ervers
,!2 &verview o$ the 'un 'ervers
,!,
Developed independently by Huawei Technologie
Co!" #td" the iManager M2000 $2 function a
%MS in the Huawei wirele networ& olution! The
M2000 $2 can acce a whole erie of product
developed by Huawei and perfor' centrali(ed
'anage'ent on the'!
Thi lide introduce the baic operation of on the
M2000 client!
,fter learning this corse +o will have a -asic /nowledge of:
,fter learning this corse +o will have a -asic /nowledge of:
Baic operation on the M2000 client!
Baic operation on the M2000 client!
)peration related to 'onitoring 'anage'ent" topology 'anage'ent" ecurity
)peration related to 'onitoring 'anage'ent" topology 'anage'ent" ecurity
'anage'ent" log 'anage'ent" fault
'anage'ent" log 'anage'ent" fault
'anage'ent" perfor'ance 'anage'ent"
'anage'ent" perfor'ance 'anage'ent"
oftware 'anage'ent" data 'anage'ent" and
iManager M2000 S+ste& 1escription
iManager M2000 S+ste& 1escription
iManager M2000 ,d&inistrator Gide
iManager M2000 ,d&inistrator Gide
iManager M2000 Co&&issioning Gide
iManager M2000 Co&&issioning Gide
Reference
Chapter Logging #n to the M2000
Chapter Logging #n to the M2000 Client
Client
C
C
hapter Logging #n to the M2000 Client
hapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
Chapter < 1ata Manage&ent
Chapter 0 Configration Manage&ent
1'in n t' the M000 *lient
1'in in t' the
M000 ser%er
1'in 't
itin
+pradin the
s'"t&are 'n the #lient
At'mati#ally
1'in n t'
1'in n t'
the M000
the M000
$ther 'perati'ns
The diagra' on the left lit
o'e baic operation involved
in M2000 client login!
1'in n t' the M000 er%er
To log in to the M2000 erver" chooe
Start
*
,ll progra&s
*
iManager M2000 client
*
M2000 client
!
Type the uer na'e and paword
in the correponding field!
Type the +, addre of the M2000
erver!
N'teF
,he initial ser name is admin
and the pass&'rd is nll.
,he ser pass&'rd is sa%ed 'n
the M000 ser%er. $nly &hen the
ser%er is initially installed9 the
pass&'rd is nll.
1'in n t' the M000 er%er
=Main interface of the M2000 client=
Navigation tree +nfor'ation diplay Menu bar Statu bar Tool bar Topology view
1'in $t $"" the M000 *lient
To log out off the M2000 client" chooe S+ste& *Logot!
Note- #ogging out off the M2000 client doe not 'ean the application running on the M2000 client are ter'inated!
itin
To e.it the M2000 client" chooe S+ste& *).it!
Note: ).iting the
M2000 client
&eans the
applications
rnning on the
M2000 client are
ter&inated>
"pgrading the Software on the M2000 Client ,to&aticall+
To upgrade the oftware on the M2000 client auto'atically" perfor' the following tep-Step /- Start the M2000 client!
Step 2- #og in to the M2000 erver!
fter you log in to the M2000 erver" the Confir'ation dialog bo. i diplayed" clic& ?es!
,rere1uiite-The M2000 can be auto'atically
and correctly upgraded only
when- The verion of the oftware on
the M2000 client and on the M2000
erver are of the a'e verion
e1uence!
The verion of the oftware on the
M2000 erver i higher than that on
the M2000 client!
"pgrading the Software on the M2000 Client ,to&aticall+
$ther $perati'ns
Syte' Setting Diplay4Hide4Cuto'i(e Toolbar Region Setting Metrology Setting #oc& Ter'inal Change ,aword ,ro.y Service Setting #MT ,ro'pt Setting!ei'n ettins
Nu'ber tab page
Ti'e tab page
Date tab page
$%er%ie& '" $ther *'mm'n $perati'ns
S+ste& secrit+ settings
Single5uer 'ode- indicate the yte' tatu
during the 'aintenance! The ingle5uer 'ode allow
only one uer to log in to the client and et up
eion!
Multi5uer 'ode- indicate the yte' tatu when
the yte' i functional! The 'ulti5uer 'ode allow
everal uer to log in to the client at the a'e ti'e!
$%er%ie& '" $ther *'mm'n $perati'ns
$%er%ie& '" $ther *'mm'n $perati'ns
Download N% 'atch file to the M2000 client
6hen the verion of an N% on the M2000
client i different fro' that on the M2000
erver" download the N% 'atch file to the
M2000 client" a hown on the right!
+f the file related to the new verion of the
N% are not available" the yte' diplay a
'eage" indicating that the yte' cannot
perfor' the upgrade operation!
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
The M2000 networ& 'onitoring 'onitor the operational tatu of the M2000! 7or intance"
the 'onitoring 'anage'ent 'onitor the tatu of hard di&" databae" eion" or ervice!
The M2000 'onitoring 'anage'ent involve the following
operation-9 Setting the erver threhold
9 Monitoring the perfor'ance tatu of the erver
9 Monitoring the hard di& tatu of the erver
9 Monitoring the databae tatu of the erver
9 Monitoring the databae erving tatu
9 Monitoring the proce tatu of the erver
Setting the Server 4hreshold
Step /- Set the hard di& threhold!
Setting the Server 4hreshold
Step 2- Set the databae threhold!
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
The topology 'anage'ent i ued for contructing and 'anaging the topology tructure of
The topology 'anage'ent i ued for contructing and 'anaging the topology tructure of
the entire networ&! +n thi way" the networ&ing topology and the operational tatu of the
the entire networ&! +n thi way" the networ&ing topology and the operational tatu of the
entire networ& are diplay
entire networ& are diplay
ed clearly!
ed clearly!
9
9
Creating phyical ubnet
Creating phyical ubnet
9
9
Creating phyical N%
Creating phyical N%
9
9
Managing SNM, para'eter te'plate
Managing SNM, para'eter te'plate
9
9
Monitoring N%
Monitoring N%
9
9
d8uting the networ& topology
d8uting the networ& topology
9
9
d8uting the diplay of the topology view
d8uting the diplay of the topology view
9
9
,rinting the topology view
,rinting the topology view
,'p'l'y Manaement
*reatin Physi#al bnets
*reatin Physi#al bnets
To cr
To cr
eate phyical
eate phyical
ubnet" perfor' the following tep-
ubnet" perfor' the following
tep-Step /- Right5clic& the topology view
Step /- Right5clic& the topology view
and chooe
and chooe
Create h+sical S-net
Create h+sical S-net
fro' the
fro' the
hortcut 'enu!
hortcut 'enu!
Set bac&ground
Set bac&ground
Create phyical ubnet
Create phyical ubnet
Create topological ob8ect
Create topological ob8ect
The
The
Create 4opo '-Aect
Create 4opo '-Aect
option i ued to create
option i ued to create
phyical N%" virtual N%" +,
phyical N%" virtual N%" +,
device" virtual lin&" and
device" virtual lin&" and
phyical lin&!
*reatin Physi#al bnets
*reatin Physi#al bnets
Step 2- Set the
Step 2- Set the
file erver!
file erver!
The file erver i ued for the file t
The file erver i ued for the file t
ranfer between the M2000 and the N%! n N% i ued a the
ranfer between the M2000 and the N%! n N% i ued a the
file erver to et up connection
file erver to et up connection
between the M2000 and other N%! +n
between the M2000 and other N%! +n
thi way"
thi way"
the proble' that
the proble' that
the M2000 cannot et up
Creating h+sical N)s
Create a ingle phyical N%!
Creating h+sical N)s
Create 'ultiple phyical N%!
7or intance" the
Search NodeB
function enable you to find the
NodeB that belong to the RNC
on the topology view! Si'ilarly"
you can et
Search #MS'"4
to
create 'ultiple phyical N%
i'ultaneouly!
M'nit'rin Ns
M'nit'rin Ns
Set N% reconnection tatu!
6hen the M2000 erver i diconnected
fro' N%" et the M2000 to re5connect N%!
The N% reconnection ha two
tatue-
7orbidden connection
6hen the M2000 erver i diconnected
fro' an N%" the M2000 will not atte'pt to
connect the N%!
,er'itted connection
6hen the M2000 erver i diconnected
fro' an N%" the M2000 atte'pt to re5
connect the N%! By default" a new N% i in
per'itted connection tatu!
Diconnection
icon-M'nit'rin Ns
,dAsting Networ/ 4opolog+,dAsting Networ/ 4opolog+ 1ispla+rinting
4opolog+ *iew
9oo' in
9oo' out
,artially (oo' in
Retore
%le'ent diplay
$iew
,rint
Search
Save
,dAsting Networ/ 4opolog+,dAsting Networ/ 4opolog+ 1ispla+rinting
4opolog+ *iew
,dAsting Networ/ 4opolog+,dAsting Networ/ 4opolog+ 1ispla+rinting
4opolog+ *iew
,dAsting Networ/ 4opolog+,dAsting Networ/ 4opolog+
1ispla+rinting 4opolog+ *iew
Search or 'odify the phyical lin&!
To earch for phyical lin&"
double5clic& a phyical lin& or a
phyical lin& et on the topology
view!
+n the diplayed dialog bo."
right5clic& a lin& and chooe
#in& Brower!
,dAsting Networ/ 4opolog+,dAsting Networ/ 4opolog+
1ispla+rinting 4opolog+ *iew
,dAsting Networ/ 4opolog+,dAsting Networ/ 4opolog+
1ispla+rinting 4opolog+ *iew
,dAsting Networ/ 4opolog+,dAsting Networ/ 4opolog+ 1ispla+rinting
4opolog+ *iew
Set the topology view to tart the ubnet!
The ubnet view refer to that
diplayed on the client after
the topology view i diplayed!
+f you do not plan to et the
topology view 'anually" the
default view of the ubnet
tarted by the topology view i
the root ubnet view!
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
The M2000 ecurity 'anage'ent involve the following
operation-9 Configuring the ecurity 'anage'ent
9 Managing )M uer
9 Managing N% uer
9 Managing )M and N% uer
9 Setting 7T,S para'eter
nter"a#e '" e#rity Manaement
Set the N% type to be
diplayed!
Refreh the ecurity
'anage'ent interface!
Manain $M +sers
Manain $M +sers
uthori(ing )M :er ;roup
igning privilege to )M uer group
igning new device right to )M uer
group
igning MM# co''and right to
)M uer group
Three default uer group are available on the
M2000 client! They are d'initrator group"
;uet group" and )perator group!
The d'initrator group ha the highet
privilege! <ou cannot 'odify or copy the
privilege of the d'initrator group! <ou can"
however" authori(e the ;uet group and the
)perator group!
Manain $M +sers
Synchroni(e )M uer data
dd )M uer to )M uer group
Bind )M uer private right
ign MM# co''and right to )M
uer
Change paword
Note that each N% i aigned with the correponding MM#
co''and right! 6hen a new N% i added" you need to re5aign
the MM# co''and right for each uer in the )M uer group!
Manain $M +sers
Set rule for N% type right!
<ou can et the rule for N%
type right in a te'plate! fter
etting the te'plate" all the N%
added have the right inherited
fro' thi te'plate!
Manain N +sers
fter the )M uer i
bound with a real N%" you
can create at the N% ide a
uer with the a'e na'e a
the )M uer! Thi uer i
called N% uer! The N%
uer log in to the N%
through the #MT!
M'nit'rin $M +sers and N +sers
Monitor the )M :er!
Monitor the operation of )M uer who are
now in eion tatu!
6hen the M2000 erver retart or the networ&
i diconnected and retored" clic&
Refresh
to
refreh the eion 'onitor table!
M'nit'rin $M +sers and N +sers
Monitor the eion of the )M uer on the #MT!
Note that thi function i applicable only to N% in
the 6CDM networ& and upport only the #MT
uer!
M'nit'rin $M +sers and N +sers
Set the tatu for a non5default N% uer!
By etting the tatu" the non5default
N% uer= login and operation of the
MM# co''and on the #MT can be
controlled! Non5default N% uer refer
to the N% local uer e.cluding the
ad'in and guet uer!
The tatue of non5default N% uer
can be 'anageable and loc&!
M'nit'rin $M +sers and N +sers
M'nit'rin $M +sers and N +sers
M'nit'rin $M +sers and N +sers
:nloc&ing )M uer!
+f the ti'e that a uer
enter wrong paword at
a ti'e e.ceed the
'a.i'u' atte'pt" the
)M uer i loc&ed for a
period! Right5clic& the
uer and chooe
"nloc/
"ser
fro' the hortcut
'enu to unloc& the uer!
M'nit'rin $M +sers and N +sers
ettin ,P Parameters
%ncryption 'ode- elf5adaptation 'ode" SS# encryption 'ode" and plain 'ode!
Supported 'ode- refer to the 7T,S connection 'ode" 'ainly including active 'ode
and paive 'ode!
Tran'iion 'ode- refer to the 'ode in which the 7T,S tranfer file! The
tran'iion 'ode can be in SC++ 'ode or in te.t 'ode!
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
Type of log
M2000 Log Manage&ent
,ypes '"
l's
'peration log
Secrit+
log
S+ste& log
N) operation
log
N)
secrit+
log
Record all the i'portant operation perfor'ed by )M uer!
Record ecurity event occurred in the yte'" uch a logging in to the M2000" 'odifying right for )M uer group" or adding )M uer!
Record ignificant event occurred in the yte'!
Record all the
i'portant operation perfor'ed by N% uer
Record ecurity event occurred to N%!
#og te'plate
M2000 Log Manage&ent
=
#og tatitic te'plate
#og 1uery te'plate
Notes:
Saved on the erver bac&ground the content of a te'plate are aociated with uer! 7or intance" the te'plate created by uer can be een by uer only!
The na'e of log te'plate that are of the a'e type and belong to the a'e uer cannot be duplicate! +f the na'e of
log te'plate are duplicate" the yte' cannot ave the te'plate!
'a.i'u' of >0 character are allowed for the na'e of the te'plate! The following character are not allowed- ?@A EFGIJKL-"OPQ
*=
The te'plate infor'ation node doe not upport dyna'ic refreh! +f uer log in to two ter'inal at the a'e ti'e and delete or 'odify te'plate / on ter'inal /" the deletion or 'odification cannot be perfor'ed on ter'inal 2
auto'atically! The 'anual refreh provided by the yte'" however" enable you to refreh the te'plate infor'ation 'anually!
)peration involved in the M2000 log 'anage'ent are a
follow-9 Uuerying log
9 Collecting tatitic on log
9 Managing log te'plate
er+ing Logs
Uuerying operation log Uuerying yte' log
Uuerying ecurity log
Uuerying N% operation log Uuerying N%
Collecting Statistics on Logs
Collecting tatitic on operation log
Collecting tatitic on yte' log Collecting tatitic on ecurity log
Collecting tatitic on N% operation log Collecting tatitic on N%
Manain 1' ,emplates
Saving a te'plate
Modifying a te'plate
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
7unction :
The M2000 report" 'anage" and analy(e N% alar' in a centrali(ed 'anner! The M2000 collect N% alar' to the M2000 and diplay different audio and video device alar' for the 'aintenance peronnel! +n addition" the M2000 notifie the 'aintenance peronnel of device alar' by hort 'eage or e'ail at the ti'e when the alar' i
generated!
)peration-The following operation and analyi can be perfor'ed on N% alar' at the M2000 ide! 9 Manual retore
9 7iltering
9 Severity redefinition 9 lar' relevance
+n thi way" the M2000 can perfor' centrali(ed analyi and proceing on the device alar' generated in the current networ&!
M2000 8alt Manage&ent
Alarm
type
alt
Manaement
Alarm
#ate'ry
Alarm
se%erity
Critical+ndicate that the device or the reource cannot be ued co'pletely and need to be retored i''ediately! MaAor
+ndicate that the 1uality of the device or the reource i everely da'aged! Corrective 'eaure hould be ta&en i''ediately!
Minor
+ndicate that the 1uality of the device or the reource i lightly affected!
ro&pt
+ndicate that the 1uality of the device or the reource 'ay probably be affected!
)vent alar&
Refer to the notification generated when the yte' detect the event occurred!
8alt alar&
Refer to the notification generated when the yte' detect the fault occurred!
lar' can be related to the following
ite'-,ower upply yte'
%nviron'ent yte' Signaling yte' Relay yte' Hardware yte' Software yte' )perating yte' Teleco''unication yte' Service 1uality 7ault handling +nternal alar'
Saving alar'
+n the alar' databae" four table are available for aving alar'! The four table are a
follow-9 tblVcurVal'- ave currently generated alar'!
9 tblVhiVal'- ave alar' generated in the pat!
9 tblVevent- ave the event alar'!
9 tblV'a&Val'- ave the hielded alar'!
By default" the alar' ervice detect whether the nu'ber of alar' in the alar' table reache to the upper threhold every W3 econd after it i tarted!
The upper threhold for each alar' table i a follow-9 tblVcurVal'- /00" 000
9 tblVhiVal'- 2 'illion and can be 'odified through the M2000 client! 9 tblVevent- 200 'illion and can be 'odified through the M2000 client! 9 tblV'a&Val'- 200" 000
Mechanis& for rocessing ,lar& 4a-le
'verflow
6hen the alar' recorded in the alar' table e.ceed the threhold" different alar' table have different
'echani' to proce alar' table overflow!
9 tblVcurVal'- ort the alar' by alar' generation ti'e in e1uence and forcibly change firt ten thouand
unac&nowledged and cleared alar' to the tblVhiVal'! +f the alar' table till ha the proble' of overflow" 'ove the earliet unac&nowleged and uncleared alar' to the tblVhiVal'!
9 tblVhiVal'- ort the alar' by alar' generation ti'e in e1uence and docu'ent the 20 percent of the earliet alar'! Then" the yte' delete thee earliet alar' auto'atically!
9 tblVevent- ort the alar' by alar' generation ti'e in e1uence and docu'ent the 20 percent of the earliet alar'! Then" the yte' delete thee earliet alar' auto'atically!
9 tblV'a&Val'- delete the earliet /00"000 alar' fro' the alar' table!
Mechanis& for rocessing ,lar& 4a-le
'verflow
$perati'ns n%'l%ed in the M000 alt Manaement
Browing current fault alar' Browing event alar' Uuerying current fault alar' Uuerying event alar' Uuerying hitory fault alar' Uuerying hielded alar' Collecting tatitic on alar'
$perati'ns n%'l%ed in the M000 alt Manaement
Browing current fault alar'
Browing event alar' Setting alar'
$perati'ns n%'l%ed in the
M000 alt Manaement
Set alar' ervice!
Setting re'ote alar' notification Setting para'eter of re'ote alar' notification c&nowledging alar' Redefining alar' everity Setting condition for alar' filtering Setting alar' correlation analyi
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
Meaure'ent i a proce during which the value of an attribute for an N% entity Iincluding logical entityJ in a period i ac1uired!
Category of perfor'ance 'eaure'ent counter
9 Syte' counter- a &ind of a default counter defined in the N%! Syte' counter are categori(ed into co''on counter and e.tended counter!
5 Co''on counter- By default" the co''on counter are in the 'eaure'ent tate! :er cannot ignore any 'eaure'ent on co''on counter!
5 %.tended counter- By default" the e.tended counter are in the non5'eaure'ent tate! Before perfor'ing any 'eaure'ent on e.tended counter" you need to activate the' firt! <ou can enable or diable the 'eaure'ent on e.tended counter!
9 Cuto' counter- refer to the counter that are defined on the M2000 client by uer! The principle for cuto'i(ing counter i to perfor' arith'etic operation on the default counter" including co''on counter and e.tended
counter" in the yte'! +n thi way" cuto' counter are elf5defined!
The 'a.i'u' aving day for the reult whoe 'eaure'ent period i X 'inute or /X 'inute are Y and repreented by the para'eter 'a.RTReultSavingDay!
The 'a.i'u' aving day for the reult whoe 'eaure'ent period i 30 'inute" Z0 'inute" or / day are 30 and repreented by the para'eter 'a.ReultSavingDay!
The M2000 chec& the reult whoe period i 30 'inute" Z0 'inute" or / day on a fi.ed ti'e 03-2X a!'! each day! Thi i repreented by the para'eter capacityControlTi'e! The M2000 delete the data aved for over 30 day! The M2000 chec& the reult whoe period i X 'inute or /X 'inute on a fi.ed ti'e 0>-3X a!'! each day! Thi i
repreented by the para'eter capacityControlTi'e [ Y0 'inute! The M2000 delete the data aved for over Y day! The para'eter decribed previouly are decribed in the file 4e.port4ho'e4o'c4var4etc4conf4p'vc!.'l!
Measrement ettins
Measrement ettins
)pen the )pen the Measre&ent Measre&ent Settings Settings window! window!ettin Measrement
ettin Measrement
Two Two navigation navigation 'ode 'ode Change of Change of function et function et Change of Change of function function ubet ubet ,eriod for the,eriod for the elected function elected function ubet ubet Counter +D Counter +D Several Several N% N%
)b8ect
)b8ect
pplying the pplying the 'eaure'ent 'eaure'entM'nit'rin N Per"'rman#e
M'nit'rin N Per"'rman#e
Synchroni(ing 'eaure'ent reult of N% Synchroni(ing 'eaure'ent reult of N%
Uuerying 'iing 'eaure'ent reult of N% Uuerying 'iing 'eaure'ent reult of N%
Meaure'ent 'anage'ent Meaure'ent 'anage'ent
M'nit'rin N Per"'rman#e
er+ing erfor&ance Measre&ent Reslts !#$
Uuery te'plate
Create a 1uery
er+ing erfor&ance Measre&ent Reslts !##$
Setting an ob8ect Setting a counter)ther etting" uch a 1uerying the buy5hour reult" 'eaure'ent period" orting" and filter
Managing Measre&ent '-Aects
+'porting the infor'ation about 'eaure'ent
ob8ect
%.porting the infor'ation about 'eaure'ent ob8ect
Managing Measre&ent '-Aects
ctivate4Supend 'eaure'ent ta&!
ctivating 'eaure'ent ta& Supending 'eaure'ent ta&
Manain +ser:2e"ined *'nters
Creating uer5defined counter Modifying uer5 defined counter+'porting uer5defined
counter
%.porting uer5defined counterManain *'nter ,hresh'ld
Setting the counter
threhold Modifying the counter threhold Setting the tatu of the counter threhold
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
The oftware 'anage'ent involve the following operation-9 Managing the oftware and file
9 :pgrading N% oftware and patche 9 Managing RN #icene
9 Uuerying $erion +nfor'ation on Software +ntalled on the Server
The file erver i defined a
follow-9 +f the M2000 plan to tranfer file to N% B" the M2000 upload file to the directory preet on N% that upport the 7T, function! Then" N% B download the file fro' the preet directory fro' N% ! +n uch a ituation" N% i defined a the file erver of N% B!
9 N% can erver a the file erver for itelf!
9 Not all N% can regard other N% a their file erver!
9 6hen the M2000 erver erve a the file erver for N%" you can infer that the M2000 erver can directly tranfer file with N%!
pplication cenario
9 6hen the M2000 can erve only a ftp client becaue of li'itation i'poed by the firewall" N% can regard itelf or other N% a file erver!
9 +n cae the NodeB can erve only a the 7T, client and the networ& bandwidth between the M2000 and the RNC hould be aved" the RNC can ta&e place of the NodeB to be the file erver of the NodeB!
Manain '"t&are and iles
B
M000:er%er
6ile
A
Manain '"t&are and iles
Browing the file infor'ation on the erver! The file
infor'ation include oftware" patche" licene" data" and
Manain '"t&are and iles
Tranferring filefro' the client to the erver
Tranferring file fro' the erver to the client Tranferring file fro' N% to the erver Tranferring file fro' the erver to N%
The oftware 'anage'ent function enable you to upgrade the oftware and patche of the following N%-9 RNC 9 NodeB 9 S;SN 9 ;;SN 9 MSC erver 9 M;6 9 SN5;6
"pgrading N) Software and atches
Note:
7or detail about how to upgrade the RNC" the NodeB" and their correponding patche" refer to the upgrade guide!
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
<ou can bac& up the NM data in two way- periodic bac&up and 'anual bac&up!
<ou can bac& up the NM data through the full bac&up and the incre'ental bac&up! The following give the difference between the full bac&up and the incre'ental
bac&up-9 %ach ti'e when a full bac&up i perfor'ed" the M2000 re'ove all the previou file related to full bac&up and incre'ental bac&up on the erver and ave one and only the latet co'preed full bac&up file! The file of full bac&up i na'ed in the following way- all5current ti'e" uch a" all-20060106103055.tar.gz.
9 %ach ti'e when an incre'ental bac&up i perfor'ed" a new bac&up file i generated! The incre'ental bac&up i on the bai of previou bac&up data that can be a full bac&up or an incre'ental bac&up! The file of an incre'ental bac&up i na'ed in the following way- inc5current ti'e" uch a" inc-20060106103055.tar.gz.
The NM data to be bac&ed up refer to the data contained the following file-9 4e.port4ho'e4o'c4var4
9 4e.port4ho'e4y'4
The bac&up file of the NM data are aved in the directory of 4e.port4ho'e4bac&up4o'c4 on the M2000 erver!
N% data bac&up- The data 'anage'ent provided by the M2000 enable you to bac& up the configuration file of all N% 'anaged by the M2000 and the file that change dyna'ically during the operation!
<ou can bac& up the N% data in two way- the periodic bac&up and the 'anual bac&up! The yte' can generate one bac&up file after you perfor' the bac&up ta& once!
9 The 'a.i'u' nu'ber of N% bac&up file tored on the erver i deter'ined by the M2000 configuration file! t preent" the M2000 erver can tore up to even bac&up file for each N%! 6hen 'ore than even bac&up file are
generated for an N%" the M2000 erver tore only the latet even bac&up file for thi N%! Meanwhile" the M2000 erver refrehe the bac&up file lit!
9 The bac&up file of N% data are aved to the path- M2000 erver4e.port4ho'e4y'4ftproot4N% type! Ta&e the RNC for e.a'ple" 4data type4N% 7DN!
6hen the M2000 yte' fail" you can run the diagnotic tool to collect all the related diagnotic infor'ation fro' the M2000 erver and client through the 7T, protocol! By uing thi infor'ation" you can locate fault!
The collected infor'ation i a
follow-9 Trace files on the client, for example, Client_DebugTrace.
9 \ava virtual 'achine thread tac& and loc& tate of the client" for e.a'ple" Client_ThreadStackDump.txt ! 9 Trace file on the erver" for e.a'ple" iMAP.root.trace Ito tore the current trace
fileJ,imap_stacks.2007020.!702"7.trace Ito tore hitory trace file before the currently collected NM log fileJ!
9 Core file on the erver" for e.a'ple" core.imaps#cd.0.2!22!.!!70$2%!$%.stack .
9 N% alar' ynchroni(ation nu'ber" for e.a'ple" &MS'nc(o.
9 The ptac& file" for e.a'ple" imap_stacks.20070207.!))$!7.trace.
9 +nfor'ation of the Sybae" for e.a'ple" S'baseCon*ig.+ip , S'base,ersion.+ip , S-/og.2007020.!7!0%0.+ip .
'verview of 1ata Manage&ent: NM Log
1ata
By default" the collected file are aved in M2000 clientKiManagerM2000ClientKdiagnoiKcollected file! <ou can change the ave path!
'verview of 1ata Manage&ent: NM Log
1ata
2ata Manaement
Manage'ent
of erver data Manage'ent of N% data
2ata Manaement
N% data 'anage'ent Refrehing N% bac&up data Retoring N% bac&up dataBac&ing
up N%
data
'tep +
Step 2- Set the 7T, erver!
9 %nter the +, addre of M2000 erver! 9 %nter the port nu'ber!
9 %nter the 7T, uer na'e and paword ued to log in to the target erver! Step 3- Select infor'ation to be collected!
9 +f you plan to collect trace file on the client" trace file on the erver" core file on the erver" or trace file on the local 'aintenance tation" you hould enter Start 4i&e and)nd 4i&e to collect the infor'ation within the pecified ti'e range!
9 +f you plan to collect alar' diagnotic data of the N%" enter the na'e of the N% whoe alar' diagnotic data you want collect inN) Na&e!
Step >- Set the folder for aving the diagnotic infor'ation!
The collected file are aved under the M2000 client intallation
directory-KiManagerM2000ClientKdiagnoiKcollected file! <ou can change the directory for aving collected file! Step X- Clic& Collect to collect the diagnotic infor'ation!
9 +f you clic& Stop when the diagnotic tool i collecting infor'ation fro' a client" you are not allowed to top the progre of collecting infor'ation fro' the client!
9 +f you clic& Stop when the diagnotic tool i collecting infor'ation fro' the M2000 erver" you are not allowed to get any diagnotic infor'ation about the erver!
Chapter Logging #n to the M2000 Client
Chapter 2 Networ/ Monitoring
Chapter 3 4opolog+ Manage&ent
Chapter 5 Secrit+ Manage&ent
Chapter 6 Log Manage&ent
Chapter 7 8alt Manage&ent
Chapter 9 erfor&ance Manage&ent
Chapter ; Software Manage&ent
Chapter < 1ata Manage&ent
The operation involved in the configuration 'anage'ent vary with different product! 7or detail about the operation involved in the configuration 'anage'ent" refer to the iManager M2000 Operator Gi!e! Thi part only illutrate how to tart the #MT!
This document mainly describes the common M2000
maintenance operations# including the M2000 operation
commands and the 'ybase operation commands!
This helps you to $amiliarize yoursel$ with%
M2000 common
operations
and common logs M2000 common maintenance commands
M2000 "dministrator uide
M2000 'o$tware 3nstallation uide
&M*"to'tar /ser Manual
!e"eren#es
*hapter = 'laris Maintenan#e *'mmands
*hapter = 'laris Maintenan#e *'mmands
*hapter ybase Maintenan#e *'mmands
*hapter 3 M000 Maintenan#e *'mmands
*hapter 4 M000 1's
*hapter 5 M000 1' *'lle#ti'n ,''l and ealth
*he#k ,''l
'laris Maintenan#e *'mmands
*'mmand
2es#ripti'n
i$con$ig Aa
isplay the 3 address
ping
Test i$ a 3 or host is reachable
netstat Aan
isplay the ports status o$ server
netstat Arn
isplay the routes o$ server
d$ 8k
isplay the amount o$ disk space
du Ak
isplay the space occupied by $iles and directory
prstat
isplay the */ and memory occupied by process
*hapter = 'laris Maintenan#e *'mmands
*hapter ybase Maintenan#e *'mmands
*hapter ybase Maintenan#e *'mmands
*hapter 3 M000 Maintenan#e *'mmands
*hapter 4 M000 1's
*hapter 5 M000 1' *'lle#ti'n ,''l and ealth
*he#k ,''l
*'mmands
2es#ripti'n
showserver
isplay the status o$ 'ybase database server
is>l
'tart 'B4 script e=ecution tool
select CCversion
isplay the 'ybase version
spDhelpdb
isplay the status o$ 'ybase database
*hapter = 'laris Maintenan#e *'mmands
*hapter ybase Maintenan#e *'mmands
*hapter 3 M000 Maintenan#e *'mmands
*hapter 3 M000 Maintenan#e *'mmands
*hapter 4 M000 1's
*hapter 5 M000 1' *'lle#ti'n ,''l and ealth
*he#k ,''l
M000 Maintenan#e *'mmands
*'mmands
2es#ripti'n
startDsvc 'tarting the entire M2000 system# including the system process and the service process (This command is not applicable to the " system!)
stopDsvc 'topping the service process o$ the M2000 network management system (This command is not applicable to the " system!)
killDsvc 6orcibly stopping the process o$ the M2000 network management system svcDadm Managing M2000 services# such as starting# stopping# and >uerying services displayVersion isplay version o$ M2000 and installed mediation
scswitch Managing the system resource o$ " system# such as starting<stop M2000# start<stop 'ybase# >uery M2000<'ybase
startDdaem 'tarting the M2000 system daemon process (This command is not applicable to the " system!)
stopDdaem 'tarting the M2000 system daemon process (This command is not applicable to the " system!)
*hapter = 'laris Maintenan#e *'mmands
*hapter ybase Maintenan#e *'mmands
*hapter 3 M000 Maintenan#e *'mmands
*hapter 4 M000 1's
*hapter 4 M000 1's
*hapter 5 M000 1' *'lle#ti'n ,''l and ealth
*he#k ,''l
'olaris 4og
'ybase 4og
M2000 'erver 4og
M2000 *lient 4og
*ore 6ile
"pplication 'cenarios
"pplication 'cenarios
9
9 /se the message log to $amiliarize yoursel$ with the starting and stopping process o$ the system!/se the message log to $amiliarize yoursel$ with the starting and stopping process o$ the system!
9
9 The hardware or other devices incur $aults# such as the disk light is abnormal or the */ and the memory cannot be $ound!The hardware or other devices incur $aults# such as the disk light is abnormal or the */ and the memory cannot be $ound!
7rie$ 3ntroduction o$ the 4og
7rie$ 3ntroduction o$ the 4og
9
9 The log e=ists under theThe log e=ists under the %ar?adm?messaes %ar?adm?messaesdirectory!directory!
9
9 The log records the in$ormation about the 'ybase starting and stopping process# the operating status o$ the hardware and so$tware# and theThe log records the in$ormation about the 'ybase starting and stopping process# the operating status o$ the hardware and so$tware# and the
main error in$ormation!
main error in$ormation!
9
9 /nder the <var<adm< directory# there are messages# messages!0# messages!+# messages!2 # and messages!,! 1here messages saves the/nder the <var<adm< directory# there are messages# messages!0# messages!+# messages!2 # and messages!,! 1here messages saves the
latest logs! &ther message $iles are cyclically recovered!
latest logs! &ther message $iles are cyclically recovered!
# ls -al /var/adm/messages*
# ls -al /var/adm/messages*
-rw-r--r--rw-r--r-- - 1 1 root root root root 31191 31191 De! De! " " 1$ 1$ messagesmessages
-rw-r--r--rw-r--r-- - 1 1 root root root root "%& "%& 'ov 'ov 19 19 1($3& 1($3& messages) messages)
-rw-r--r--rw-r--r-- - 1 1 root root root root 111 111 'ov 'ov 1 1 1$ 1$ messages)1messages)1
-rw-r--r--rw-r--r-- - 1 1 root root root root %%% %%% 'ov 'ov ( ( 1$" 1$" messages) messages)
-rw-r--r--rw-r--r-- - 1 1 root root root root 1"931 1"931 +!t +!t 9 9 1$3 1$3 messages)3messages)3
&btaining and *hecking the 6iles
&btaining and *hecking the 6iles
9
9 Eou can download the message log to the local computer through 6T and open it in !t=t $ormat!Eou can download the message log to the local computer through 6T and open it in !t=t $ormat!
9
9 Eou can check the $iles through the uni= $iles such as more and cat!Eou can check the $iles through the uni= $iles such as more and cat!