c04 Bts3812e-Bts3812a-Bts3812ae v100r013c00spc320 Upgrade Guide (Lmt-Based)

HUAWEI BTS3812E-BTS3812A-BTS3812AE V100R013C00SPC320
Upgrade Guide
Issue Date 01 2012-04-13
HUAWEI TECHNOLOGIES CO. LTD.
C!"#$%&'t ( Hua)e% Te*'+!,!&%es C!. Lt-. 2012. A,, $%&'ts $ese$.e-.

No part of this document may be reproduced or transmitted in any form or by any means without prior written consent of Huawei Techno ogies !o"# $td"
T$a-e/a$0s a+- Pe$/%ss%!+s

and other Huawei trademar%s are the property of Huawei Techno ogies !o"# $td" & other trademar%s and trade names mentioned in this document are the property of their respecti'e ho ders"
N!t%*e
The purchased products# ser'ices and features are stipu ated by the contract made between Huawei and the customer" & or part of the products# ser'ices and features described in this document may not be within the purchase scope or the usage scope" Un ess otherwise specified in the contract# a statements# information# and recommendations in this document are pro'ided (&) *)( without warranties# guarantees or representations of any %ind# either e+press or imp ied" The information in this document is sub,ect to change without notice" -'ery effort has been made in the preparation of this document to ensure accuracy of the contents# but a statements# information# and recommendations in this document do not constitute a warranty of any %ind# e+press or imp ie d"
Huawei Techno ogies !o"# $td"

&ddress. Huawei *ndustria /ase /antian# $onggang )hen0hen 112123 4eop e5s 6epub ic of !hina 7ebsite. -mai . http.88www"huawei"com support9huawei"com
*ssue 01 :2012-04-13;
Huawei 4roprietary and !onfidentia !opyright < Huawei Techno ogies !o"# $td"
iii
/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide &bout This >ocument
A1!ut T'%s D!*u/e+t

Aut'!$
P$e"a$e- 1# Re.%e)e- 1# Teste- 1# A""$!.e- 1# >ong $ing $i /aoying# ?ang @ei# Ahang Bin# Bu )henghong# ?ao Cian0hong Diu 7enbin ?ang Hao Date Date Date Date 2012-04-10 2012-04-11 2012-04-12 2012-04-13
Su//a$#
This document pro'ides 'ersion upgrade instructions for the /T)3212--/T)3212&/T)3212&- =1006013!00)4!320" This document consists of the fo owing chapters. C'a"te$ 16ead-&head *nformation 2F'er'iew of the Upgrade 4rocess 3Upgrade 4reparations 4Upgrade 4rocedures 1Upgrade =erification G=ersion 6o bac% HI&Ds 2&ppendi+ Deta%,s >escribes the 'ersion reEuirements for the upgrade" >escribes the upgrade procedure" >escribes the preparations before upgrade" >escribes how to upgrade the Node/" >escribes the 'erification operations after upgrade" >escribes how to ro bac% to the 'ersion before upgrade" 4ro'ides answers to the freEuent y as%ed Euestions" 4ro'ides the dia ing test and 'erification sheets used after the upgrade"
*ssue 01 :2012-04-13;
'
/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide
!ontents
C!+te+ts
1 Read-Ahead Information...............................................................1
1.1 Application Scope....................................................................................................................................................1 1.2 Applicable Product Versions....................................................................................................................................1 1.3 Impacts of the Upgrade............................................................................................................................................2 1.4 Precautions...............................................................................................................................................................2 1.4.1 Version Re uirements for !ther "#s................................................................................................................2 1.4.2 Upgrade Precautions..........................................................................................................................................3 1.4.3 "otes..................................................................................................................................................................4 1.4.4 $o%nload $uration of In&ol&ed Soft%are........................................................................................................'
2 Overview of the Upgrade Process..................................................1 3 Upgrade Preparations..................................................................1

3.1 Preparation (hec)list...............................................................................................................................................1 3.2 !btaining *ools........................................................................................................................................................2 3.3 !btaining +iles for Upgrade....................................................................................................................................2 3.4 (hec)ing the "et%or).............................................................................................................................................2 3.' (hec)ing the # uipment !perating Status..............................................................................................................3 3., Upgrading the -.*.................................................................................................................................................3 3./ Upgrading a (.# Version or a (.# (omponent Pac)age....................................................................................4 3.0 (onfirming the (onfiguration 1aseline...................................................................................................................4
4 Upgrade Procedures.....................................................................1
4.1 Upgrading the "ode1 1ootR!.............................................................................................................................1 4.2 Upgrading the "ode1 Soft%are..............................................................................................................................4
Upgrade !erification....................................................................1
'.1 (hec)ing (urrent Alarms........................................................................................................................................1 '.2 (hec)ing (ell Status...............................................................................................................................................1 '.3 2uer3ing the Acti&e "ode1 Version.......................................................................................................................1 '.4 Performing a $ialing *est........................................................................................................................................1 '.' .onitoring the 4PIs After the Upgrade..................................................................................................................2 '.'.1 (riteria for a Successful Upgrade......................................................................................................................2 '.'.2 .onitoring +lo% (hart......................................................................................................................................3
" !ersion Ro##$ac%..........................................................................1

*ssue 01 :2012-04-13; Huawei 4roprietary and !onfidentia !opyright < Huawei Techno ogies !o"# $td" 'ii
!ontents
& 'A(s............................................................................................ 1
/.1 +A2 *able................................................................................................................................................................1 /.2 +A21........................................................................................................................................................................1 /.3 +A22........................................................................................................................................................................3 /.4 +A23........................................................................................................................................................................4 /.' +A24........................................................................................................................................................................' /., +A2'......................................................................................................................................................................../ /./ +A2,........................................................................................................................................................................0 /.0 +A2/........................................................................................................................................................................0
) Appendi*..................................................................................... 1
0.1 $ialing *est After "ode1 Upgrade.........................................................................................................................1 0.2 (hec)ing the $e&ice Panel Status...........................................................................................................................2
'iii
*ssue 01 :2012-04-13;
1 6ead-&head *nformation
1
1.1 A"",%*at%!+ S*!"e

Rea--A'ea- I+2!$/at%!+
The Node/ upgrade can be performed on the @2000 or $@T" Fn the @2000# mu tip e Node/s can be upgraded at the same time" Ior detai ed operations# see the BTS3812E-BTS3812A-BTS3812AE V100R013C00SPC320 Upgrade Guide (M2000-Based)" Fn the $@T# on y one Node/ can be upgraded at a time" The detai ed operations are described in this document"
1.2 A"",%*a1,e P$!-u*t Ve$s%!+s

Tab e 1"1 and Tab e 1"2 describe the 'ersion reEuirements for the upgrade of a Node/ upgrade" Table 1.1 I ash upgrade strategy 3,as' Ve$s%!+ =1006011 and ater 'ersions =ersions ear ier than =1006011 3,as' U"&$a-e St$ate&# Upgrade to /T)3212--12&!-12&-/T)3212&=1006013!00)4!320 Upgrade to =1006011!01)4!302 first# and then to =1006013!00)4!320" Ior detai s# see the BTS3812EBTS3812A-BTS3812AE V100R011C01SPC302 Upgrade Guide"
*ssue 01 :2012-04-13;
Table 1.2 The upgrade po icy of the /oot6F@ B!!tRO4 Ve$s%!+ =ersions ear ier than =1006010!01/013 =1006010!01/013 or ater U"&$a-e P!,%*# Upgrade the /oot6F@ to =1006010!01/013# and then upgrade the software to /T)3212--12&!-12&-/T)3212&=1006013!00)4!320 No need to upgrade the /oot6F@
Ior the Euery method of /oot6F@ 'ersion# see section H"HJI&DG"( Ior how to upgrade the /oot6F@# see section 4"1(Upgrading the Node/ /oot6F@"(
1.3 I/"a*ts !2 t'e U"&$a-e

I/"a*ts !+ Se$.%*es
>uring the acti'ation of the Node/ software# the !4U usage increases" 7hen the acti'ation is comp ete# the !4U usage automatica y reco'ers" Therefore# you are ad'ised to acti'ate the software when the traffic is ow" &fter the acti'ation of the Node/ software# the Node/ automatica y resets# and the ser'ices are interrupted" Iigure 1"1 ists the interruption duration of ser'ices during the upgrade of the reEuired software" Figure 1.1 *nterruption duration of ser'ices during the upgrade of the reEuired software S!2t)a$e Se$.%*es I+te$$u"teSe$.%*e I+te$$u"t%!+ Du$at%!+ 54%+utes6 2K1 4a%+te+a+*e I+te$$u"te4a%+te+a+*e I+te$$u"t%!+ Du$at%!+ 54%+utes6 10
Node/ software
I/"a*ts !+ Net)!$0 C!//u+%*at%!+s

None
1.4 P$e*aut%!+s
1.4.1 Ve$s%!+ Re7u%$e/e+ts 2!$ Ot'e$ NEs
!hec% (6e ated 4roduct =ersion( and ()oftware =ersions( in the BTS3812EBTS3812A-BTS3812AE V100R013C00SPC320 Release !"es re eased with this 'ersion to determine whether the 6N!# !@-# $@T# and @2000 shou d a so be
*ssue 01 :2012-04-13;
upgraded"
1.4.2 U"&$a-e P$e*aut%!+s

Figure 1.1 4@U maintenance in% is bro%en U"&$a-e R%s0 Re,ate- t! 3u+*t%!+s &ffected =ersion )ymptoms and *mpact Des*$%"t%!+
The Node/ is configured with the 4@U whose software 'ersion is 112" @aintenance of the 4@U cannot be performed# or an a arm is reported indicating that the 4@U maintenance in% is bro%en" The fau t is rectified on y after the 4@U is reinsta ed" /efore upgrading the Node/# upgrade the 4@U software to the 113 'ersion or ater" L 1M
7or%around 4robabi ity
Figure 1.2 The icense may fai to be de i'ered U"&$a-e R%s0 Re,ate- t! 3u+*t%!+s &ffected =ersion )ymptoms and *mpacts Des*$%"t%!+
& the 'ersions of /T)3212--/T)3212&-/T)3212&-" 7hen changing the state of the dynamic !- switch of the Node/# the site shou d carry no U-# that is# a the ce s shou d be disab ed" Ftherwise# the icense may fai to be de i'ered" >eacti'ate a the ce s# and then de i'er the icense to change the state of the dynamic !- switch of the Node/" 100M
7or%arounds 4robabi ity
Figure 1.3 The 66U3204866U3201-866U320G876IU fai s to be acti'ated U"&$a-e R%s0 Re,ate- t! 3u+*t%!+s &ffected =ersion )ymptoms and *mpacts Des*$%"t%!+
& the 'ersions of /T)3212--/T)3212&-/T)3212&-" 7hen the Node/ is upgraded from =1006011 to =1006012!00 or a ater 'ersion# there is a probabi ity that the 66U3204866U3201-866U320G876IU fai s to be acti'ated"
*ssue 01 :2012-04-13;
U"&$a-e R%s0 Re,ate- t! 3u+*t%!+s 7or%arounds 4robabi ity
Des*$%"t%!+
6eacti'ate the 66U3204866U3201-866U320G876IU or upgrade the Node/ again" 10M
Figure 1.4 The oca ce becomes una'ai ab e after a distributed site is upgraded" U"&$a-e R%s0 Re,ate- t! 3u+*t%!+s 4rob em >escription Des*$%"t%!+
*f a distributed ce has been configured under the Node/ and the tota number of ce s e+ceeds the icensed imit# the e+cess ce s become una'ai ab e after the Node/ is upgraded" Under a Node/# a distributed ce is configured and a the ce s are a'ai ab e" &fter the Node/ is upgraded# some ce s become una'ai ab e" )end a new icense to the Node/ on the @2000" The icensed imit is arger than or eEua to the tota number of ce s under the Node/" 100M
*mpact
7or%around
4robabi ity
1.4.3 N!tes
The upgrade procedure must be in strict comp iance with the upgrade guide" No re'erse procedure is a owed" >o not upgrade different types of N-s at the same time" 4erform a tria upgrade on one or mu tip e sites" &fter the sites run proper y for more than three days# perform the batch upgrade on the sites on the commercia networ%s" The upgrade procedure and preparation for a sing e-site upgrade are the same as those for the batch upgrade" >uring the upgrade# wait for the command response and chec% whether the command runs successfu y before you run the ne+t command" *f the command fai s# fo ow the instructions pro'ided in this guide" >o not perform the fo owing operations on the N@4T when upgrading the software.
5 5 5
4owering off the N@4T @anua y resetting the N@4T 4u ing out or inserting the N@4T
*f there is a standby N@4T# chec% before the upgrade whether the standby N@4T status is a'ai ab e"
*ssue 01 :2012-04-13;
*f the upgrade fai s or the networ% performance serious y deteriorates during the dia ing test after the upgrade# a 'ersion ro bac% is recommended" The ro bac% depends on the rea situations of the networ% and the reEuirements of the customer" Ior detai s about how to perform the ro bac%# see chapter G=ersion 6o bac%" The software 'ersion in a snapshots of this guide is based on /T)3212-/T)3212&-/T)3212&- =1006013!00)4!BBB"
1.4.4 D!)+,!a- Du$at%!+ !2 I+.!,.e- S!2t)a$e

Iigure 1"1 ists the duration of down oading Node/-re ated software on the $@T of different F@!H bandwidths" Figure 1.5 >own oad duration upgraded through the $@T N!-eB O4CH Ba+-)%-t' 10 @bit8s 122 %bit8s# =/6 112 %bit8s# =/6 D!)+,!a- N!-eB S!2t)a$e T%/e 105 3G511( 12510( Re/a$0 $oca 6emote 6emote
*ssue 01 :2012-04-13;
O.e$.%e) !2 t'e U"&$a-e P$!*ess
>uring a Node/ upgrade# fo ow the upgrade process# as shown in Iigure 1"1" Figure 1.1 Upgrade process
*ssue 01 :2012-04-13;
3
3.1 P$e"a$at%!+ C'e*0,%st
Figure 1.6 4reparation chec% ist N!. 1 2 3 4 1 G H 2 3 Ite/
U"&$a-e P$e"a$at%!+s
Re/a$0 !hec% how many patches ha'e been insta ed" !hec% how many patches ha'e been insta ed" !hec% the acti'e !@- 'ersion and the !@- component pac%age /ac% up the data configuration fi e" -
$ocation of the eEuipment to be upgraded Upgrade time and duration specified by the operator Upgrade reEuirements of the operator Type and mode of the Node/ to be upgraded Number of Node/s to be upgraded Target 'ersion after upgrade :such as software# $@T# @2000 mediation; &cti'e 'ersion of the @2000 ser'er on the operator side &cti'e 'ersion of the 6N! on the operator side &cti'e 'ersion of the !@- on the operator side &cti'e 'ersion of the Node/ on the operator side >ata configuration fi e of the operator eEuipment Transmission networ% topo ogy on the operator side
10 11 12
*ssue 01 :2012-04-13;
N!. 13
Ite/ 7hether the @2000 ser'er needs to be upgraded for synchroni0ation
Re/a$0 *f the @2000 ser'er must be upgraded# contact the engineers responsib e for the @2000 ser'er to prepare for upgrade" *f the 6N! needs to be upgraded# contact the engineers responsib e for the 6N! to prepare for upgrade" To upgrade a !@- 'ersion or a !@- component pac%age# see the !@--re ated upgrade guide" -
14
7hether the 6N! needs to be upgraded for synchroni0ation
11
7hether the !@- needs to be upgraded for synchroni0ation Fther data that shou d be recorded
1G
3.2 O1ta%+%+& T!!,s

-nsure the fo owing too s are a'ai ab e after the upgrade.

U-s for dia ing tests )*@ cards Test 'ehic es
4repare spare parts according to the actua reEuirements"
3.3 O1ta%+%+& 3%,es 2!$ U"&$a-e

To obtain the fi es for upgrade# perform the fo owing steps. +tep 1 Fbtain the software pac%ages" Fbtain the fi es corresponding to the 'ersion from the upgrade ser'er" The fi es are the insta ation fi es of the $@T and Node/ software pac%age" +tep 2 >ecompress the 'ersion fi es to the destination fo ders" *t is assumed that the 'ersion fi es are decompressed to the >.NNode/=er path" This path is assumed as the destination path in the description of the fo owing upgrade steps" ----E+-
3.4 C'e*0%+& t'e Net)!$0

)a'e the atest O4* report before the upgrade" Ior the O4*s to be chec%ed# see section 1"1(@onitoring the O4*s &fter the Upgrade("
*ssue 01 :2012-04-13;
4erform dia ing tests before the upgrade" Ior the test items# see section 2"1(>ia ing Test &fter Node/ Upgrade(" 6ecord the re ated traced messages"
3.
C'e*0%+& t'e E7u%"/e+t O"e$at%+& Status

Iigure 1"H ists the items for chec%ing the operating status of the eEuipment on the $@T before the upgrading" Figure 1.7 !hec% ist for the operating status of the eEuipment before the upgrade on the $@T Ite/ !hec%ing acti'e a arm data. !hec% a a arms of the Node/s to be upgraded on the $@T" ! ear the a arms according to the a arm on ine he p"
Generation of some a arms eads to an upgrade fai ure" Ior detai s# see section H"2JI&DHP"
Resu,t -
C!+*,us%!+ -
!hec%ing ce status. 6un the DSP LOCELL command on the $@T# and then chec% the status of a the ce s contro ed by the Node/s to be upgraded" !hec% whether a the oca and ogica ce s configured are a'ai ab e" *f not# see the a arm reference to rectify the fau t" !hec%ing data consistency. 6un the CH8 DATA command on the $@T# and then chec% the consistency between the Node/ f ash data and the running data" *f the data is inconsistent# reset the Node/"
3." U"&$a-%+& t'e L4T

To upgrade the Node/ $@T# perform the fo owing steps. +tep 1 $og in to the operating system as an administrator" +tep 2 >oub e-c ic% setu".e9e in the $@T insta ation directory to start insta ing the $@T" +tep 3 *nsta the $@T by using the defau t settings" The defau t insta ation path is >.NH7 $@T" ----E+-
*ssue 01 :2012-04-13;
3.& U"&$a-%+& a C4E Ve$s%!+ !$ a C4E C!/"!+e+t Pa*0a&e

Ior detai s about upgrading a !@- 'ersion# see the CME V200R011C00SPC### Upgrade Guide$ Ior detai s about upgrading a !@- component pac%age# see the CME BTS3812EBTS3812A-BTS3812AE %C&MA V200R011C01SPC### C!'p!(ent Upgrade Guide"
3.) C!+2%$/%+& t'e C!+2%&u$at%!+ Base,%+e

6un the C34 CB command to bac% up the acti'e 'ersion# inc uding software 'ersion and data configuration fi e# to create a new !onfiguration /ase ine :!/;" Ior 'ersion ro bac% after the upgrade# you need to confirm the !/" Ior detai s about ro bac% operation steps# see chapter G(=ersion 6o bac%(" There are two modes to confirm the !/. 3ORCED and UN3ORCED"
*f the 3ORCED mode is se ected# the system recreates a !/ e'en if the acti'e !/ is confirmed" *f the UN3ORCED mode is se ected# reconfirming the !/ fai s if the acti'e !/ is confirmed"
*t is recommended that C!+2%$/ 4!-e be set to UN3ORCED# which is the defau t 'a ue of the parameter" /ecause the name of the !/ cannot be dup icated# the !/ might be named with the corresponding current running 'ersion and date# such as V100R011C00SPC100:200;1120"
&fter the confirmation of the !/# do not change the configuration" Ftherwise# the !/ shou d be reconfirmed"
*ssue 01 :2012-04-13;
4
Ste" 1 2 Des*$%"t%!+ Upgrade the Node/ /oot6F@ Upgrade the Node/ software"
U"&$a-e P$!*e-u$es
Iigure 1"2 describes the procedure for upgrading the Node/" Figure 1.8 4rocedure for upgrading the Node/ Re2e$e+*e 4"1Upgrading the Node/ /oot6F@ 4"2Upgrading the Node/ )oftware Du$at%!+ 52!$ Re2e$e+*e O+,#6 10 minutes 30 minutes
The &$@-2G202 /oard F'er oad may be generated during the fo owing operations.

>own oading the Node/ software pac%age &cti'ating the Node/ software &cti'ating the N@4T board software
The a arm is automatica y c eared after the upgrade"
4.1 U"&$a-%+& t'e N!-eB B!!tRO4
&n une+pected reset of a board during the /oot6F@ upgrade process may ead to damage to the /oot6F@ software or fai ure to start up the board" *n this case# send the fau ty board to Huawei for maintenance" To upgrade the Node/ /oot6F@# perform the fo owing steps.
*ssue 01 :2012-04-13;
+tep 1 Fn the Node/ $@T# c ic% the 4a%+te+a+*e tab in the na'igation pane" +tep 2 >oub e-c ic% S!2t)a$e 4a+a&e/e+t Q S!2t)a$e U"-ate" The S!2t)a$e U"-ate dia og bo+ is disp ayed# as shown in Iigure 1"1" Figure 1.1 )tarting to upgrade the /oot6F@
+tep 3 )e ect U"&$a-e BOOTRO4# and then c ic% Ne9t" The U"&$a-e BOOTRO4 dia og bo+ is disp ayed" +tep 4 )e ect the D!)+,!a- BOOTRO4 Pa*0a&e and A*t%.ate BOOTRO4 chec% bo+es# and enter the /oot6F@ pac%age path :for e+amp e# >.NNode/=erN/T)3212-/T)3212&-/T)3212&-=1006010!01/013#; in the D%$e*t!$# Na/e bo+# as shown in Iigure 1"1"
*ssue 01 :2012-04-13;
Figure 1.1 Upgrading the /oot6F@
+tep
! ic% Ne9t" & dia og bo+ is disp ayed# shown as Iigure 1"1" Figure 1.1 !onfirmation dia og bo+
+tep " ! ic% <es" & dia og bo+ is disp ayed# indicating the status and progress of the /oot6F@ upgrade" &fter the /oot6F@ pac%age is acti'ated# the boards that are acti'ated and those fai ing to be acti'ated are isted"
*ssue 01 :2012-04-13;
*f there are boards whose /oot6F@ fai s to be acti'ated# repeat )tep 1 through )tep G# before you perform the subseEuent procedures" ----E+-
4.2 U"&$a-%+& t'e N!-eB S!2t)a$e

To upgrade the Node/ software# perform the fo owing steps. +tep 1 Fn the Node/ $@T# c ic% the 4a%+te+a+*e tab in the na'igation pane" +tep 2 >oub e-c ic% S!2t)a$e 4a+a&e/e+t Q S!2t)a$e U"-ate" The S!2t)a$e U"-ate dia og bo+ is disp ayed# as shown in Iigure 1"1" Figure 1.1 )tarting to upgrade the Node/ software
+tep 3 )e ect U"&$a-e N!-eB S!2t)a$e# and then c ic% Ne9t" The U"-ate N!-eB S!2t)a$e dia og bo+ is disp ayed" +tep 4 )e ect the D!)+,!a- N!-eB S!2t)a$e Pa*0a&e# A*t%.ate N!-eB S!2t)a$e# and
*ssue 01 :2012-04-13;
D!)+,!a- 1# C!+2%&u$at%!+ chec% bo+es# and enter the Node/ software pac%age path :for e+amp e# >.NNode/=erN/T)3212--/T)3212&/T)3212&-=1006013!00)4!320; in the D%$e*t!$# Na/e bo+# as shown in Iigure 1"1"
Ior the reason why the D!)+,!a- 1# C!+2%&u$at%!+ chec% bo+ is se ected# see section H"1(I&D4("
Figure 1.1 Upgrading the Node/ software
+tep
! ic% Ne9t" & dia og bo+ is disp ayed# shown as Iigure 1"1"
*ssue 01 :2012-04-13;
Figure 1.1 !onfirmation dia og bo+
+tep " ! ic% <es" & dia og bo+ is disp ayed# indicating the status and progress of the Node/ software upgrade" &fter the Node/ software acti'ation is comp ete# the boards whose software is acti'ated and those whose software fai s to be acti'ated are isted" *f there are boards whose software fai to be acti'ated# perform troub eshooting by referring to section H"2(I&D1("
&fter the acti'ation of the Node/ software# the Node/ automatica y resets which ta%es about 4 minutes :for reference on y;# and the ser'ices are interrupted"
----END
*ssue 01 :2012-04-13;
U"&$a-e Ve$%2%*at%!+
&fter the upgrade# fo ow the description in this chapter to 'erify the upgrade"
.1 C'e*0%+& Cu$$e+t A,a$/s

!hec% a the acti'e a arms of the upgraded Node/ on the $@T# and c ear the a arms according to the a arm on ine he p"
.2 C'e*0%+& Ce,, Status

6un the DSP LOCELL command on the $@T to chec% the status of a the ce s contro ed by the upgraded Node/" !hec% whether a the oca and ogica ce s configured are a'ai ab e"

*f the ce s are a'ai ab e# you can infer that the upgrade is successfu " *f the ce s are una'ai ab e# chec% whether there are a arms re ated to oca and ogica ce s" )ee the a arm on ine he p for troub eshooting" *f the oca or ogica ce s are una'ai ab e after the a arms are c eared# contact Huawei technica support engineers"
.3 =ue$#%+& t'e A*t%.e N!-eB Ve$s%!+

6un the LST VER command on the $@T" Then# chec% whether the !urrent )oftware =ersion is /T)3212--12&!-12&--/T)3212&=1006013!00)4!320"
.4 Pe$2!$/%+& a D%a,%+& Test

4erform the test by fo owing the instructions pro'ided in section 2"1(>ia ing Test &fter Node/ Upgrade(" -nsure that the system ser'ices are not affected after the Node/ upgrade"
*ssue 01 :2012-04-13;
4!+%t!$%+& t'e 8PIs A2te$ t'e U"&$a-e

This section describes a mechanism that is used for chec%ing whether the O4*s are norma after the Node/ is upgraded and the corresponding f ow chart"
. .1 C$%te$%a 2!$ a Su**ess2u, U"&$a-e

The criteria for a successfu upgrade under norma conditions are as fo ows.
The fo owing O4*s in one integrated counter origina period :usua y one hour or ha f an hour; after upgrade do not e+perience ob'ious f uctuation compared with the O4*s in the same period of ast wee% before the upgrade.
5
Traffic 'o ume :the difference between traffic 'o umes does not e+ceed 1M;. !) -r ang# 4) G4O8122O8324O# H)>4&# H)U4&# 66! setup times# and 6&/ setup times :!)# 4)# and H)4&; )uccess rate of ser'ice access :the difference between success rates of ser'ice access does not e+ceed 0"2M;. 66!# 6&/# and H)4& )uccess rate of mobi ity :the difference between success rates of mobi ity does not e+ceed 0"2M;. intra-freEuency# inter-freEuency# and inter-6&T !a drop rate :the difference between ca drop rates does not e+ceed 0"2M;. &@6# 4)# H)>4&# and H)U4& O4*s that the customer reEuired specia y :the difference between O4*s does not e+ceed 1M;
5 5 5 5
To pre'ent ma,or prob ems fo owing an upgrade# co ect the fo owing O4*s on an hour y basis during the 24 hours after the upgrade is comp ete# and compare these O4*s with those co ected at the same periods of time one wee% before the upgrade.
5
Traffic 'o ume :the difference between traffic 'o umes does not e+ceed 1M;. !) -r ang# 4) G4O8122O8324O# H)>4&# H)U4&# 66! setup times# and 6&/ setup times :!)# 4)# and H)4&; )uccess rate of ser'ice access :the difference between success rates of ser'ice access does not e+ceed 0"4M;. 66!# 6&/# and H)4& )uccess rate of mobi ity :the difference between success rates of mobi ity does not e+ceed 0"4M;. intra-freEuency# inter-freEuency# and inter-6&T !a drop rate :the difference between ca drop rates does not e+ceed 0"4M;. &@6# 4)# H)>4&# and H)U4& O4*s that the customer reEuired specia y :the difference between O4*s does not e+ceed 1M;
5 5 5 5
*f the Node/ does not pass the 'erification and the prob em cannot be so 'ed# you can acti'ate the !/ by running ACT CB to ro bac% the 'ersion" Ior detai s# see chapter G(=ersion 6o bac%"( *f the Node/ passes the 'erification# you can run C34 CB as reEuired to confirm the current !/"
*ssue 01 :2012-04-13;
. .2 4!+%t!$%+& 3,!) C'a$t

Figure 1.1 @onitoring I ow !hart
*ssue 01 :2012-04-13;
"
Ve$s%!+ R!,,1a*0
*f the upgrade fai s or the networ% performance serious y deteriorates in the dia ing test after the upgrade# the 'ersion needs a ro bac%" The ro bac%# howe'er# depends on the actua situations of the networ% and the customer reEuirements" 6un the ACT CB command to ro bac% the software 'ersion" The target !/ name in this step is V100R011C00SPC100:200;1120# as described in section 3"2(!onfirming the !onfiguration /ase ine(" *f the !/ status is 'a id# run the ACT CB command to ro bac% the software 'ersion" *f the !/ status is in'a id# down oad the software 'ersion corresponding to the target !/ and then run the ACT CB command to ro bac% the software 'ersion" )ee 1(Upgrade =erification( to chec% whether the Node/ 'ersion ro bac% is successfu "
7hen ro ing bac% the 'ersion by running ACT CB# if the a arm with B!a$- S!2t)a$e Aut!Su"",# 3a%,u$e :*>. 2G213; is generated# see section H"G(I&D1("
*ssue 01 :2012-04-13;
&
&.1 3A= Ta1,e
Figure 1.9 I&D tab e N!. I&D1 I&D2 I&D3 I&D4 I&D1 =uest%!+
3A=s
How to hand e the fau t in acti'ating the Node/ software when upgrading the Node/ on the $@TR How to c ear the fau t in an abnorma *4o& channe at the far endR How to hand e the fau t in access of a U- to a Node/ after the Node/ is upgradedR 7hy is the duration of down oading shorter if the D!)+,!a- 1# C!+2%&u$at%!+ chec% bo+ is se ectedR How to hand e the fo owing a arms generated when ro ing bac% the 'ersion by running ACT CB. the a arm B!a$- S!2t)a$e Aut!-Su"",# 3a%,u$e :*>. 2G213;R How to determine an ear ier or ater /oot6F@ 'ersionR 7hich & arms @ust /e ! eared /efore the Node/ )oftware Upgrade )tartsR
I&DG I&DH
&.2 3A=1
=uest%!+
How to hand e the fau t in acti'ating the Node/ software when upgrading the Node/ on the $@TR
*ssue 01 :2012-04-13;
A+s)e$
! ic% V%e) Deta%,s to ist the boards whose software fai s to be acti'ated# according to the resu t of the Node/ software acti'ation" Iigure 1"1 shows an e+amp e of the resu t" Figure 1.1 )oftware upgrade resu t
?ou may choose to acti'ate the software of on y one board or a boards of the same type# depending on the resu t of the Node/ software acti'ation" The atter is app icab e to the situation in which the software fai s to be acti'ated for a number of boards of the same type" To acti'ate the board software# perform the fo owing steps. +tep 1 Fn the $@T# c ic% the 4a%+te+a+*e tab in the na'igation pane" +tep 2 >oub e-c ic% S!2t)a$e 4a+a&e/e+t Q S!2t)a$e U"-ate" The S!2t)a$e U"-ate dia og bo+ is disp ayed" +tep 3 )e ect A*t%.ate B!a$-# and then c ic% Ne9t" The S!2t)a$e U"-ate S A*t%.ate B!a$- dia og bo+ is disp ayed" +tep 4 ! ic% S%+&,e 1!a$- on the right of A*t%.ate S!2t)a$e# and then enter the re ated subrac% number and the s ot number"
*ssue 01 :2012-04-13;
*f there are a number of boards whose software fai s to be acti'ated and the boards are of the same type# c ic% A t#"e !2 1!a$-s on the right of A*t%.ate S!2t)a$e# and then se ect the type of boards in the B!a$- t#"e drop-down ist" +tep ! ic% Ne9t# & dia og bo+ is disp ayed# shown as Iigure 1"1" Figure 1.1 !onfirmation dia og bo+
+tep " ! ic% <es to acti'ate the software of a sing e board or a type of boards" +tep & 6epeat )tep 1 to )tep G to acti'ate the software of other types of boards" +tep ) *f the prob em persists after a the preceding operations are performed# contact Huawei technica support engineers" ----E+-
&.3 3A=2
=uest%!+
How to c ear the fau t in an abnorma *4o& channe at the far endR
A+s)e$
*f the Node/ F@ *4 address fai s to be pinged# see Iigure 1"1 for specific so utions" Figure 1.1 )o utions to the fai ure to ping the Node/ F@ *4 address S#/"t!/ The re ated a arms indicate that the -1 in% between the 6N! and the Node/ or the *@&8UN*8!4 port incurs fau ts" The resu t of running DSP E1T1 command at the 6N! indicates that the *@& groups at the 6N! and Node/ fai to interwor% because there is an -1 in% wor%ing in oopbac% mode in the *@& group of the Node/ configured at the 6N!" S!,ut%!+ 6ectify the fau ts in the -1 transmission unti a the re ated a arms are c eared"
6eset the *@& group at the 6N!" *f the fau t in the *4o& channe persists# reset the *@& group after remo'ing the -1 in% that wor%s in oopbac% mode at the 6N!"
*ssue 01 :2012-04-13;
S#/"t!/ The resu t of the on-site chec% indicates that the 6UN8&$@8&!T $->s on the N@4T are not in the e+pected states"
S!,ut%!+ !ontact Huawei technica support engineers immediate y" !o ect the re ated data under the guidance of the engineers" &fter getting the appro'a of the engineers# reset# remo'e# insta # or rep ace the N@4T unti a the re ated fau ts are rectified" !ontact Huawei technica support engineers immediate y" !o ect the re ated data under the guidance of the engineers" &fter getting the appro'a of the engineers# reset# remo'e# insta # or rep ace the N@4T unti a the re ated fau ts are rectified"
$ogin to the Node/ through the -thernet port from the $@T fai ed" The *4 address cannot be pinged"
&.4 3A=3
=uest%!+
How to hand e the fau t in access of a U- to a Node/ after the Node/ is upgradedR
A+s)e$
!ontact Huawei technica support engineers immediate y" !o ect the re ated data under the guidance of the specia ist" 6ectify the fau t at the far end unti a the re ated fau ts are c eared" Ior the troub eshooting steps and the co ected data# see Iigure 1"1" Figure 1.1 Troub eshooting steps and co ected data A*t%!+ !hec% the Node/ acti'e a arms on the Node/ $@T# and then c ear the a arms if any" !hec% the acti'e a arms associated with the Node/ on the 6N! $@T# and then c ear the a arms if any" Up oad the main board ogs by running the fo owing command.
U$> I*$-. >)TIT()*+'ai(,rd-!g$"."(# I$&GT@&*N/6>$FG# *4T(10"1G1"41"H1(# U)6T(admin(# 47>T(admin(# !ITUN!F@46-))->U
Data C!,,e*teNode/ a arm data Node/ a arm data
Up oaded main board ogs
*ssue 01 :2012-04-13;
A*t%!+ !hec% the a'ai abi ity of the oca ce s at the Node/ by running the DSP LOCELL command" !hec% the a'ai abi ity of the ogica ce s at the 6N! by running the DSP UCELL command" !hec% the Node/ output power" !hec% the oc%ing of freEuency and scramb e of the U- under test" !hec% the accessibi ity of another U- or another )*@ card to the Node/" *f possib e# chec% whether the U- under test sends an 66! !FNN-!T 6-D message" !hec% the 6T74 of the Node/" The 6T74 shou d be a 'a ue at S10G d/mV3 d/" Duery the *ub connection data carried o'er a &&$2 paths of the Node/ by running the DSP AAL2CHN command at the 6N!" Trace and sa'e a messages of the Uunder test through sing e U- tracing at the 6N!" Trace and sa'e a messages of the Uunder test o'er the Uu# *u# and *ub interfaces at the 6N!" Trace messages o'er the *ub interface of the Node/" -+port 6N! !>6 og fi es before and after the Node/ upgrade"
Data C!,,e*te@@$ command messages sa'ed
@@$ command messages sa'ed
$ogs recorded 6T74 measurement fi es recorded @@$ command messages sa'ed )ing e U- tracing
@essages traced o'er the *u# *ub and Uu interfaces @essages traced o'er Node/ *ub interface !>6 og fi es before and after Node/ upgrade
&.
=uest%!+
3A=>
7hy is the duration of down oading shorter if the D!)+,!a- 1# C!+2%&u$at%!+ chec% bo+ is se ectedR
A+s)e$
The Node/ software pac%age contains the software for a the boards supported by
*ssue 01 :2012-04-13;
the Node/" -ach board type corresponds to one board software pac%age" *n regu ar mode# the entire Node/ software pac%age is down oaded to the Node/" *n practice# howe'er# on y some types of board are configured on the Node/# and not a board software pac%ages are reEuired" >own oad by configuration refers to the action to down oad the reEuired board software from the fi e ser'er during the upgrade according to the types of board current y configured on the Node/" This can effecti'e y reduce the tota 'o ume of data to be down oaded# minimi0e the duration# and ensure that the software pac%age occupies the east storage space on the hard dis%" Genera y# down oad by configuration has the fo owing benefits.
Fn y the reEuired board software pac%ages are down oaded according to the current Node/ configuration" The 'a uab e maintenance in% bandwidth is uti i0ed effecti'e y# the duration of down oading the software is minimi0ed# and the upgrade efficiency is impro'ed" The storage space on the hard dis% of the Node/ is uti i0ed effecti'e y# and unused software storage space is a'oided" This mode features a higher down oad rate when the Node/ is configured with boards of fewer types"
Figure 1.1 !omparison between regu ar down oad and down oad by configuration T#"%*a, C!+2%&u$at%!+ B!a$T#"e N@4T NUT* H//* @T6U @&IU 3+1 configuration of the >/)3200 H//U =t#. 1 1 1 3 3 1 G0 min" 10 min" 21 @/ 12 @/ G4 %bit8s Du$at%!+ Re&u,a$ 20 min" B# C!+2%&u$at%!+ 40 min" St!$a&e S"a*e Re&u,a$ 30 @/ B# C!+2%&u$at%!+ 11 @/ G4 %bit8s Ba+-)%-t'
3+1 configuration of the /T)3212or /T)3212&
The Node/ uses one acti'e directory and one standby directory to store two pieces of software" Ior the >/)3200# the sa'ed space on the hard dis% in down oad by configuration mode is 3 @/ + 2T G @/"
*ssue 01 :2012-04-13;
The methods of adding a type of board to the Node/ 'ary with the down oad modes# as described in Iigure 1"2" Figure 1.2 @ethods of adding new types of board to the Node/ 4!-e 6egu ar down oad Des*$%"t%!+ >own oad the entire Node/ software pac%age to the Node/" >own oad on y the reEuired board software pac%ages for the boards current y configured on the Node/" H!) t! A-- a T#"e !2 B!a$The system obtains the board software pac%age direct y from the Node/ and automatica y acti'ates it" ?ou shou d obtain the software pac%age from the specific fi e ser'er" Then# the system automatica y acti'ates it to upgrade the board" E9*e"t%!+ None" Re/a$0 None"
>own oad by configuration
&n a arm is reported if the fi e ser'er cannot be connected to or no corresponding 'ersion is found on the ser'er"
The a arm B!a$S!2t)a$e Aut!-Su"",# 3a%,u$e :*>.2G213;
The Node/ supports down oad by configuration for the f ash software on the boards but does not support down oad by configuration for the /oot6F@" The Node/ /oot6F@ pac%age must be down oaded in regu ar mode" *f the a arm with the B!a$- S!2t)a$e Aut!-Su"",# 3a%,u$e :*>. 2G213; is generated# run the SPL SO3TWARE command to supp ement the software"
&." 3A=?
=uest%!+
How to hand e the fo owing a arms generated when ro ing bac% the 'ersion by running ACT CB. the a arm B!a$- S!2t)a$e Aut!-Su"",# 3a%,u$e :*>. 2G213;R
A+s)e$
>uring the upgrade# the 'ersion to be ro ed bac% is down oaded according to the configuration" *n this case# if some boards are not configured# the corresponding software pac%ages are not down oaded to the N-" 7hen these boards are configured and the N- is being upgraded to another 'ersion# the corresponding software pac%ages are not a'ai ab e in the standby directory" *f the 'ersion is ro ed bac% to the 'ersion before upgrade# the a arm B!a$- S!2t)a$e Aut!-Su"",# 3a%,u$e :*>. 2G213; is generated" To so 'e the prob em using the @2000# up oad the corresponding software pac%ages again to the @2000 ser'er# and then run SPL SO3TWARE to manua y supp ement the board software" The Node/ automatica y acti'ates the board software" To so 'e the prob em using the $@T# run SPL SO3TWARE to manua y supp ement the board software" The Node/ automatica y acti'ates the board software" *f the
*ssue 01 :2012-04-13;
command does not run successfu y and the software pac%ages are remo'ed from the oca hard dis% or their paths are changed# you shou d down oad the software pac%ages again and acti'ate them"
&.& 3A=@
=uest%!+
How to determine an ear ier or ater /oot6F@ 'ersionR
A+s)e$
?ou can run LST VER to Euery the /oot6F@ 'ersion of the Node/# run LST BRDIN3O to Euery the board type# run DSP BRDVER to Euery the /oot6F@ 'ersion of the board" The re eased /oot6F@ 'ersions are numbered in two formats# BB"BBB"BB"BBB and =BBB6BBB!BB/BBB" The fo owing is the method for determining an ear ier or ater /oot6F@ 'ersion. - iminate the non-digita characters contained in the 'ersion number# and you get a number" & arge number indicates a ater /oot6F@ 'ersion" Ior e+amp e# in =ersion & :100"012"00"200; and =ersion / :=1006010!01/013;# the number of =ersion & is 10001200200 and the number of =ersion / is 10001001013" /ecause 10001200200 is arger than 10001001013# =ersion & is re eased ater than =ersion /"
&.) 3A=A
=uest%!+
7hich & arms @ust /e ! eared /efore the Node/ )oftware Upgrade )tartsR
A+s)e$
!hec% for acti'e a arms before the Node/ software upgrade" ! ear a a arms indicating in% fai ures before upgrading the Node/ software# such as 6I Unit @aintenance $in% Iai ure :& arm *>. 2G231; and 6emote @aintenance $in% Iai ure :& arm *>. 21301;"
*ssue 01 :2012-04-13;
)
).1 D%a,%+& Test A2te$ N!-eB U"&$a-e
Figure 1.1 >ia test after Node/ upgrade Re*!$- !2 t'e N!-eB D%a,%+& Test Node/ name Test time Test resu t W4ass WNot 4ass
A""e+-%9
!e name !e *> !e scramb e
D%a,%+& Test )peech. fi+ed- ine phone to mobi e :3G; )peech. mobi e :3G; to fi+ed- ine phone )peech. mobi e :3G; to mobi e :2G; )peech. mobi e :2G; to mobi e :3G; )peech. mobi e :3G; to mobi e :3G;
Resu,t W4ass WNot 4ass WN8& W4ass WNot 4ass WN8& W4ass WNot 4ass WN8& W4ass WNot 4ass WN8& W4ass WNot 4ass WN8&
Re/a$0
*ssue 01 :2012-04-13;
=4. mobi e :3G; to mobi e :3G; 4). 4>4 acti'ation )peech con'ersation Eua ity =4 con'ersation Eua ity 4) communications Eua ity !a drop )oft hando'er 6)!4 :shou d Q SH0 d/m; -c8*0 :shou d Q S10 d/;
W4ass WNot 4ass WN8& W4ass WNot 4ass WN8& WGood W/ad WN8& WGood W/ad WN8& WGood W/ad WN8& W4ass WNot 4ass WN8& W4ass WNot 4ass WN8&
Re/a$0
Teste- 1# 5s%&+atu$e6
).2 C'e*0%+& t'e De.%*e Pa+e, Status

Figure 1.2 !hec% ist for the de'ice pane status N!. 1 2 3 4 Ite/ 7hether the de'ice pane can be proper y started 7hether there is any board in red :fau ty; 7hether there is any board in ye ow :reporting an a arm; 7hether there is any board in b ue :b oc%ed; E9"e*teResu,t ? N N N A*tua, Resu,t
*ssue 01 :2012-04-13;
N!. 1 G H 2 3 10
Ite/ 7hether there is any board in dar% gray :in position but not configured; 7hether there is board in ight gray :configured but not in position; 7hether the board configured after upgrade is consistent with that before upgrade 7hether the 66Us are proper y disp ayed 7hether the 6HU/s are proper y disp ayed 7hether the 4ico 66Us are proper y disp ayed
E9"e*teResu,t N N ? ? ? ?
A*tua, Resu,t
*ssue 01 :2012-04-13;

c04 Bts3812e-Bts3812a-Bts3812ae v100r013c00spc320 Upgrade Guide (Lmt-Based)

Hochgeladen von

Dokumentinformationen

Originaltitel

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

c04 Bts3812e-Bts3812a-Bts3812ae v100r013c00spc320 Upgrade Guide (Lmt-Based)

Hochgeladen von

Copyright:

Verfügbare Formate

HUAWEI BTS3812E-BTS3812A-BTS3812AE V100R013C00SPC320

HUAWEI TECHNOLOGIES CO. LTD.

C!"#$%&'t ( Hua)e% Te*'+!,!&%es C!. Lt-. 2012. A,, $%&'ts $ese$.e-.

T$a-e/a$0s a+- Pe$/%ss%!+s

Huawei Techno ogies !o"# $td"

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide &bout This >ocument

A1!ut T'%s D!*u/e+t

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

2 Overview of the Upgrade Process..................................................1 3 Upgrade Preparations..................................................................1

" !ersion Ro##$ac%..........................................................................1

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

1.2 A"",%*a1,e P$!-u*t Ve$s%!+s

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

1.3 I/"a*ts !2 t'e U"&$a-e

I/"a*ts !+ Net)!$0 C!//u+%*at%!+s

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

1.4.2 U"&$a-e P$e*aut%!+s

7or%around 4robabi ity

7or%arounds 4robabi ity

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

U"&$a-e R%s0 Re,ate- t! 3u+*t%!+s 7or%arounds 4robabi ity

6eacti'ate the 66U3204866U3201-866U320G876IU or upgrade the Node/ again" 10M

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

1.4.4 D!)+,!a- Du$at%!+ !2 I+.!,.e- S!2t)a$e

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

O.e$.%e) !2 t'e U"&$a-e P$!*ess

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

Ite/ 7hether the @2000 ser'er needs to be upgraded for synchroni0ation

7hether the 6N! needs to be upgraded for synchroni0ation

3.2 O1ta%+%+& T!!,s

U-s for dia ing tests )*@ cards Test 'ehic es

4repare spare parts according to the actua reEuirements"

3.3 O1ta%+%+& 3%,es 2!$ U"&$a-e

3.4 C'e*0%+& t'e Net)!$0

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

C'e*0%+& t'e E7u%"/e+t O"e$at%+& Status

3." U"&$a-%+& t'e L4T

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

3.& U"&$a-%+& a C4E Ve$s%!+ !$ a C4E C!/"!+e+t Pa*0a&e

3.) C!+2%$/%+& t'e C!+2%&u$at%!+ Base,%+e

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

The a arm is automatica y c eared after the upgrade"

4.1 U"&$a-%+& t'e N!-eB B!!tRO4

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

Figure 1.1 Upgrading the /oot6F@

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

4.2 U"&$a-%+& t'e N!-eB S!2t)a$e

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

Figure 1.1 Upgrading the Node/ software

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

Figure 1.1 !onfirmation dia og bo+

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

.1 C'e*0%+& Cu$$e+t A,a$/s

.2 C'e*0%+& Ce,, Status

.3 =ue$#%+& t'e A*t%.e N!-eB Ve$s%!+

.4 Pe$2!$/%+& a D%a,%+& Test

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

4!+%t!$%+& t'e 8PIs A2te$ t'e U"&$a-e

. .1 C$%te$%a 2!$ a Su**ess2u, U"&$a-e

/T)3212--/T)3212&-/T)3212&=1006013!00)4!320 Upgrade Guide

1.2 A"",%a1,e P$!-ut Ve$s%!+s

I/"ats !+ Net)!$0 C!//u+%at%!+s

).2 C'e0%+& t'e De.%e Pa+e, Status