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!