ZTEDH ZXWR RNC Radio Network Controller Software Manage- ment Operation Guide Version 3.09.30 ‘ZTE CORPORATION INO.55, Hitech Road South, ShenZhen, PRChina Portcade: $18057 Tel: (88) 755 26771900, Fe "35 267708 ersLEGAL INFORMATION (Copyright © 2010 ZTE CORPORATION. ‘The contents of this document are protected by copyright laws and intemational treaties. Any reproduction or dtribution of this document or any partion ofthis document, in any frm by any means, thou the prior written consent of ZTE CORPO- RATION s prohibited, Addtionally, the contents of this document are protected by contractual confidential obligations. ‘All company, brand and product names are trade or service matks, or registered trade or service marks, of ZTE CORPOR ATION or of their respective owners, This document is provided "a i", and all express, implied, or statutory warranties, representations or condtions are ds- claimed, inducing without limitation any implied warranty of merchartabty,fness for pattcular purpose, title er norin- Fringement, ZTE CORPORATION anditslcensers shall nat be lable For damages resulting from the use oF or reliance on the information contained herein. ZZTE CORPCRATION or its licensors may have current or pencing intellectual property ights or applications covering the subject, tmalter ofthis document. Except as expressly provided in any wien license between ZTE CORPORATION ands licensee, the user of ths documert shallnct acquire any license to the subject matter herein {ZTE CORPORATION reserves the right to upgrade or make technical change to this product without further notice Users may ist ZTE technical sunpert website hitp:/Jensuppatzte.com cn to inquire related information. ‘The imate right to interpret this product resides in ZTE CORPORATION. Revision History Revision No. _| Revision Date | Revision Reason R10 20100713 First Edition (V3.09.30.03) Rid 20100906 Updated: 2 Managing Software Version Package Serial Number: $J-20100603155704-017Contents Preface Basic Concepts . Introduction Of Terms .......scereeeeeeteteeeteteeneeeee L Resource Status Transfer Managing Software Version Package Entering RNC Version Package Management... Adding Version Package To Database... Full Downloading Version Package........ Activating Version Files. Deleting Packages s..cssssseesesssssessetenessesseeaessssseesnee 10 Deleting Version Packages ..vsesscsesssssestnessesseeenesveseee 10 Deleting Patch Packages v..scsosscsesssssesemessesseeenesveseee EL Part Downloading Packages.....cssscssssessesseeaessesseesne 12 Part Activating Packages ......cscsessssssesetusssssseeeessssseeenen DA COMP Initial Version .cccssssseecesssssessetenessesseeenessssseesensss 16 Creating OMP Initial Version .....ccsssssseseeessesseeenssveseee 16 Querying OMP Initial Version ....csesssssesetessssseeenssveseee 18 Version Package Log Management ....ssssscssessssssseeenessessee 18 Displaying LOgS ..sssssssseessssseeesessssseseesnsssssseeeeesveseee 18 QUErYINg LOGS. sessesssssetsessssseeetessssseseesnissessceceesveseee 19 RNC NE Software Version Management. Entering RNC NE Software Version Management ....sscsss21 Displaying Rack Diagram ....scsssssssssessessesseeaesvsseeeeennn 22 Displaying NE Running Version Information .....ssssseese 23 Displaying NE Common Version Information ...ssssseeee 23 Displaying NE Special Version Information ...s.sscsesssseesen 24 Deleting Versions ....csssssssssssesessssseeenssseeseesnensene 4 Displaying NE Log Information ......sscssuessesseesesssseeesnen 2S Querying NE Log Inform ation ....scsssssesesessesseeeessesee 26 Displaying Board Version Information ....ssessesesesssseeeen 27 Running Version Interface....sosscessssssestessesseeenssesee 28 Confidential and Proprietary Information of ZTE CORPORATION IZAWR RIC Softw are Management Operation Guide TIE Special Version Interface ....secscsesssssesetsssessetenesseseeee29 Refreshing Versions ...scsesssssessssssseseeen essences 29 Upgrading Versions ...ssesssssesssssseseeseesssseeeens30 Cancelling Test vasssscssssussssseeenesssseeentenseseens 32 Backing Up Version Interface....scsssseessessssessetenesseseeee33 Activating Versions ..csscssssssseeseessssceeeensessens D4 Testing Versions ..scsscsssesssseeesssssseseeseesssseeeens 36 Deleting Versions ...sscscsessssseeussssseseesessssseeeens ST Switching OMP Version ....ssosscsesessssseeesssssesetseesssseeeens 38 Setting OMP Boot Mode ....ssssscsssessssseeessssseseesnessssseeeen 39 Querying OMP Start Mode....s.cscsessssseecnssssesersneesssseeenn 40 Refreshing Rack Diagram Status... 4 Exporting Version Information ...csssssesssssseseenessssseeeen # Figures. 43 Tables HI Confidential and Proprietary Information of STE CORPORATIONPreface About This Manual What Is In This Manual? Thank you very much for choosing the UMTS wireless access sys- tem of ZTE Corporation ‘The UMTS wireless access system of ZTE is a 3G mobile commu nication system developed on a basis of the UMTS technology. It features strong capability in CS and PS service processing and pro- vides diversified services. Compared with GSM, UMTS delivers a wider range of telecommunication services, induding such multi- media services as voice, data, and image transmission, with higher rate and resource utilization ratio. ZXWR RNC, a new generation radio network controller in the ZTE UMTS V3 family, delivers functions of system access control, secu- rity mode control, mobility management, and radio resource man agement and control, etc ZXWR RNC provides all the functions defined in the 3GPP R99/R4/R5/R6/R7 protocol, and offers Iu, Iub, and Iur series standard interfaces, which enable it to connect with CNs, RNCs, and Node Bs from different manufacturers. Developed on a basis of ZTE all IP unified hardware platform, ZXWR RNC features a distributed design, separating control plane and user plane as well as interface and application. It supports ATM/IP dual protocol stack and can smoothly evolve to full IP UTRAN Chapter Summary Chapter 1 Basic Concepts Introduces glossaries and resource status transfer of this manual: Chapter 2 Software Version Introduces relative operations Package Management of software version packages management. Chapter 3 RNC NE Software Introduces relative operations Version Management. of RNC NE software version management. Confidential and Proprietary Information of ZTE CORPORATION IEXWR RNC Softrare Management Operation Guide TIE This page is intentionally blank, HI Confidential and Proprietary Information of STE CORPORATIONChapter 1 Basic Concepts Table of Contents Introduction Of Terms Resource Status Transfer ... Introduction Of Terms Software version management is to manage software versions of RNC, provide such operations as adding, deleting and activating RNC software versions, and complete maintenance and control of NE device running versions. Terms on the interface of this version are different from those in the previous version, so hereby a brief explanation of them is made in advanee, 1. Backup version: its files have been downloaded to RNC, but have not been applied to boards. 2. Common version : it has been applied to boards of ist type. If users put these in slots, then the common version is the version that runs on them 3. Special version : itis the specified version that runs on defined boards, and its level is higher than the common version. Running version: it is the present version running on boards. 5. Configuration version: it includes the special version and the common version. If the special version is running on boards, it is the special version. If the special version is not running ‘on boards, it is the common version. Resource Status Transfer There are three foreground database tables (r_verall, r_verdft, and r_ veraptd) relating to software versions on OMP board. = r_verall: itis suitable for all version file information tables of peripheral boards. = rverdft: itis the default version file information table except for OMP version file information ‘Confidential and Proprietary Information of STE CORPORATION 1(WR RNC Softw are Management Operation Guide TIER = t_veraptd: it is the specified version file information table except for OMP version file information Although software version m anagem ent is to configure foreground database tables through message procedures and without syn- chronizing foreground and background data process, the back: ground is also to write database recording tables only related to version package and OMP version table, Each status's transfer involves changes of foreground table data, as shown in Figure 1 FIGURE 1 RESOURCE STATUS TRANSFER MAP yo ar Backup Version 5 oe . on rag vee) ing Version) SS . vena File Package spat venae Comsition Sei eet “ re Spesat Venion 1 is deleted from r_ veraptd table. Version package download- ing: if version files to RNC, the downloaded version files are added into r_verall table Version deleting: if a single backup versions deleted, a records deleted from r_ve- rall table, Special version —switch- ing: if the special version is switched, a record is deleted from r_veraptd ta~ ble. Version activating: if a single version file is acti- vated, a record is added into r_verdft table. Version upgrading (only for special version) : if the special version is up- graded, a record is added into rverdft, and a record 2 Confidential and Proprietary Information of STE CORPORATIONChapter 2 Managing Software Version Package Context RNC version package is to organize versions released this time all together according to one configuration file. Users can have full downloading and activating of the RNC version package from software version management, In order to manage them conveniently, Version packages are di- vided into software package and hardware package. Therefore, you can activate them separately as needed, which has effectively solved the problem of service interruption due to board resetting when the hardware version is activated ‘The following is the description of the software package and the hardware package = The software package includes CPU version, FPGA version, MCU version, microcode version, and 3G platform online configuration script file version. = The hardware version package includes such versions as WORKEPLD, BOOT, etc. O vote: Presently, part downloading and part activating of version pack- ages are available to RNC version package. Users need to put this type of boards in slot on the slack diagram after packages are ac- tivated. Table of Contents Entering RNC Version Package Management cesctnissenseee Adding Version Package To Database....csissscssssuessneesnnes 5 Full Downloading Version Package. 7 Activating Version Files... : 9 Deleting Packages ...sscucsssseensssssetsnscnienseesiesvesseesenses 10 Part Downloading PackageS...........:su.stenssseesnsetennneces verse AB Part Activating Packages..esccsccssccsssseeensessnseesensensesaseeecvees L OMP Initial Version ....... seosiessnneeennsnnvsnneesnenses 16 Version Package Log Management ......c:s:...cessesnsseeesieeee AB ‘Confidential and Proprietary Information of STE CORPORATION 3ZAWR RIC Softw are Management Operation Guide TIE Entering RNC Version Package Management Prerequisites The Topology Management view is opened. Steps 1, Select View Software Version Management from the Topology Management view, as shown in Figure 2 FIGURE 2 ENTERING SOFTWARE MANAGEMENT VIEW Byster Tonology Operation Help (B® | Topology Management Configuration Management Performance Management Eault Management ree F 1) Test Management ‘Security Management Log Managomont Policy Management Report Management Syetem Management MML Terninal Right click RNG Software Version Package from Configura- tion Resource Tree of the left pane. Add Version Package Into Database interface pops up, as shown in Figure 3 FIGURE 3 RNC SOFTWARE PACK MANAGEMENT Confidential and Proprietary Information of ZTE CORPORATIONTIER Prerequisites Context Steps Chapter 2 Managing Softw are Version Package A Caution: Users have to obtain mutual exclusion right before operat- ing on NM system software. To apply for mutual exclusion right, please see ZXWR RNC (V3.08.30) RNC Tool Configura~ tion Guide. END oF steps Adding Version Package To Database ‘The Software Version Management interface is opened. WRNC version is published in the type of software package with configuration file list To add software package to database is to transfer the completed versions in the mode of FTP fram user-defined location to the ne- gotiated directory of server for later use, which is called as estab- lishing an MO from the role of management object. To add versions to database is to perform at the background. It does not need to synchronize with the foreground, and does not need to operate on business, but can be operated offline. Software package is saved in the server’s directory as “ums-svr/tmp/ftp/version/NE_ type/large version No./small version No." To find correspondent version files in the version pool through "NE type/large version No./small version No./fine name”. 1. Right click RNC Software Pack Management, and the Cre- ate Version Pack menu pops up, as shown in Figure 4. FIGURE 4 CREATE VERSION PACK VIEW [B) Configuration Resource Tes ono01(10.82.102.71:2109 a L.| ement 4h MassDateoreating-789 fw 2. The Create Version Pack dialog box pops up, and click =1 to select the configuration file (config.ini) from File Path, as shown in Figure 5. ‘Confidential and Proprietary Information of STE CORPORATION 5EXWR RNC Softrare Management Operation Guide TIEN FIGURE 5 FILE PATH SELECTION countchecksum? O vote: The combining check value of all version files! contents is wri ten at the end of the configuration file (VersionConfig.ini) when the foreground is making software packages, which is not in formed to operators (executing packages added into database ) of whether the content of this package has been revised be- fore it is added to database by OMC, so there is an option of Count Checksum? If operators select Count Checksum? , the system will read the information of all version files to get a combining check value compared with the check value of the configuration file. If these two values are same, execute the operation of adding packages to database. If they are different, do not execute the operation of adding packages to database. Click OK, and the Version Pack Information interface pops up, as shown in Figure 6, FIGURE 6 VERSION PACK INFORMATION INTERFACE Te tiaermee (T0077 00000 ‘oon raekn (aoanm0 creastine (TOT TH0086 ‘oon ree namter re Pam fateetva8 = TRSSTaVPRE RAP ROE. ANG JPRE FAP. VEOUAIUD {RalsesoaPBEWAPUC ANC APEE_RAP_ VG093002 veman07 SCHUBICHUSIRNE.RC_CHUB_C..¥3093002 veman07 é Confidential and Proprietary Information of ZTE CORPORATIONTIER Prerequisites Context Steps Chapter 2 Managing Softw are Version Package 4. Click OK, version files are uploaded to OMC server by FTP, as shown in Figure 7. FIGURE 7 RESULT INTERFACE IRNC_RNC_APEE_RéP_T#®_DEV.. Success IRNC_RNC_APEE RAP 9DU DE. Success \Uc_ANC_APSE_AAP_DEWNOS. Success IRNE_ANC_APEE_2_RAP_AOO%,. Success \uc_RNC_APSE_? RAP_CEWaD.. Success IRNC_ANC_CHUB CHUB #215... Success IRNC_RNC_CHUG_CHuB 260_.. Success IRNG_RNC_CHUB_THUR_6250_ Success IRNC_ANC_OTA_RAP_250 DEV. Success luc RNC_OT Rap Dewos.00. Success IRNC_RNC_DTE_OTB G62 DEW. Success IRNC_RNC_OT_EUP_2m0_DEV. Success luc_ANC_AT_Eup_Bewos a0. Success IRNE_GUISY_GLL EGRESS DEW. success SSuocase ‘oparcten somplota te total number 186,166 cucraceru, vale DOF STEPS Full Downloading Version Package ‘The Software Version Management interface is opened. Full downloading version package is to download all version files of version packages to the foreground. Version package downloading needs to specify a management NE so that the system will list this NE’s type. And the system will ist the NE that is matched with the version package and in link status for users to select, That is to say there is a version running on the NS board that needs to be loaded with NE, and an empty rack is run by pre-delivery initial versions. 1. The Version Package view is opened, and click the Down- load All Pack button, as shown in Figure 6. ‘Confidential and Proprietary Information of STE CORPORATION 7EXWR RNC Softrare Management Operation Guide TIE FIGURE 8 SOFTWARE PACKAGE DOWNLOADING INTERFACE > Mromorgze nae: 21030 RAC Senet nccenert Pavan Payee “pyc eyvecesansrst Savana ‘eons ra Same =———4 eomecemcn SE 2. The Select Managed Element dialog box pops up, and select the NE linked, as shown in Figure 9. FIGURE 9 SELECT MANAGED ELEMENT Eee @ a Server Th RNC Management UE 110 3. Click OK, and the system downloads version files to foreground NE. If downloading fails, the system will list failure causes in Result, as shown in Figure 10. 8 Confidential and Proprietary Information of 2TE CORPORATIONTIER Prerequisites Context Steps Chapter 2 Managing Softw are Version Package FIGURE 10 RESULT OF THE DOWNLOAD To RNC EEO BOORT-EPU TOTO ‘pera equet en ral ve=porae a peoer 0" 090202-EPLb- 1005p Operturoquetetrattesonoe ke =) 04 Uae? #54 Oshn Cpertnn raul est rl tearce ci i DL 04000 FPA 6 person rave esarliesorse cit fo ota o1 oso" ePcp-10rsps Operon equesteanrattesanse tu [22 bragatzomaat-fron sbrew_s00nin ——_opersanraniestesnrttesparse it force we aenaHt ePLe roeves———dpetsunronuecteanrttectonoe at [ie bIee- oestrus eet inevea person rave esarliesorse cit [3 on-ei oanan_ePio_1Gsme0 Operon equesteanrattesanse tu [ir ess of ounatarrom atm veznn (gorse roguet eat rte a Oc Operturequestectrattessnoe ur [Iban oro eFL0- 104 vo person rave esa rliesorse cit (euava 3 oetan-Fraa 1053 Operon quest ant esanoe END oF steps Activating Version Files ‘The Software Version Management interface is opened. To activate Version files is to multicast all version files in version packages from the OMP board to correspondent boards, regard version files as common version switching. Change of NS boards version affects greatly, therefore correspondent boards are not re- booted during software package activation, and users can activate these correspondent boards in batch on rack diagram 1. The Version Package view is opened, and click the Activate All Version Files button ®, as shown in Figure 11 FIGURE 11 SOFTWARE PACKAGE ACTIVATING INTERFACE {> Hl soncin anon az2%c2m Me: cotrachackaaneere Bpenanoan eon * Ba yo02.20020_ ‘-Luson anor fipipeccinsneer seman oh — ‘Confidential and Proprietary Information of ZTE CORPORATION 9ZAWR RIC Softw are Management Operation Guide TIE 2, The Select Managed Element dialog box pops up, and select the NE linked, as shown in Figure 12. FIGURE 12 SELECT MANAGED ELEMENT Eee @ a Server Th RNC Management UE 110 3. Click OK, the system will activate version files that have been downloaded to RNC. If the activation fails, the system will list failure causes END OF steps Deleting Packages Context Package deleting falls into version packages deleting and patch packages deleting Deleting Version Packages Prerequisites The Software Version Management interface is opened Steps 1, Select the Version Package node from Configuration Re- source Tree, and right click to select Delete, as shown in Figure 13 10. Confidential and Proprietary Information of ZTE CORPORATIONTIED Chapter 2 Managing Soft are Version Package FIGURE 13 DELETING VERSION PACKAGE INTERFACE © Configuraton Resource Tree 1 op001(128.0.0.202:21099 JALRNC SoftWarePack Management fay v3.09.3002 $ (oa V3.09.3003 Download Jagomont Compare > After version packages are deleted, the version packages on the topology tree and the sub-tree are deleted also. DOF STEPS Deleting Patch Packages Prerequisites The Software Version Management interface is opened. Steps 1. Select a version file package from Configuration Resource Tree, and right dick to select Delete, as shown in Figure 14, FIGURE 14 PATCH PACKAGE DELETING INTERFACE © Configuraton Resource Tree 1 op001(128.0.0.202:21099 JALRNC SoftWarePack Management fay v3.09.3002 $ (oa V3.09.3003 Download Jagomont Compare > ‘The patch package is deleted. If no other patch packages are contained in the version package, the version package is also deleted. DOF STEPS ‘Confidential and Proprietary Information of ZTE CORPORATION 42Prerequisites Steps (WR RNC Softw are Management Operation Guide TIEN Part Downloading Packages The Software Version Management interface is opened 1. The Version Package view is opened, and click the Down- load Pack button 8, as shown in Figure 15, FIGURE 15 SOFTWARE PACKAGE PART DOWNLOADING INTERFACE ‘pH taworyaenn zest) FMF covneracanaget Greqes0osn2 pegenmaag: ® peginm mann Ci fean nase ‘sonra fe oar ener acer CR ‘rao rie noma \esonDeston =m Select a version file in the file list from the Choose Version Pack dialog box popped up, as shown in Figure 16 FIGURE 16 CHOOSE VERSION PACK Galenil * NTOD_2Cetwere On Tae Beare MPxeBSaflware On The Board fNic_2sanware On The Bosra D> DTEGetvare On The Board o3en (CLKOSerware On The Boare jpsen SsDTBsanvare On The Board UM_26oftwete On The Beard (i ] 3. Click OK, and the Select Managed Element dialog box pops up, and select the NE linked, as shown in Figure 17. 12 Confidential and Proprietary Information of ZTE CORPORATIONTIE Chapter 2 Managing Softw are Version Package FIGURE 17 SELECT MANAGED ELEMENT Eee @ a Server Th RNC Management UE 110 4. Click OK, and the system will download version files to fore- ground NE. Once downloading fails, the system will list failure causes, as shown in Figure 18. ‘Confidential and Proprietary Information of ZTE CORPORATION 13(WR RNC Softw are Management Operation Guide TIEN Prerequisites Context Steps FIGURE 18 RESULT OF THE DOWNLOAD To RNC SPEETOEWEVIT PLD TOT ae para agree sr na ponae i] Pee) 02 een FPOA TOS (petaonecuascarntresponse cl 59661 03 060202 EP.0_IOt vs Dpetabnresiest corral reponse ca | BPE: 0296907 FPOAO4 in Sparx eaiaetsnnotiepanse (iva en-gatt BOLD Torro ale eos co al eopose at DDebud a_Devel 0031 BIN Operon eqnetean natresponce at Sparaonraciaetsan not estanse eit Spetatonesuest otra epanse cat (Operon reuestcannatre sparse at aon teqncteon atesponee ct Dree-t=-ovoTae_ePLD~ ease (ootabor esuocatraretonse car Disifaonian-£6LD tee Sparatonagiaetannotesanse eit Dictr-oe0u017FPca wPrnHDLC ‘Oz Opeaten euestca ates Cat -D1-B60101-FPOALP 105. ate est ca ates at eos ELD TOS Dpetabnresiest or ra epanse car END OF steps Part Activating Packages The Software Version Management interface is opened Although it is overlapped with the function of software package ac~ tivating, this function is to make testing become more convenient, This function needs to be hidden if it is used at site. Software package activating is to activate all packages at one time without choice. 1. The Version Package view is opened. Click the Activate Pack button ®, as shown in Figure 19. FIGURE 19 SOFTWARE PACKAGE PART ACTIVATING INTERFACE (eo arse 1S Hownnanas 229 SFM Musca uve a Venue, vewenrissnameer fd a pein Cees aoe febveanso nor i eee Sane nag San 2, Select a version file in the file list from the Choose Version Pack dialog box popped up, as shown in Figure 20. a ‘Confidential and Proprietary Information of ZTE CORPORATIONTIE Chapter 2 Managing Softw are Version Package FIGURE 20 CHOOSE VERSION PACK NTOD_26efware On The Boer MPxe6Sanware On The Board NIc_zsanware on The Board DTEGotvare On The Board (CLK@Sehware On The Board sDTBsanvare On The Board UIM_26oftwere On The Boars) 3. Click OK, and select the NE linked from the Select Managed Element dialog box, as shown in Figure 21 FIGURE 21 SELECT MANAGED ELEMENT Eee @ a Server Th RNC Management UE 110 Cancel ‘Confidential and Proprietary Information of ZTE CORPORATION 15ZAWR RIC Softw are Management Operation Guide TIE Prerequisites Steps 4. Click OK, and the system will activate version files that have been downloaded to foreground NE. Once activation fails, the system will list failure causes END OF steps OMP Initial Version COMP initial version is used for the first time to OMP boards, on which no version is being used. Therefore to attain OMP infor- mation and its version is only to guide programs, input IP ad= dress, username, password, IP directory, and the configuration file's name of the background FTP server. If users do not input these information into the background server, a default value is attained. If OMP board runs improperly, reload the version and recreate OMP initial version, and upload version files to RNC through network cables. The default settings of the OMP are as the following = OMC FTPSVR IP: 0.0.0.0 = OMC FTPSVR UserName: uep = OMC FTPSVR Password: uep = OMC FTPSVR Filepath: empty = OMC FTPSYR Configfile Name: compefg.ini To configure CPU and FPGA versions for OMP loading, after which the background generates a configuration file for the foreground to download according to MO configuration information of the OMP version. To create the OMP initial version, the following requirements must be satisfied: 1. Physical types of version files must be the same. 2. Physical board type, logic board type, version type and func- tional version type of CPU versions’ are _BT_3G_MPX86 or _8T_3G_MPX86_2_LOGIC_OMPDB_CPUID_NOi_VERDB_DE- FAULT_VER. 3. Physical board type, logic board type, version type and func- tional version type of FPGA versions are _BT_3G_MPX86 or _BT_3G_MPX86_2_LOGIC_OMP DB_FPGA_VERMPX86_BOAR- D_FPGA, Creating OMP Initial Version The Software Version Management interface is opened 1. The Version Package view is opened, and click the Create OMP Version button 4, as shown inFigure 22 ie ‘Confidential and Proprietary Information of ZTE CORPORATIONTIER Chapter 2 Managing Softw are Version Package FIGURE 22 OMP INITIAL VERSION CREATION INTERFACE (P RIPAC cornwraccwara ‘pigs see Parone: roman Sa mannoero, Segvsoe soccer ersion Pak oR Swisinriesnunow fa] eran Dscnen fa 2. The Create OMP Version dialog box pops up, as shown in Figure 23, FIGURE 23 CREATE OMP VERSION iz ate OMP version CPL version fle [RNC_RNG_MPXE0_ROMP_x@3_DEW05.00_v309.30.03_ZEIN Left ONP's FEGA Version file [ex@6_02_030700 FPGA 104.16 sd Right OWP's FPGA version fle (MPxa6_00_020700_FPGA_104 cor 7 3. Click OK, and OMP initial version is created. O nore: Users launch the operation of creating OMP initial version on the dient interface, and saving its information in the database after creation succeeds, and putting the generated OMP in- formation files and initial version files under the OMC server's directory (tmp/ftp/common/version). This directory is shared by multi network elements. The initial version created later will cover the result of the previous initial version. END OF STEPS ‘Confidential and Proprietary Information of ZTE CORPORATION 17ZAWR RIC Softw are Management Operation Guide TIE Prerequisites Steps Prerequisites Querying OMP Initial Version The Software Version Management interface is opened 1. The Version Package view is opened. Click the OMP Initial Version Query button #, as shown inFigure 24 FIGURE 24 OMP INITIAL VERSION QUERY INTERFACE Pao fesonre | Eb vaneansor \esenPaerna == SR enn eencieannnee Yeoeossnany fe 2, The OMP Version tab pops up, and results are shown if a record exists in the table, as shown in Figure 25. FIGURE 25 QUERYING RESULT INTERFACE BPROGRA vessior tumation | PackLon | bx|ONPWErSOn | version ype END OF steps Version Package Log Management Displaying Logs The Software Version Management interface is opened 18 Confidential and Proprietary Information of ZTE CORPORATIONTIE Chapter 2 Managing Softw are Version Package Context Version log records such operations as version file downloading and activating, etc, Steps 1. Select the Pack Log tab from the Software Package Man- agement view, as shown in Figure 26. FIGURE 26 LOG INFORMATION DISPLAYING INTERFACE geaoyee DOF STEPS Querying Logs Prerequisites The Software Version Management interface is opened. Steps 1. The Version Package view is opened. Click the Query Ver- sion Files’ Log button %, as shown in Figure 27 FIGURE 27 VERSION PACKAGE QUERYING INTERFACE Ip certqratn Resor > Bf sanonn2aon2e2 2036 Inne conracrscktnsgonert ‘hin te cso Nersoaries name ‘rons fae ‘Confidential and Proprietary Information of ZTE CORPORATION 19EXWR RNC Softrare Management Operation Guide 2. The Query Versi in Figure 28. FIcURE 28 QUERY VERSION FILES’ Filename NanagerElament ID Host P Operstion Narne Operstion result Stat Time a o a O Usertlame a a a End time O vote: TIER n Files’ Log dialog box pops up, as shown. Loc proa2e 7436 a admin = [Adato RNC a [Operation succeeded [wv 2010-06-22 1. 97:20~| 2010-06-22 19.97: 20> To query the version filename is to have fuzzy querying. Users can search out log information only with some characters that are in consistent with the version file, END OF steps 20 ‘Confidential and Proprietary Information of ZTE CORPORATIONChapter 3 RNC NE Software Version Management Prerequisites Context Steps Table of Contents Entering RNC NE Software Version Management Displaying Rack Diagram .. co Displaying NE Running Version Inform ation Displaying NE Common Version Inform ation Displaying NE Special Version Information Displaying NE Log Inform ation .........ee Displaying Board Version Information. Switching OMP Version .......ssec0 Setting OMP Boot Mode... Querying OMP Start Mode... Refreshing Rack Diagram Status Exporting Version Information Entering RNC NE Software Version Management ‘The Software Version Management interface is opened. RNC NE software version management provides operations on a single version file (such as activating, deleting, version testing, and cancel testing, etc), and provides some other relating func tions. 1. Select View > Software Version Managemt > RNC NE Software Version Management from the cli nt interface, and the RNC NE software version management interface is opened, as shown in Figure 29. ‘Confidential and Proprietary Information of ZTE CORPORATION a(WR RNC Softw are Management Operation Guide TIEN FIGURE 29 RNC NE SOFTWARE VERSION MANAGEMENT Dea RE eT END OF STEPS Displaying Rack Diagram Prerequisites The Software Version Management interface is opened Context Software version provides rack diagram interface so that users can conveniently check the present status of versions running on boards as the following: 1. Special status: a special version is running on boards, which is marked in red Inconsistent status: the version running on boards is inconsis- tent with the configuration version, which is marked in blue. 3. Common status: the version running on boards is consistent with the common version, which is marked in green 4. Non-configured status: boards are improper or do not belong to boards of background configuration version file, which is marked in grey. Steps 1. Put the mouse on boards and board version's hint inform ation is displayed, as shown in Figure 30. FIGURE 30 BOARD VERSION HINT INFORMATION INTERFACE Tm Siancard eevee ee fee TE a Ta 1S 6 a7 age Rasce SE 2 ‘Confidential and Proprietary Information of ZTE CORPORATIONTIER Prerequisites Context Steps Prerequisites Context Steps Chapter 3 RNC NE Softw are Version Management O vote: Inconsistent version numbers are shown if the running version of boards is inconsistent with its configuration version number. END oF steps Displaying NE Running Version Information The RNC NE Software Version Management interface is opened. To display NE running version information is to attain all NE running versions’ information through real time querying at foreground 1. Click the Running Version tab, and NE running versions’ in- formation is shown as Figure 31. FIGURE 31 INFORMATION QUERYING RESULT INTERFACE Rule eALoeraaLT BeFAlLT Fran rau cs. Au HULTCOREWuLTORE Eo SefakT EA erLn-ioar END oF steps Displaying NE Common Version Information ‘The RNG Software Version Management interface is opened To display NE common version information is to attain all NE common versions’ information through real time querying at foreground, 1. Click the Common Version tab, and NE common version in- formation is shown as Figure 32) ‘Confidential and Proprietary Information of ETE CORPORATION 23(WR RNC Sofevare Management Operation Guide TIE Prerequisites Context Steps Prerequisites Context FIGURE 32 QUERYING RESULT INTERFACE (INC VEseiverevesionmenesenenT | [esetoxsne] Lecanowsine|vesintor [| —Fonmonion [#00] END OF steps Displaying NE Special Version Information The RNG NE software version management interface is opened, To display NE special version information is to attain all NE special versions’ information through real time querying at foreground Users can cancel special version switching through mouse right= dick menu. 1. Click the Special Version tab, and NE running versions’ infor- mation is shown as Figure 33 FIGURE 33 QUERYING RESULT INTERFACE Raqesrewsioncr no | Pst porenge | veda! oartype | version use| Funcion ren Wee END OF steps Deleting Versions The RNG NE Software Version Management interface is opened, To delete versions is to delete foreground version files that are not used as common or special ones, and these files can be deleted in batch. 2 ‘Confidential and Proprietary Information of ZTE CORPORATIONTIED Chapter 3 RIC NE Sofbv are Version Management Steps 1. Right dick Delete Version to select the versions to be deleted from the NE Version Information Displaying interface, as shown in Figure 34. FIGURE 34 DELETE VERSION er “reais | rarsrson | cxrmonvesen [Seda aon | jouay ol ‘MICROCODE | = E95 DEFAULT Nm Seo Ue = ee PRE Rae cru (OPULDEFAULT (25x INA END oF steps Displaying NE Log Information Prerequisites The RNC NE Software Version Management interface is opened. Context To display operation log information of all version files under this NE. Steps 1. Click the Log Informa shown as Figure 35. n tab, and the NE log information is ‘Confidential and Proprietary Information of ETE CORPORATION 25EXWR RNC Softrare Management Operation Guide TIEN FIGURE 35 QUERYING RESULT INTERFACE enoag [orenmnme [an END OF steps Querying NE Log Information The RNG NE Software Version Management interface is opened, Steps 1. Click the Query Version Files’ Log button # to query NE version log information, as shown in Figure 36 FIGURE 36 INFORMATION QUERYING INTERFACE net 1830030 — Oper 2. The Query Version Files’ Log dialog box pops up, as shown in Figure 37. 26 Confidential and Proprietary Information of ZTE CORPORATIONTIED Chapter 3 RIC NE Sofbv are Version Management FIGURE 37 QUERY VERSION FILES’ Loc O fFilenarns Os Patthno Os Host iP (10.128.74.126 =] OsoUserName [acrnin ¥) 1 Operstion Name [Ace ta RNC T) 1 Operation result [Operation succeeded ¥] CS Start Time 2010-06. a End Time. 2010-06-22 19: 65:29 ¥| = O nore: Users do not need to input specific character string as for ver- sion filename’s and version package number's querying is to have fuzzy querying END oF steps Displaying Board Version Information Prerequisites The RNC NE Software Version Management interface is opened. Context To provide such three tabs as the Operation Version tab, the Special Version tab, and the Backup Version tab. Steps 1. Right click Check Board Version Information to select boards from the Rack Map tab, as shown in Figure 38, ‘Confidential and Proprietary Information of ZTE CORPORATION 27EXWR RNC Softrare Management Operation Guide TIEN FIGURE 38 BOARD VERSION INFORMATION QUERYING INTERFACE Tr Slandare aaael S25 SS eee ef eee ee Cig Resor END OF STEPS Running Version Interface Prerequisites The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played: Context 4 comparison view of the operation version and the configuration version is provided. Steps 1. Select the Running Version tab, and boards! running version information is shown as Figure 39 FIGURE 39 INFORMATION QUERYING RESULT INTERFACE =n Praontne (> | yes Ed econ wintee Ed END OF STEPS 28. Confidential and Proprietary Information of ZTE CORPORATIONTIER Prerequisites Context Steps Prerequisites Context Steps Chapter 3 RNC NE Softw are Version Management Special Version Interface The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played. ‘A comparison view of the special version and the common version is provided. 1. Click the Special Version tab, and boards’ special version in- formation is shown as Figure 40. FIGURE 40 QUERYING RESULT INTERFACE aaoaa END OF STEPS Refreshing Versions The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played. To refresh versions is to refresh board version information, and at real time to attain the running version, the common version, the special version and the backup version of the board 1, Select correspondent boards from the Special Version tab, and dick Refresh Version, as shown inFigure 41, ‘Confidential and Proprietary Information of ZTE CORPORATION 23,(WR RNC Softw are Management Operation Guide TIEN FIGURE 41 REFRESH VERSION ENTRANCE ([Busialtonse [Loncattonains | Veoniro [conte |[_reresne._] ———J bo at) The Ok dialog box pops up, as shown in Figure 42. FIGURE 42 OK DIALOG BOX @ Are you sure you want to continue? OK Cancel 3. Click OK and return to the Running Version tab, as shown in gure 43 FIGURE 43 VERSION REFRESHING RESULT INTERFACE (_Phasieateoneuee | —Loaeaiboaaipe eriontee | varia ree ‘0 ‘VAIN OHDOT — [5 ire? Dera Fre waa ree 2 Re IneRooaDe ‘Yas oapmeno0 ie? erat suoreoH uae END OF STEPS Upgrading Versions Prerequisites The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played: Context To upgrade versions is to upgrade the special version into the com- mon version. After upgrading succeeds, all specified types of chips will run this common version, whose status will be changed into common. Steps 1. Select correspondent boards from the Special Version tab, and click the Set to Common button, as shown in Figure 44. 30 Confidential and Proprietary Information of ZTE CORPORATIONTIE Chapter 3 RNC NE Software Version Management FIGURE 44 VERSION UPGRADING INTERFACE Pyscalinavins| Cogctonhee | —vsenipe | —vesonti | Reteotwe_] 2. The Ok dialog box pops up, as shown in Figure 45. FIGURE 45 Ox DIALOG Box @ Are you sure you want to continue? OK] [Caneat_] 3. Click OK, and the Cancel Special Version Switch Result window pops up, as shown in Figure 46. FIGURE 46 CANCEL SPECIAL VERSION SWITCH RESULT al nt END OF STEPS ‘Confidential and Proprietary Information of ZTE CORPORATION 31.ZAWR RIC Softw are Management Operation Guide TIE Prerequisites Context Steps Cancelling Test The RNG NE Software Version Management interface is opened, and the Check Board Information interface is dis- played: After the default board is rebooted, the background will send the special version switching information to the foreground. After test cancellation succeeds, the specifies chip of the defined board will run the common version again, and the testing version’s status will be switched into backup. 1, Select correspondent boards from the Special Version tab, and click the Cancel Special Version button, as shown infigure 47 FIGURE 47 CANCELLING TEST INTERFACE ewonnio.—] [Retest The Ok dialog box pops up, as shown in Figure 48. FIGURE 48 OK DIALOG BOX @ Are you sure you want to continue? OK] [Caneat_] 3. Click OK, and the Cancel Special Version Switch Result window pops up, as shown in Figure 49. 2 ‘Confidential and Proprietary Information of ZTE CORPORATIONTIE Chapter 3 RNC NE Software Version Management FIGURE 49 CANCEL SPECIAL VERSION SWITCH RESULT DOF STEPS Backing Up Version Interface Prerequisites The RNG NE Software Version Management interface is opened, and the Check Board Information interface is dis- played. Context A comparison view of the backup version and the common version is provided. Steps 1. Select the Backup Version tab, and the backup board ver- sions’ information is shown as Figure 50. ‘Confidential and Proprietary Information of ZTE CORPORATION 33EXWR RNC Softrare Management Operation Guide TIEN FIGURE 50 QUERVING RESULT INTERFACE [Rrmnpareen| connor [ Sean | arin | Fan [Euston orabetieo|_—Yronioe [iano — [Ame] Py a ICROCGOE V3 08 0839078000 | patna rrsvateatiys [) ) a a | a | | | Mesormaieine [Od END OF steps Activating Versions The RNG NE Software Version Management interface is opened, and the Check Board Information interface is dis- played: Context when the default board is restarted, and the backup version can be activated. The background sending software activation require- ment to the foreground and version activating succeeds, all spec- ified types of chips will run the defined version, whose status is switched into common. Steps 1, Select correspondent boards from the Backup Version tab, and click Activate Version, as shown in Figure 51 FIGURE 51 ACTIVATE VERSION INTERFACE ‘oe sn aFOTEDHT The Whether to reset Board dialog box pops up, and select Yes or No as needed, as shown in Figure 52. 34 Confidential and Proprietary Information of ZTE CORPORATIONTIE Chapter 3 RNC NE Software Version Management FIGURE 52 WHETHER To RESET BOARD DIALOG BOX Cine) Whether resetat once [Yes |= No 3. Click OK, and the Ok dialog box pops up, as shown inFigure 53 FIGURE 53 OK DIALOG BOX @ ‘Are you sure you want to continue? 4. Click OK, and the Common Version Switch Result interface ops up, and the version activating result is shown in Figure 54. FIGURE 54 COMMON VERSION SWITCH RESULT EL | END oF steps ‘Confidential and Proprietary Information of ZTE CORPORATION 35(WR RNC Softw are Management Operation Guide TIEN Testing Versions Prerequisites The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played: Context After users select boards to be rebooted or not, the backup ver- sion can be tested and the background sends software special ac- tivation requirement to the foreground. After version testing suc~ ceeds, the specified chip of defined boards will run the specified software version, whose status is switched into special Steps 1, Select correspondent boards from the Backup Version tab, and click the Set to Special button, as shown inFigure 55. FIGURE 55 VERSION TESTING ENTRANCE Frys noose | cogialinardhpe | —venionige | —veunn acne] ae? ae a0 ———— aE? Par mcrocone ——vauesnoroi00 [pros The Special Version Switch dialog box pops up, and select Yes or No from Whether Reset At Once as needed, as shown infigure 56 FIGURE 56 SPECIAL VERSION SWITCH Physical index (only availabl../0 ¥ Whether reset atonce [Yes iad 3. Click Ok, and the OK window pops up, as shown infigure 57. FIGURE 57 OK DIALOG BOX @ ‘Are you sure you wantto continue? 4. Click OK. The Special Version Switch Result window pops up, and the version testing result is displayed, as shown in gure 58 36 Confidential and Proprietary Information of ZTE CORPORATIONTIE Chapter 3 RNC NE Software Version Management FIGURE 58 SPECIAL VERSION SWITCH RESULT a eT) END OF STEPS Deleting Versions Prerequisites The RNG NE Software Version Management interface is opened, and the Check Board Information interface is dis- played. Context To delete versions is to delete foreground version files that are not needed any more, Steps 1. Select correspondent boards from the Backup Version tab, and dick the button Delete Version, as shown in Figure 52 FIGURE 59 DELETE VERSION INTERFACE Pyke boarlipe [Lapel toate [_—wesionyge —[ —vewinna —][_acwateve._] or Re or 3 130 0 2. The Ok dialog box pops up, as shown in Figure 60. ‘Confidential and Proprietary Information of ZTE CORPORATION 37ZAWR RIC Softw are Management Operation Guide TIE FIGURE 60 OK DIALOG BOX @ ‘Are you sure you wantto continue? Cancel 3. Click OK, and the All Results interface pops up, as shown infigure 61 FIGURE 61 ALL RESULTS END OF STEPS Switching OMP Version Prerequisites The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played: Context —OMP version switching is to write version files into OMP flash, and the foreground does not write data tables. Compared with other peripheral boards, OMP version switching is special, and the RPU module has no specified version switching. Steps 1. Click the Version Activate button from the Backup Version tab on the OMP board, and the OMP Version Switch dialog box pops up, as shown in Figure 62. 38 Confidential and Proprietary Information of ZTE CORPORATIONTIE Chapter 3 RNC NE Software Version Management FIGURE 62 OMP VERSION SWITCH Lennitocetposon (oT Gfromonses =) ea) een = 2. Click OK after selecting whether reset at once and the position of the right and left boards from the OMP Version Switch dialog box. END OF STEPS Setting OMP Boot Mode Prerequisites The RNG NE Software Version Management interface is opened, and the Check Board Information interface is dis- played. Context Users can launch operations of setting OMP starting mode on the interface. OMP boot mode falls into boards booting and back- ground booting. Steps 1. The NE Version Management view is opened, and click the Setting OMP Boot Mode button #, as shown in Figure 63. FIGURE 63 SETTING OMP BOOT MODE INTERFACE (Fave | Fumingverson Commenvesin | Stedalversin 2. The Select OMP Boot Mode dialog box pops up, and select boot mode as needed, as shown inFigure 64. ‘Confidential and Proprietary Information of ZTE CORPORATION 33(WR RNC Sofevare Management Operation Guide TIE FIGURE 64 SELECT OMP BOOT MODE Sele:t RNC boot mode [Boot trom hoard |= [Boot ror OMe: 3. Click OK, and the OMP boot mode is created successfully. END OF Stes Querying OMP Start Mode Prerequisites The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played: Context Users can launch an operation of querying foreground boot mode on the interface. Steps 1. The NE Version Management view is opened, and dlick the RNC Board Boot Mode Query button @, as shown inFigure 65. FIGURE 65 RNC BOARD BOOT MODE QUERY |(Feckiew | Runntavesion | Commonversian | Spedaverson The RNC Board Boot Mode Query dialog box pops up, and the querying result is shown as Figure 66. FIGURE 66 RNC BOARD BOOT MODE QUERY erie Board boot mode of RNC is: Boot fram boars END OF steps 40. Confidential and Proprietary Information of ZTE CORPORATIONTIER Prerequisites Context Steps Prerequisites Context Steps Chapter 3 RNC NE Softw are Version Management Refreshing Rack Diagram Status The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played. Rack diagram status refreshing is to refresh rack map status and at real time attain RNC NE information of all running versions, com= mon versions, special versions and backup versions. 1. The NE Version Management view is opened, and click the Refresh Rack State button®, as shown inFigure 67. FIGURE 67 REFRESH RACK STATE INTERFACE ((Beckvem (Runningverson (Common version | Sreaverson D_OF STEPS Exporting Version Information The RNC NE Software Version Management interface is opened, and the Check Board Information interface is dis- played. To export version information is to export data from a table in the specified present page so as to back up contents of the running version, the special version, the backup version, and version logs, ete. 1. The NE Version Management view is opened, and click the Export button, as shown in Figure 68. FIGURE 68 EXPORTING OPERATION INTERFACE ae eo & (eke | Furi sin | Coron vesion | Sede vecon 2. Click and select to input the excel filename to be saved from the Local Path Choose dialog box popped up, as shown in Figure 69. ‘Confidential and Proprietary Information of ZTE CORPORATION 41.EXWR RNC Softrare Management Operation Guide TIE FIGURE 69 LOCAL PATH CHOOSE see eoeae Ow musie (wy Pictures My Fea (D ve.02.2002 version Prostasite O Wersion Infosds Fiesorype. [rx 3. Click Save, and the Hint dialog box pops up, and the exporting result is shown in Figure 70. FIGURE 70 HINT INTERFACE @ Success to export file, OK END OF steps 42. Confidential and Proprietary Information of ZTE CORPORATIONFigures Figure 1 Resource Status Transfer Map ...... 2 Figure 2 Entering Software Management View 4 Figure 3 RNC Software Pack Management... 4 Figure 4 Create Version Pack View 5 Figure 5 File Path Selection 6 Figure 6 Version Pack Information Interface 6 Figure 7 Result Interface .. cestisnneneanneee 7 Figure 8 Software Package Downloading Interface......... 8 Figure 9 Select Managed Element. 8 Figure 10 Result Of the Download To RNC 8 Figure 11 Software Package Activating Interface a) Figure 12 Select Managed Element 10 Figure 13 Deleting Version Package Interface ..... ed Figure 14 Patch Package Deleting Interface eesetveneee Td Figure 15 Software Package Part Downloading Interface .........12 Figure 16 Choose Version Pack...... 12 Figure 17 Select Managed Element 213 Figure 18 Result Of The Download To RNC cecetsennee Figure 19 Software Package Part Activating Interface ......c014 Figure 20 Choose Version Pack ..... 1S Figure 21 Select Managed Element 1S Figure 22 OMP Initial Version Creation Interface 17 Figure 23 Create OMP Version cece 17 Figure 24 OMP Initial Version Query Interface. 18 Figure 25 Querying Result Interface ce 18 Figure 26 Log Information Displaying Interface... 219 Figure 27 Version Package Querying Interface 219 Figure 28 Query Version Files’ Log - 20 Figure 29 RNC NE Software Version Management. 122 Figure 30 Board Version Hint Information Interface .......see022 Figure 31 Information Querying Result Interface 223 Figure 32 Querying Result Interface 224 Figure 33 Querying Result Interface 224 Figure 34 Delete Version .. 225 Confidential and Proprietary Information of 2TE CORPORATION 43ZAWR RIC Softw are Management Operation Guide TIE Figure 35 Querying Result Interface ....csssssesseseessssseesenesn 26 Figure 36 Information Querying Interface \...sscssesseseeeenen 26 Figure 37 Query Version Files’ LOg .ss.cssssssssssseteessesseeennssen 27 Figure 38 Board Version Information Querying Interface .........28 Figure 39 Information Querying Result Interface .....secess028 Figure 40 Querying Result Interface ...scsssssesseteessssseeeeen 29 Figure 41 Refresh Version Entrance ....scsssssessetessesseeeneen 30 Figure 42 Ok Dialog BOX .sssscsccsesssseesetsssessetennssnsseesinnen3O Figure 43 Version Refreshing Result Interface .....cssesseeeen 30 Figure 44 Version Upgrading Interface... SD Figure 45 Ok Dialog Box ...ssscssseesssseeenssssseseetsesssnseeeessen SD Figure 46 Cancel Special Version Switch Result.....ssssecese 3D Figure 47 Cancelling Test Interface ...ccssssesscssetsessssseeenessen 32 Figure 48 Ok Dialog BOX ..s.sscssseesssseeenessesseseetsssssnseeenessene32 Figure 49 Cancel Special Version Switch Result .....sssscee 33 Figure 50 Querying Result Interface ...scsssssesseesenseeenne SF Figure $1 Activate Version Interface ....ssssssessesesssnseeennen 4 Figure 52 Whether To Reset Board Dialog BOX sas.ssseseesenen 3S Figure $3 Ok Dialog BOX .ssssessssesssseeensssesseteessssseesnen 3S Figure 54 Common Version Switch ReSUlt sss... 3S Figure $5 Version Testing Entrance ....scssessesseteesseseeeensen 36 Figure 56 Special Version Switch ...ssccscssssssesseteessesseeeinen 36 Figure $7 Ok Dialog Box sss... cssettssnneesetecisseneees36 Figure $8 Special Version Switch RESUIt....scsscsessssseeeeen 37 Figure 59 Delete Version Interface .....scsessesseteessssseesinn 37 Figure 60 Ok Dialog BOX ...sssescssesssseeeetsssesseteissesseeeieen 38 Figure 61 All RESUItS ...cccsssseecssssssseeeetsssessetenessssseesinsn 38 Figure 62 OMP Version Switch ...csssccsesssssssseteessesseeeisen 39 Figure 63 Setting OMP Boot Mode Interface ....cseiesssseeeee 39 Figure 64 Select OMP Boot Mode .s.ssessetssessessetenessesseeeninen 40 Figure 65 RNC Board Boot Mode QUETY...rs.sssssetesessssseteeneen 0 Figure 66 RNC Board Boot Mode QUETY...rs.sssssesessssseteeeeen 40 Figure 67 Refresh Rack State Interface ..aicssessetessesseeeen Al Figure 68 Exporting Operation Interface ....s.esscseesssseeeessen Al Figure 69 Local Path ChOOS€ -..cscsssseeessssssssseetsnsesnseeenesssne 2 Figure 70 Hint Interface ....sscsccsssssseeenessssseseetsssssnseesnsssne 2 144 Confidential and Proprietary Information of ZTE CORPORATIONTables ‘Confidential and Proprietary Information of ZTE CORPORATION 45