This document is posted to help you gain knowledge. Please leave a comment to let me know what you think about it! Share it to your friends and learn new things together.
Nokia Solutions and Networks is continually striving to reduce the adverse environmental effects of itsproducts and services. We would like to encourage you as our customers and users to join us inworking towards a cleaner, safer environment. Please recycle product packaging and follow therecommendations for power use and proper disposal of our products and their components.
If you should have questions regarding our Environmental Policy or any of the environmental services
we offer, please contact us at Nokia Solutions and Networks for additional information.
4.1 Downloading from PC to BSC ................................................................................................ 7 4.2 Downloading from NetAct ....................................................................................................... 8
4.2.1
Copy files to NetAct by media drive ......... ......... ......... ......... ......... .......... ......... ......... ......... . 8
4.2.2 Copy files to NetAct by ftp.................................................................................................. 8 4.3 Checking the CDTEMP directory ............................................................................................ 9
5.1.1 Copying data of files with ZDEM to the new file ............................................................... 10 5.1.2 Adding the SW Update to existing package ......... ......... ......... ......... ......... ......... ......... ...... 11 5.1.3 Copy manually the ESBB26GX and ESBB2DGX file to the LFILES in Flexi BSCand BSC3i models ..................................................................................................................... 12 5.1.4 Copy manually the BJCACPLD.ZIP and BCNHIGIG.ZIP file to the LFILES inmcBSC and Flexi BSC ............................................................................................................... 12 5.1.5 Creating a new package .................................................................................................. 12
5.1.6 Selecting the new package as active ............................................................................... 12 5.1.7 Run BTFCNVSB conversion for BTF_BGSX file and copy POCIPXZZ data tonew file ....................................................................................................................................... 12
5.2 SW Update installation on a running S16.1 package ........ ......... ......... ......... ......... ......... ....... 14 5.2.1 Copying data of files with ZDEM to the new file ............................................................... 14 5.2.2 Adding the SW Update to the running package ........ ......... ......... ......... ......... ......... ......... . 15 5.2.3 Copy manually the ESBB26GX and ESBB2DGX file to the LFILES in Flexi andBSC3i 15 5.2.4 Copy manually the BJCACPLD.ZIP and BCNHIGIG.ZIP file to the LFILES inmcBSC and Flexi BSC ............................................................................................................... 16 5.2.5 Deleting MENUES*.MIF files ........................................................................................... 16 5.2.6 Creating a new package .................................................................................................. 16 5.2.7 Selecting the new package as active ............................................................................... 16 5.2.8 Run BTFCNVSB conversion for BTF_BGSX file and copy POCIPXZZ data tonew file ....................................................................................................................................... 16 5.2.9 Checking of the package consistency .............................................................................. 17
5.3 Activation of the new package ........ ......... ......... ......... ......... ......... ......... .......... ......... ......... .... 18 5.4 Special Instructions for BSC3i and Flexi BSC ...................................................................... 19
5.4.1 Special instructions for BSC3i and Flexi BSC for TG4_EXSX ......... ......... ......... ......... ...... 19 5.4.2 Blackbox service terminal extension BOXANAGX workaround ........ ......... ......... ......... ..... 23 5.4.3 Updating embedded software of ETP .............................................................................. 23 5.4.4 Updating embedded software of ETIP1-A ........................................................................ 24 5.4.5 Updating Advantech CP1D-A BIOS SW .......................................................................... 26 5.4.6 Updating instructions for ESB24-D switch software ......................................................... 28 5.4.7 Updating instructions for HWAT-B switch software .......................................................... 34
ZDEM after ZWNA19-Sep-2013 6.0 ABI_BXSX information updated to ZMXV, ZMXP20-Sep-2013 7.0 Modify Note before CPLD update25-Sep-2013 8.0 Corrected CP1D-A info and add one syntax to
5.5.421-Nov-2013 9.0 Add special instructions for mcBSC TG4_MBSX13-Jan-2014 10.0 Add BOXANAGX special instructions
It is highly recommended that a safecopy of the active package be made prior to SWUpdate installation. The safecopy can be made by following the document Safecopying inBSC. The safecopy document can be found from NED.
3. PREPARATIONS
Software Update can be installed with Software Update Installation macro.The macro can be run with HIT (Holistic Integration Tester) software tool. The HITsoftware is a Microsoft Windows® based tool, which automates most of the tasksnecessary for the Software Update installation.
The latest version of BSC Software Update installation macro can be found from ownmacro page on NOLS under Software release S16.1.Title: S16.1 Software Update installation macroID: CDinstall_macro_ver
The following table describes the HIT macro name and minimum version of macro whichis required for installation of this Software update. The macros have been designed tooperate with HIT versions 2.10-3 swup on Windows XP, Windows 2000 and Windows 7.
ThThe macro can be used for singl e or multipl e SW update installation on the top ofrunning S16.1. package with a local (LAN/Telnet/MML) or a remote (NetAct)connectio n. The latest version of macro is always com patible with earlier releasedBSC Maintenance or Enhancements packages.
Installation durin g S16.1 SW upgrade is to be performed when th e upgrade macro is
infor ming th e user to do the CD installation manually. In this phase, user must o pen
S16.1 HIT Macro File The main task of the macro
CD_Installation.hit v.6.6-8 or newer Basic Software Update installationCD_Special_S16.hit v.6.6-9 or newer Contains Software Update specific functions
(file copy, conversions, special restarts etc.)CD_special_S14.hit Mandatory , but not used
new HIT session to separate wind ow and ru n the CD installation macro. Whenmacro asks " Do you w ant to select destinatio n package (BU/NW)?" answer YES and
select NW package. Af ter th e CD has been inst alled, c lo se the HIT u sed for CD ins tal lat io n and proceedwith th e actual upgrade in the upgrade windo w.
Before starting the Software Update installation macro copy ALL four macros under samedirectory on your LapTop. Open CD_Installation.hit macro with HIT-tool and press a greenarrow to start macro and follow instructions of macro. The installation macro recognizesfirst the type of BSC and then installs software modules from correct directory (M92 orM98 or FLE) from ZIP file.
When using the HIT, the MML commands are executed automatically. It is not necessaryto type any commands until it is specifically requested by HIT. Installation logs are savedto the same directory where HIT Macro Files are.
When using the HIT for Software Update installation, these instructions can be followedfor a more detailed description of the different phases, which take place during theinstallation.
NOTE: The commands executed by the HIT macro do not always match exactly with thecommands presented in the manual. This is because sometimes the automated tasks ofthe HIT macro require more commands and different command syntaxes, than arepresented in the manual.
3.1 Prerequisites
The installation of this SW Update requires a basic knowledge of the DX200 equipment.Please see the following table for more information on pre-requisites on different networkelements.
NetworkElement
Pre-requisite
BSC S16.1 3.5-0 SW packageTCSM No special requirementsBTS No special requirementsSGSN No special requirementsMSC No special requirementsOSS No special requirements
3.1.1 Printout the topol ogy information
New version of topology file has been included to the CD and because of thecorrection the files are taken to use without conversion. So user need to check andprintout the current topology information to be able to add same data back if the topologyhas been modified manually.
Printout the current topology information with MML command:
ZW6I;
Modify the data after new SW package activation, the step you can find in chapter5.4.1
3.2 Checking preconditions
To ensure that the active package is correct, it is recommended that package verificationbe performed prior to the SW Update installation. The package verification can be donewith the MML-command:
ZWQB:NAME= <S16.1_package> :FORM=FAILED;
Note! If some modules fail, find out why they failed and correct the failures beforeproceeding to the installation.
Check if the directory, where this SW Update is going to be installed, includes two createdpackages. If the directory includes two packages, delete the non-default one.
Delete all the non-default file versions from the active S16.1. package with the commands:
Note! Remember to use the parameter FF at the end of the following commands. If theparameter FF is not used, the command deletes everything from that directory!
Note ! The ZIP file contains three files, which are not BSC software but used for DATcreation with DATTAP32 program. Those files are not necessary to be copied to BSC, butare not causing any problems if they are copied. The files in question are *.bat, *.cnf and*.lis.
Remove files from SWupdate sub-directory (FLE or M98 or M92):ZIWD: <bsc> ,OMU:WS,NODEF:FTPTMP, <SoftwareUpdate_ID>,<FLEorM98orM92> :%,%;
The Software Update can be copied from NetAct using the "SOFTWARE MANAGER "application. For more information on this procedure, see the OSS document "SOFTWAREMANAGER HELP".
4.2.1 Copy files to NetAct by media drive
Insert the media (i.e. DAT/CD/DVD) into the NetAct communication server drive and copyfiles to /var/opt/nokiaoss/admin/swmgmt/swtemp -directory. Give access for importing bycommand chmod -R 777 <corresponding directory> .
Start the Software Manager application, select SW Archive and BSC S16.1 ChangeDeliveries from the toolbar. Select IMPORT NEW SW package action.
After importing, select Network SW Status and choose correct Network Element whereyou want install the Updates. Choose New task toolbar and click correct Task type , SW
type and SW package .
Click Start TASK to download the Software Update into the BSC CDTEMP directory. Afterdownloading, continue the Software Update installation procedure.
4.2.2 Copy files to NetAct by f tp
Copy Software Update zip file to your computer (i.e. C:/temp/). Open command promptwhere the Software Update zip is or when extracted (C:/temp/S16.1 CDxx/ M98 (BSC3ivariants) or FLE (FlexiBSC)).
Open connection to OSS server by command ftp <IP address of NetAct server> (login
Go to swtemp directory using command cd /var/opt/nokiaoss/admin/swmgmt/swtemp .
Give access for importing by command chmod -R 777 <correspondi ng director y> .
Create a new directory for your files mkdir <name of directory>
Go to the directory created cd <name of directo ry>
Set bin mode on by command bin
Set checksum on by command has
Give command prompt
Copy all files from directory by command mput *
After the files have been copied, give command by e to log off from NetAct server.
Start the Software Manager application, select SW Archive and BSC S16.1 ChangeDeliveries from the toolbar. Select action IMPORT NEW SW package .
After importing, select Network SW Status and choose correct the Network Elementwhere you want install the Software Update. Choose New task toolbar and click correctTask type , SW type and SW package .
Click Start TASK to download the Software Update to the corresponding BSC CDTEMPdirectory. After downloading , continue Software Update installation procedure.
4.3 Checking the CDTEMP directory
The amount and the checksums of the modules in CDTEMP directory are to be checkedthrough this step. The checking is done with the following commands:
Depending on content of SW update printout might show NO PI D STRI NG or CHECKSUMVERI FI CATI ON NOT POSSI BLE , because some modules used by the system do notcontain checksum information since they are not in conventional DX 200 file format. Such
files are e.g. CFL, AQL, OCT, ESBB****.BIN files. If some other files fail, find out why theyfailed and correct the files before proceeding with the installation.
Note! Printouts of checksums of the modules in CDTEMP directory can be found fromchapter 8 Appendices/References end of the document.
Checksums and versions of modules in CDTEMP-directory can be listed with followingcommand:
Note ! The ZIP file contains three files (*.bat, *.cnf and *.lis), which are not BSC software
but used for DAT creation with DATTAP32 program. Those files are not necessary to becopied to BSC, but are not causing any problems if they are copied.
5. SW UPDATE INSTALLATION
5.1 SW Update installation dur ing S16.1 upgrade
The status of the S16.1 package must be NW. If it’s not, change the S16.1 package statuswith the command:
ZWSC:NAME= <S16.1_package> :STAT=NW;
Note! If multiple Maintenance packages are installed, check running conversionsinstructions of each package and execute all required conversions with correct packagespecific files.
5.1.1 Copying data of files wit h ZDEM to the new file
Create the temporary directories (if not exist):ZIWL::WS,NODEF: <new_S16.1_directory> :SRCTMP,FF,02,XX;ZIWL::WS,NODEF: <new_S16.1_directory> :CNVTMP,FF,02,XX;
If directories already exist, empty them:ZIWD::WS,NODEF: <new_S16.1_directory> :SRCTMP,:%,%;
ZIWD::WS,NODEF: <new_S16.1_directory> :CNVTMP,:%,%;Copy original files from LFILES to SRCTMP (conversion source directory):ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /LFILES,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /SRCTMP,DRIVE=WDU-S,;ZIBC:,,DXPFILGX,IMG;ZIBC:,,MEF%,IMG;ZIBC:,,BAW_BGSX,IMG;ZIBC:,,BXW_BGSX,IMG;ZIBC:,,CIT_BGSX,IMG;ZIBC:,,TDP_BGSX,IMG;ZIBC:,,BTF_BGSX,IMG;ZIBC:,,POCIPXZZ,IMG;
Copy original MAFILE file from BLCODE to SRCTMP:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /BLCODE,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /SRCTMP,DRIVE=WDU-S,;ZIBC:,,MAFILEGX,IMG;
Copy new files from CDTEMP to CNVTMP:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /CDTEMP,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /CNVTMP,DRIVE=WDU-S,;ZIBC:,,BAW_BGSX,IMG;ZIBC:,,BXW_BGSX,IMG;ZIBC:,,CIT_BGSX,IMG;ZIBC:,,TDP_BGSX,IMG
Check the status of the created packages with the command:ZWQO:CR;
5.1.6 Selecting the new package as active
In this step, the new package is selected to be an active package in the directory. Thepackage can be switched to active through the following command:
ZWSS:NAME=<new_package>;
The command changes the status of the packages following way:
Old S16.1 package NW -> UTNew S16.1 package UT -> NWCheck the status of packages with the command:
ZWQO:CR;
5.1.7 Run BTFCNVSB conversion for BTF_BGSX fil e and copy POCIPXZZ data tonew file
Copy MEFILE from LFILES to CNVTMP from running package:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /LFILES,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /CNVTMP,DRIVE=WDU-S,;ZIBC:,,MEF%,IMG;
Copy original MAFILE file from BLCODE to CNVTMP:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /BLCODE,DRIVE=WDU-S,;
Run BTFCNVSB conversion to convert data from old file to new file:ZDEY:S:I:OMU:/ <new_S16.1_directory> /SRCTMP:WDU-S;ZDEY:D:I:OMU:/ <new_S16.1_directory> /CNVTMP:WDU-S;
Check OMU computer logs, log should be empty:ZDDE:OMU:"ZGSC";
Copy original BTF_BGSX from SRCTMP to LFILES:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /SRCTMP,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /LFILES,DRIVE=WDU-SB;ZIBC:,,BTF_BGSX,IMG;ZIBC:,,POCIPXZZ,IMG;
5.2 SW Update installation on a running S16.1 package
Note! If multiple Maintenance packages are installed, check running conversionsinstructions of each package and execute all required conversions with correct packagespecific files.
5.2.1 Copying data of files wit h ZDEM to the new file
Create the temporary directories (if not exist):ZIWL::WS,NODEF: <new_S16.1_directory> :SRCTMP,FF,02,XX;ZIWL::WS,NODEF: <new_S16.1_directory> :CNVTMP,FF,02,XX;
If directories already exist, empty them:ZIWD::WS,NODEF: <new_S16.1_directory> :SRCTMP,:%,%;ZIWD::WS,NODEF: <new_S16.1_directory> :CNVTMP,:%,%;
Copy original files from LFILES to SRCTMP (conversion source directory):ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /LFILES,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /SRCTMP,DRIVE=WDU-S,;ZIBC:,,DXPFILGX,IMG;ZIBC:,,MEF%,IMG;ZIBC:,,BAW_BGSX,IMG;ZIBC:,,BXW_BGSX,IMG;ZIBC:,,CIT_BGSX,IMG;ZIBC:,,TDP_BGSX,IMG;ZIBC:,,BTF_BGSX,IMG;
ZIBC:,,POCIPXZZ,IMG;
Copy original MAFILE file from BLCODE to SRCTMP:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /BLCODE,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /SRCTMP,DRIVE=WDU-S,;ZIBC:,,MAFILEGX,IMG;
Copy new files from CDTEMP to CNVTMP:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /CDTEMP,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /CNVTMP,DRIVE=WDU-S,;ZIBC:,,BAW_BGSX,IMG;ZIBC:,,BXW_BGSX,IMG;ZIBC:,,CIT_BGSX,IMG;ZIBC:,,TDP_BGSX,IMG;ZIBC:,,DXPFILGX,IMG;ZIBC:,,BTF_BGSX,IMG;ZIBC:,,POCIPXZZ,IMG;
Copy MEFILE from LFILES to CNVTMP from running package:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /LFILES,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16.1_directory> /CNVTMP,DRIVE=WDU-S,;ZIBC:,,MEF%,IMG;
Copy original MAFILE file from BLCODE to CNVTMP:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /BLCODE,DRIVE=WDU-S,;
Copy old data to new file :ZDEY:S:I:OMU:/ <new_S16.1_directory> /SRCTMP:WDU-S;ZDEY:D:I:OMU:/ <new_S16.1_directory> /CNVTMP:WDU-S;ZDEM:BAW_BGSX,IMG;ZDEM:BXW_BGSX,IMG;ZDEM:CIT_BGSX,IMG;ZDEM:TDP_BGSX,IMG
Copy converted files to CDTEMP:ZIWY:S:UNIT=OMU,PATH=/ <new_S16.1_directory> /CNVTMP,DRIVE=WDU-S,;
Through this step, the contents of the SW Update from the CDTEMP directory areautomatically copied to proper directories (BLCODE, LFILES, MMDIRE) according to theCFL list file. The ASWDIR directory is created (if necessary) and the CFL list file is copiedinto it. Also, a new MAFILEGX is created into the BLCODE directory.
A single SW Update can be added to the running package with MML command:
ZWNA:NAME= <running_package_name> :<cd_ind> ;
If more than one SW Update is installed at the same time, give the indexes in sequentialorder, using the &-character as a separator. The indexes must be given in the order inwhich the Updates are to be installed. This is also the order in which the SW Updatecontents are copied to the CDTEMP-directory (the oldest first, the latest last).
The copying can be made according to the instructions described in chapter 5.
Multiple Updates can be added to the S16.1 package with MML command:
When the new software package is installed in BSC, MMI system creates command classmenus to MMDIRE directory. The system does not update menus before following step isexecuted:
Delete MENUES*.MIF files from MMDIRE with MML command:ZIWD:,OMU:WSB,NODEF:<current_SW_directory>,MMDIRE,:MENUES%,MIF;
5.2.6 Creating a new package
The following command creates a new package for the SW Update.
Check the status of the created packages with the command:ZWQO:CR;
5.2.7 Selecting the new package as active
In this step, the new package is selected to be an active package in the directory. Thepackage can be switched to active through the following command:
ZWSS:NAME= <new_package> ;
The command changes the status of the packages following way:
Old package BU -> UTNew package UT -> BU
Check the status of packages with the command:ZWQO:CR;
5.2.8 Run BTFCNVSB conversion for BTF_BGSX fil e and copy POCIPXZZ data tonew file
Copy MEFILE from LFILES to CNVTMP from running package:ZIWY:S:UNIT=OMU,PATH=/ <new_S16_1_directory> /LFILES,DRIVE=WDU-S,;ZIWY:D:UNIT=OMU,PATH=/ <new_S16_1_directory> /CNVTMP,DRIVE=WDU-S,;ZIBC:,,MEF%,IMG;
Copy original MAFILE file from BLCODE to CNVTMP:ZIWY:S:UNIT=OMU,PATH=/ <new_S16_1_directory> /BLCODE,DRIVE=WDU-S,;
The values of SIMQUE and SEQQUE must be zero (0) except next one.If the MMLLOG logical file is connected to a ring file the value of the SIMQUE TOTALLENGHT is 1 for OMU.
Check the file of the MMLLOG connection by MML command.ZIID:<bsc name> ,OMU:MMLLOG,B;
MMLLOG must be connected to BBU-0.
5.3 Activation of the new package
Note! If Multiple Updates are installed, check the activation instructions of eachupdate and execute all required restarts. There may also be some special instructionsfor different Updates, which must be followed.
In order to activate the new package into the system, the system restart is needed. Thesystem can be restarted using the following MML command:
Note! By default, interface units are not restarted when their gateway computer isrestarted. If BSC has STMU, include parameter “:STMU” end of ZUSS- command sothat all interface computers of the STMU type are also restarted. In the same way allconfigured ETPE-, ETPT-, ETPA-, ETPC, ETME, ETMA units must be restarted whentheir gateway computer is restarted.
ZUSS:SYM:C=DSK;
NOTE! In som e configu rations b elow alarms may com e active because of th eTG4_EXSX change
- 2863 UNKNOWN LAN CONNECTION DETECTED- 3292 INTERNAL LAN LINK BROKEN
SEE MORE INFO IN CHAPTER 5.4.1
After BSC has been recovered restart all TCSM3i units one by one with followingcommand:
ZUSU:TCSM, <tcsm_no> :C=TOT;
After the TCSM3i has recovered to WO-EX state, updated software version can bechecked with following commands:
5.4.1 Special inst ruc tions fo r BSC3i and Flexi BSC for TG4_EXSXInstructi ons are needed when installing CD during upgr ade or to the runni ngpackage.
NOTE! In som e configu rations b elow alarms may com e active because of th eTG4_EXSX change
- 2863 UNKNOWN LAN CONNECTION DETECTED- 3292 INTERNAL LAN LINK BROKEN
Modification s to TG4_EXSX files topolo gies are needed after CD activation ONLY incase 1 or 2 or 3 or 4:
1. User has modif ied the active topologies manually with MML command ZW6N
2. The BSC is new delivered Flexi BSC using HW defined Topolo gy T29 List ofLAN port s in S15 first-delivery Flexi BSC cabinet with ETP (Alternative 2)
3. The source SW level duri ng the upgrade is S15 or S16 and topolog y copy whichcan be numb er T30, T31 or T32 excludi ng t he opti on 2 and 4)
4. The OMU separated from O&M LAN feature has been used in S15 site by usingtopol ogy numbers T17-T29 or T31
Use instr uctio ns if n eeded, choose corr ect step 1 or 2 or 3 or 4:
1. Check and modify the topol ogy data manually if needed in case user hasmodif ied the data with MML command ZW6N:
W6N:<operation>:[<topol ogy ind ex>],[<EMB topology ind ex>]:[<unittype>,<unit ind ex>],[<switch role>],[<port s>],[<new unit type>,<new unitindex>]:
[<port i ndex>],[<dest uni t type>,[<dest un it ind ex>|<dest pairindex>,<dest unit index>]]:[<dest piu t ype>,<dest piu ind ex>]:[<dest portindex>]:[<connection type>];
NOTE! In case the T12, T13, T25 or T26 or T29 has been in use before CDinstallations do not make any manual modifications.
2. Active topol ogy needs to be re-selected if new delivered Flexi BSC hastopology based on Use of LAN document Use of LAN Ports in Flexi BSC/Topology T29/ List of LAN ports in S15 first-delivery Flexi BSC cabinet withETP (Altern ative 2) (In Flexi BSC S15 Site NED “ Nokia Siemens Networ ksFlexi BSC, Rel. S15, Site Docum entatio n).
Activate topology T29 after CD installation: ZW6G:T29; .
If the "OMU separate from O&M LAN" ON feature has been used activate withcommand:ZW6K:ENA;
Af ter th e chang es restart OMUZUSU:OMU:C=DSK;
3. Check from b elow list the corr ect BSC model and used PIU types andactivate the topology w ith MML command ZW6G:
ZW6G:<topology>;
Topologies:• T4 for upgraded Flexi BSC with ESB24 (L2/L3) in CPU & PCU LANs and
in EMB LANs.
• T5 for new delivery Flexi BSC with ESB24 (L2/L3) in CPU & PCU & EMBLANs.
• T6 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANs.EMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T7 for BSC3i 1000/2000 with ESB24 (L2/L3) in CPU & PCU & EMB &ETP LANs.
• T8 for upgraded Flexi BSC with ESB24 (L3) in CPU & PCU LANs and inEMB & ETP LANs.
• T9 for new delivery Flexi BSC with ESB24 (L3) in CPU & PCU & EMB &ETP LANs (Alternative 1).
• T10 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANsand ESB24 in ETP LAN and with optical uplinks.EMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T11 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANs
EMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T12 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANsand ESB24 in BSCD cabinetEMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T13 for BSC3i 1000/2000 with ESB26 (L2) in BSCC cabinet and withESB24 in BSCD cabinet.EMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T14 for BSC3i 1000/2000 with ESB24 (L3) in CPU & PCU & EMB & ETPLANs.
• T15 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANs,ESB24 in BSCD cabinet and for ETP LAN and with optical uplinksEMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5]
• T16 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANs,ESB24 in BSCD cabinet and for ETP LAN and with electrical uplinksEMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5]
• T29 for new delivery Flexi BSC with ESB24 (L3) in CPU & PCU & EMB &ETP LANs (Alternative 2).
Af ter th e chang es restart OMU:ZUSU:OMU:C=DSK;
4. If the "OMU separate from O&M LAN" ON feature has been used in previousSW level.
Activate the correct topology with MML command ZW6G and after thatactivate the OMU separated O&M LAN feature with command ZW6K.
Note in S15 site the OMU separated O&M LAN was wi th to polog yindexes T17-T29 and now in S16.1 site the co rrect t opolo gy in dex is -13.ExampleIf in S15 site T19 has been in use, then th e corr ect on e in S16.1 site is T6+ ZW6K:ENA; to act ivate OMU separated O&M LAN.
Choose the correct topology from below list and activate it with MMLcommand ZW6G:ZW6G:<topology>;
Topologies:• T4 for upgraded Flexi BSC with ESB24 (L2/L3) in CPU & PCU LANs and
• T5 for new delivery Flexi BSC with ESB24 (L2/L3) in CPU & PCU & EMBLANs.
• T6 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANs.EMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T7 for BSC3i 1000/2000 with ESB24 (L2/L3) in CPU & PCU & EMB &ETP LANs.
• T8 for upgraded Flexi BSC with ESB24 (L3) in CPU & PCU LANs and inEMB & ETP LANs.
• T9 for new delivery Flexi BSC with ESB24 (L3) in CPU & PCU & EMB &ETP LANs (Alternative 1).
• T10 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANsand ESB24 in ETP LAN and with optical uplinks.EMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T11 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANsand ESB24 in ETP LAN and with electrical uplinks.EMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T12 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANsand ESB24 in BSCD cabinetEMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T13 for BSC3i 1000/2000 with ESB26 (L2) in BSCC cabinet and withESB24 in BSCD cabinet.EMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5].
• T14 for BSC3i 1000/2000 with ESB24 (L3) in CPU & PCU & EMB & ETPLANs.
• T15 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANs,ESB24 in BSCD cabinet and for ETP LAN and with optical uplinksEMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5]
• T16 for BSC3i 1000/2000 with ESB26 (L3) in CPU & PCU & EMB LANs,ESB24 in BSCD cabinet and for ETP LAN and with electrical uplinksEMB LAN port specifications for BSC3i 1000/2000 according to thedocument [5]
• T29 for new delivery Flexi BSC with ESB24 (L3) in CPU & PCU & EMB &ETP LANs (Alternative 2).
Activate the OMU separated O&M LAN feature with command ZW6K:ZW6K:ENA;
Verify that the result of ZWDL command shows SUCCESS, if not enter ZWDL commandagain.
Step 2) Verify that the standby flash software upgrade is successful.
Check the SW version in the standby flash, it should display the new SW version.
ZWDM:UT= <ETP_ type> ,UI=<index> ,MODE=STANDBY;
If the new SW version is displayed, switch the new software on standby flash active.Use command ZWDS switch upgraded flash as ACTIVE flash on the ETP card.
After this the upgraded flash with new software should be as the ACTIVE flash of the ETPcard and old software on STANDBY state displayed ZWDM command.
Repeat ETP software upgrade (ZWDL-mml) as in Step 1 to other flash of the ETP cardand verify that ZWDL command shows SUCCESS.
If checking of software versions are done again (ZWDM –mml) the software versions ofboth flashes on STANBY and on ACTIVE side should be same.
Change unit state back to SP-EX and WO-EX state:ZUSC: <ETP_unit_type> ,<index> :SP;ZUSC: <ETP_unit_type> ,<index> :WO;
Repeat steps 1 and 2 to all other ETP units which need to be updated.
5.4.4 Updating embedded sof tware of ETIP1-A
The embedded software is stored in the flash memory of the ETIP1-A plug-in unit and inthe OMU computer. It is possible to upload newer software build to the ETIP1-A plug-in
unit in BSC and in TCSM with the WDJ and WDK MML commands. It is recommended touse the same software version in all the ETIP1-A plug-in units, therefore a software
update is necessary when a faulty plug-in unit is replaced with a new one, and the newunit's SW version in the flash memory is different than that of the other plug-in units.
New softw are version(s) included in th is delivery:• LNX701G1.PAC 2.24-0 (APPL)• LNX704G1.PAC 2.10-0 (APPL)• LNX910G1.PAC 20.18-0 (APPL)• LNX91FG1.PAC 1.14-0 (APPL)
- The following example steps showing how to update ETIP1-A flash memory in BSCduring software update. If ETIP1-A configured to TCSM unit in WDK and WDJcommands have to be defined "NT=TCSM, NI=<TCSM index>" parameters.
- If IP for the eSW FTP loading is configured (and ETIP-A has LNX71BG1 3.5-0 ornewer ), then software can be loaded to TCSM’s ETIP1-A via IP/Ethernet instead ofLAPD channel by defining parameter SERVER= <omu_external_ip_adress> for WDJ-command.
If there are differences between existing and newer eSW, a new software(s) must beupdated to the flash memory of ETIP1-A.
NOTE! Depending on amount of software modules being to update it might take up to 45minutes per ETIP1-A plug-in unit.
The software has been divided into two categories: applications and Board SupportPackage (BSP).BSP consists of three modules:- Kernel = LNX71C02- FPGA = LNXFPG02- Loader = LNXUBO02
Application software (APPL) is all other modules listed WDK-command
Check ETIP units states:ZUSI:ETIP;
Change ETIP unit to TE-EX state:ZUSC:ETIP,<index>:BL;ZUSC:ETIP,<index>:TE,FCD;
Update changed eSW of ETIP unit:ZWDJ:UT=ETIP,UI=<index>,SW=ALL;
Or separately with below commands according above mentioned categories:
Restart ETIP unit and check alarms:ZUSU:ETIP,<index>;ZAHO:ETIP,<index>;
Check that primary and secondary software are corresponding each other.ZWDK:UT=ETIP,UI=<index>;
Change ETIP unit back to WO-EX state.ZUSC:ETIP,<index>:WO;
Repeat same procedure for all other ETIP Units.
If updated ETIP-A plug in unit is in TCSM, start a remote session with the ZDDT commandand restart ET units with ZUP command.ZDDT:TCSM,<tcsm_index>;ZUP:ET,<ETIP index>;
5.4.5 Updating Advantech CP1D-A BIOS SW
Check the BIOS eSW version from the CPU with MML command:ZWDI:UT=<unit >,UI=<unit index>,PT=CP1D-A,PI=0,SW=BIOS;
If Advantech CP1D-A is in use the update is needed to BIOS eSWNew software version(s) included in this delivery: AEM00024.IMG 1.6-0 = cp1d-a_ad_bios_0_4_6.rom
First change the unit state to TE-EX state with following command:ZUSC:<unit>, <unit index>:TE;
The BIOS software can be updated for CPU with following command:ZWDR:UT=<unit>,UI=<unit index>,PT=CP1D_A,PI=0,SW=BIOS:;
The following steps should be done after updating BIOS on CP1D_A card.Change unit to SE-NH
ZUSC:<unit>, <unit index>:SE;
In case MCMU CP1D-A is updated remember to chang e the EMB also to SE-NH statein affected MCMU site before taking the pow er OFFZUSC:EMB,<index>:TE;ZUSC:EMB,<index>:SE;ZUSC:EMB,<index>:SE;
Switch power off from unit cartridge power plug-in unit and switch power back tothe unit
Change unit to SP-EX or WO-EX stateZUSC:<unit>, <unit index>:SE;
ZUSC:<unit>, <unit index>:TE;ZUSC:<unit>, <unit index>:<SP or WO>;
5.4.6 Updating instruct ions for ESB24-D switch softw are
This CD includes new software for the ESB Ethernet switches. If ESB devices are used,update the software image to the ESB Ethernet switches.
Note! ESB modules ESB24DGX.BIN is DX200 format files and they can be used if updateis done using YF MML commands.For installing the ESB SW using PC and TFTP server/client, then module ESBB2DGX.BINcan be used.
5.4.6.1 Updatin g of ESB24-D wit h YF MML
Check the software version of the LAN switch.
ZYFM:ISW:SWU,<unit ind ex>;
Note! If the OS version in the LAN switch is older than the OS version in the build, updatethe software of the LAN switch according to the following instructions.
Open a telnet connection to the switch and save current configuration to memory.
Change Spare EMB unit to SE-OU state:ZUSC:EMB,<unit index>:TE;ZUSC:EMB,<unit index>:SE;
Update software to LAN switch:ZYFM:USW:SWU,<unit i ndex>;
Reset LAN switch:ZYFM:RES:SWU,<unit i ndex>;
Check updated software version of LAN switch:ZYFM:ISW:SWU,<unit index>;
Change state of Ethernet-based Message Bus (EMB):ZUSC:EMB,<unit index>:TE;ZUSC:EMB,<unit index>:SP;ZUSC:EMB,<unit index>:WO;
Repeat same procedure to other EMB LAN switch.
5.4.6.3 Updatin g with TFTP image to the ESB24-D Ethernet switc h.
In the examples of this document it is assumed that the IP-address of the updated switchis 192.168.0.1/24. Check the correct IP address of the switch you are updating before
entering the site.
The PC that is used as the FTP or TFTP server is supposed to have the IP address on thesame subnet as the switch has. This is essential because if the IP address of the PC isnot in the same subnet as the switch is, the FTP or TFTP transfer cannot be done properly(unless there is router between the subnets directing the IP packets to the correct subnet).If a personal firewall has been installed on PC, the IP address (192.168.0.1) of the switchmust be added to the access-list of the firewall software.
NoteNokia Siemens Networks sw itches have a default IP address w hich m ight besame on several switches. Therefore prior attempti ng th e update, the default IPaddresses should be changed to individ ual ones to ensure a successfulconnection to each individual sw itch.
In order to perform the update, following equipment is needed:
• ESB24-D switch to be updated• one PC or laptop with Ethernet• FTP or TFTP-server application installed on the PC.• terminal program installed on the PC• one straight through Ethernet cable (RJ-45)• the software image to be uploaded
This section provides instructions for upgrading the ESB24-D NOS operating system to anewer version.
The switch is rebooted during the update procedure: all LANconnections through the switch being updated are going to be downduring t he reboot.
In order to install a new NOS operating system version to ESB24-D, a FTP or TFTPserver is required: this is because ESB24-D downloads a new software image from a FTPor TFTP server. In these instructions it is assumed that the default IP address of theupdated switch is:IP Address: 192.168.0.1Netmask: 255.255.255.0Default Gateway: 192.168.0.254
Check the correct IP address of the switch before entering the site. The PC that is used asa FTP or TFTP server is supposed to have the IP address on the same subnet as theswitch has. This is essential because if the IP address of the PC is not in the same subnetas the switch is, the FTP or TFTP transfer cannot be done properly (unless there is routerbetween the subnets directing the IP packets to the correct subnet).In these instructions the IP address of the PC used as the TFTP server is assumed to be192.168.0.120/24.
1. Connect the PC to one of the Ethernet ports of the switch by using an Ethernet cable(no MGT port).
2. Check that the ESB24-D is powered up.
3. Start a Telnet session and connect to the IP address of the switch (for example,
192.168.0.1).On Windows this can be done as follows:START -> Run -> telnet 192.168.0.1
4. Login to the switch.Password: nsn- swi t ch
5. Enable "privileged mode".
ESB24D>enable
The Privileged mode allows advanced viewing and configuration capabilities for unit.
Note:The privileged mode command prompt is the hash symbol " #".
6. Check the current software version and date to avoid unnecessary upgrades.
In case OS1 or OS2 contains wanted SW version. You should use default-os <os> andreload <os> commands to select right SW package.
ESB24D# show f l ashFl ash I nf ormati on( Bytes)Ar ea tot al used f r ee- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -OS1( def aul t ) ( r unni ng) 25165824 14037024 11128800 1. 3- 2
Copy the software image (ESBB2DGX.BIN) to the PC.It is advised that the image is copied to the TFTP-server's default directory.
7. Start a FTP or TFTP server application on the PC.There are many different FTP or TFTP server applications available and management ofthese applications may vary between products.- Setup the FTP or TFTP server so that ESB24-D is allowed to download a file from thePC. See instructions how to setup FTP or TFTP.
- Set the root directory to be the same where the SW is located in the PC for the FTP orTFTP program:Current directory C:\<Root directory>Server interface Server IP address
8. Take a back-up copy of the switch’s configuration file by uploading it to the FTP orTFTP server.
Example:In the case TFTP is used. The TFTP server is running on a PC that has IP address192.168.0.120. The TFTP client is enabled on the switch that has IP address 192.168.0.1.The configuration file is copied to TFTP-server root directory on the PC.
ESB24D# copy r unni ng- conf i g st art up- conf i g[ OK]ESB24D# copy t f t p conf i g upl oad st ar t up- conf i g
IP address or name of remote host (TFTP): 192.168.0.120
Upl oad Fi l e Name [r unni ng]: conf i gNow upl oad conf i g f i l e i nt o 192. 168. 0. 120 vi a t f t p.Upl oadi ng f i l e . . . .Sent 923 byt es.Unexpected outcomeIf the IP address of the switch is missing from the PC’s firewall or there is other connectionproblem, you will get the following error:
ESB24D# copy t f t p conf i g upl oad st ar t up- conf i g To exi t : pr ess Ct r l +D- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -I P addr ess or name of r emot e host ( TFTP) : 192. 168. 0. 120Upl oad Fi l e Name [r unni ng]: conf i gNow upl oad conf i g f i l e i nt o 192. 168. 0. 120 vi a t f t p.Upl oadi ng f i l e . . . .
Tr ansf er t i med out .
Check the firewall settings and try again.
9. Copy the software image file to the Flash memory of the switch using the copy -command.
You can specify the file name of the software which will be saved to the file system. If thename is not specified, the software will be saved to the file system with its original name.
ESB24D# copy f t p os downl oad os1 To exi t : pr ess Ct r l +D- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -I P addr ess or name of r emot e host ( FTP) : 192. 168. 0. 120Downl oad Fi l e Name : ESBB2DGX. BI NUser Name : nos_ 0512Passwor d:Hash mar k pri nti ng on ( 1024 byt es/ hash mar k) .Downl oadi ng NOS . . . .############################…############################14037024 byt es downl oad OK.Upgr adi ng NOS : 100%ESB24D#
NoteIf the switch w as booted while receiving a TFTP packet, it willrestart using th e last image file. If this occur s, restart the
download.
Expected outcomeWhen the transfer is complete, ESB24-D writes the new software to Flash. After a whileNOS command prompt is displayed again.
Unexpected outcomeIf after a while the ESB24-D does not find a correct packet from FTP server or if ESB24-Dcannot connect to FTP server, it will return an error message and cancel the downloading.If this occurs, NOS command prompt is displayed again.
ESB24D# copy f t p os downl oad os1 To exi t : pr ess Ct r l +D
- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -I P addr ess or name of r emot e host ( FTP) : 192. 168. 0. 120Downl oad Fi l e Name : ESBB2DGX. BI NUser Name : nos_ 0512Not connect ed.Not connect ed.Hash mar k pri nti ng on ( 1024 byt es/ hash mar k) .Not connect ed.
10. Configure the switch so that it boots the newly downloaded image.
ESB24D# def aul t - os os1
11. Reset ESB24-D.
ESB24D# r el oad os1Do you want t o save t he syst emconf i gur ati on? [ y/ n]yDo you want t o r el oad t he syst em? [ y/ n] y
Expected outcomeTelnet connection is terminated and ESB24-D reboots with the new software version.
12. Reconnect to ESB24-D by using Telnet and check that the new software isprogrammed correctly to the ESB24-D.
ESB24D>show f l ash
13. In case running-config is not original download the configuration file from the FTPserver to the switch.
ExampleThe configuration file is copied to FTP server root directory on PC.
If OMU IP address type is logical connection to the OMU will be lost after unit has be changed to TE-EX state. In case of IP address is logical do this chapter manually via COM/VDU port or change IPtype to physical before macro execution.
First change the OMU state to TE-EX state with following command:ZUSC:OMU:TE;
The software can be updated for HWAT with following command:ZWDH:UT=OMU,UI=0,PT=HWAT_B,PI=3;
Change unit back to WO-EX:ZUSC:OMU:WO;
5.5 Special Instructions for mcBSC
5.5.1 Special instruct ions for mcBSC for TG4_MBSX
Instructi ons are needed when installing CD during upgr ade or to the runni ngpackage.
NOTE! In som e configu rations b elow alarms may com e active because of th eTG4_MBSX change
- 2863 UNKNOWN LAN CONNECTION DETECTED- 3292 INTERNAL LAN LINK BROKEN
Modification s to TG4_MBSX files topol ogies are needed after CD activation ONLY iftopol ogy cop y has been used in S16 source SW level with number T8
Check from below list the correct topology number based on box type and howmany boxes are in u se with MML com mand ZW6G:
Following step needs to be done if it is not done before.
MMI authentication is needed for mcBSC eSW update. Temporary user ID 'OCTEON' andpassword 'UPGRADE' need to be created with SYSTEM AUTHORITY HANDLING
COMMANDS (IAH). This must be done before the eSW update. Otherwise updateexecution fails.
Example of temporary user creation:
ZIAH:OCTEON:PROFILE;
EXECUTION STARTED/* IDENTIFY PASSWORD:MINIMUM PASSWORD LENGTH IS 6MAXIMUM PASSWORD LENGTH IS 16 */NEW PASSWORD:UPGRADEVERIFICATION:UPGRADE
/* IDENTIFY PASSWORD FOR OLDER SYSTEM LEVELS:MINIMUM PASSWORD LENGTH IS 6MAXIMUM PASSWORD LENGTH IS 15 */NEW PASSWORD:UPGRADEVERIFICATION:UPGRADECOMMAND EXECUTED IAH:OCTEON:PROFILE;
5.5.4.2 Enablin g FTP/Telnet server at LMP
In order to install eSW to BNC/BOC/BJC/BSAC add in cards with MML commandsFTP/Telnet server should be activated in LMP.
The eSW images are programmed into the BJC-A add-in card flash memory.
Following BJC-A eSW will be installedPIU/Units Program block Version Use Note OR Name in MML printou tBJC-A/ AEM00056 1.3-0 fpga bcnjc-a_em_dmxf_00_06_0027
OMU, MCMU,BCXU
AEM00057 1.6-0 bios bjc-a_em_bios_01_20_000e
AEM00054 1.8-0 fru bcnjc-a_em_frud_01.19.0003 AEM00046 1.8-0 mmcf bcnjc-a_em_mmcf_01.21.0000BJCACPLD 1.4-0 cpld CPLD 0x8F(card version A1A) or
0x8E (card version A2A)
5.5.5.1 Upgrade BJC-A FRU eSW
Check BJC-A add-in cards FRU versions with the MML command:
ZWDP:PT=BJC_A,;
Example:
FUNCTI ONAL PLUG- I N UNI T VERSION UNI T TYPE I NDEX CURRENT -> AFTER UPDATE- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
If newer MMCF is available, update the eSW unit by u nit w ith the MML commandZWDF. MCMU and BCXU uni t must be in TE state during update, OMU mus t be inWO-EX.
Note! OMU update needs to run with forced command:
Note!FPGA eSW activation requires col d restart of t he unit, whic h is don e during CPLDeSW update.Due to th at FPGA eSW update checking will be executed after CPLD eSW update.
5.5.5.6 Update BJC-A CPLD 0x8F (card version A1A) or 0x8E (card version A2A)
Start updating procedure with spare unit (MCMU, BCXU). After the unit is upgraded makeswitchover (ZUSC) and start the procedure with current SP unit until all units areupgraded.
After each unit upgrade test CS and PS call.
Open MGT (LMP) or serial session to BCN box.
It is also possible to connect from MML session to LMP with VIMMLAGX Service Terminalextension in order to update CPLD eSW for MCMUs and BCXUs. OMU update have to bedone locally via serial or MGT(LMP) connection.If remote MGT connection is available all steps can be done remotely, also for OMU.
5.5.5.6.1 LMP connect ion via VIMMLAGX Servi ce Termin al program
Connected to 10.10.10.1.220 Service ready for new user
Name (10.10.10.1:root): <mcBSC_user_id> //use capital letters//331 Username ok, need password.Password: <mcBSC_pasword> //use capital letters// 230 User xxx logged in.
1. Change connection type to binary
ftp> bin
2. Go to LFILES directory:
ftp> cd <mcs15_running_sw_package>/LFILES //use capital letters//
3. Copy BJCACPLD.ZIP to LMP
ftp> get B JCACPLD.ZIP
4. Close ftp connection
ftp> exit
5. Check that BJCACPLD.ZIP is in /tmp
root@BCNMB-A:/tmp# ls
6. Exract BJCACPLD.ZIP
.root@BCNMB-A:/tmp# tar -zxvf BJCACPLD.ZIP
7. Check that directories bcnjc-a_em_cpld_00_08_0014 and bcnjc-a_em_cpld_00_08_0015 and script file update-cpld-bcnjc-a.sh exist in the /tmp
root@BCNMB-A:/tmp# ls
8. Before upgrading the CPLD, check that the Product Version and Board partnumber are set correctly (Rev 1.1 for C112019.A1A and Rev 1.3 forC112019.A2A) in FRU:
root@BCNMB-A:/tmp # ipmitool -t 0x <slot-address> -b 7 fru pri nt 0
Where slot addresses are defined as follows:Slot 1 -> 0x72Slot 2 -> 0x74Slot 3 -> 0x76Slot 4 -> 0x78Slot 5 -> 0x7ASlot 6 -> 0x7CSlot 7 -> 0x7ESlot 8 -> 0x80
For Example:r oot @BCNMB- A: ~# i pmi t ool - t 0x72 - b 7 f r u pr i nt 0
Boar d Mf g : EMERSONBoar d Pr oduct : BCNJ C- ABoar d Ser i al : TV132112174Board Part Number : C112019.A2ABoar d Ext r a : 01b2Pr oduct Manuf act ur er : EMERSONPr oduct Name : BCNJ C- APr oduct Par t Number : 0106807H03BProduct Versi on : Rev 1. 3Pr oduct Ser i al : E1012DB
Pr oduct Asset Tag : asset Tagxx
r oot @BCNMB- A: ~# i pmi t ool - t 0x74 - b 7 f r u pr i nt 0Boar d Mf g : EMERSONBoar d Pr oduct : BCNJ C- ABoar d Ser i al : TV125220694Board Part Number : C112019.A1ABoar d Ext r a : 01b2Pr oduct Manuf act ur er : EMERSONPr oduct Name : BCNJ C- APr oduct Par t Number : 0106807H01EProduct Versi on : Rev 1. 1Pr oduct Ser i al : 6010680048W8Pr oduct Asset Tag : asset Tagxx
9. Update MCMU or BCXU. Deactivate BJC-A add-in card. Remember to deactivateSP-EX MCMU or BCXU unit.
Pr ocessor Name: I nt el ( R) Xeon( R) CPUProcessor Versi on: 14 Revi si on: 4CPU I D: 106e4 Mi cr ocode: 0xf f f f 0002Pr ocess or Speed: 1729 MHz Pr ocess or Maxi mum Speed: 1739 MHzNumber of Cor es: Enabl ed: 2 Di sabl ed: 0Logi cal Processors: Enabl ed: 2 Di sabl ed: 2Pr ocessor BI ST: P0 BI ST: Ok P1 BI ST: OkMemBI ST: Ok
Tot al Memor y Si ze: 4096 MBMemor y Mode: I ndependent Memor y Speed: 1067 MHzMemor y:Ch 0 Di mm 0: 2048 Rows: 14Ch 1 Di mm 0: 2048 Rows: 14
DMX FPGA I nf or mat i onFPGA Code: 0615W VARCODE[ 0: 1] BJ C- A
CPLD Ver si on: 0x8F or 0x8E
Note! If you missed this point on the boot up log, then wait until the startup is complete.Login to service terminal and output the stored boot log with command:ZDDT:110000,+1FFF
14. Af ter th e un it rec ov ery ch ang e next MCMU or BCXU (B JC-A) uni t t o SP-EXstate
a) Repeat steps 9 – 14 with all BJC-A add-in cards in t he BCN BOX until allMCMUs and BCXUs are updated
15. OMU CPLD eSW update
Make a local serial or MGT (LMP) or remote MGT (LMP) connection to the mcBSCBCN-A box 1. Repeat steps 9 -15 abov e for OMU.
5.5.5.6.2 Checking BJC-A FPGA eSW upd ate
Check the result:
ZWDI:PT=BJC_A,SW=FPGA;
Example:
/ *** NOTE ! ! ***/
FPGA VERSI ON I S ALWAYS THE RUNNI NG VERSI ON.ONLY AFTER COLD RESTART, THE NEWLY UPDATED FPGA VERSI ON COULD BE DI SLAYED.
FUNCTI ONAL PLUG- I N UNI T DMX FPGA: FLASH MEMORYUNI T TYPE I NDEX DI SK FI LE- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@ WARNI NG: REMOTE HOST I DENTI FI CATI ON HAS CHANGED! @@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@@I T I S POSSI BLE THAT SOMEONE I S DOI NG SOMETHI NG NASTY!
Someone coul d be eavesdr oppi ng on you ri ght now ( man- i n- t he- mi ddl e att ack) !I t i s al so possi bl e that t he RSA host key has j ust been changed. The f i nger pr i nt f or t he RSA key sent by t he r emot e host i s72: cb: f a: 89: e5: 91: c3: 00: 7b: 45: 3d: 7a: cc: 6a: 76: 06.Pl ease cont act your syst em admi ni st r ator .Add corr ect host key i n / r oot / . ssh/ known_hosts t o get r i d of t hi s message.Of f endi ng key i n / r oot / . ssh/ known_host s: 1RSA host key f or 10. 10. 10. 11 has changed and you have request ed st r i ct checki ng.Host key ver i f i cat i on f ai l ed.
In order to continue run command:
root@BCNMB-A:~# rm /root/.ssh/known_hosts
root@BCNMB-A:~# ssh 10.10.10.50
The aut hent i ci t y of host ' 10. 10. 10. 50 ( 10. 10. 10. 50) ' can' t be est abl i shed.RSA key f i nger pr i nt i s 1d: b0: ed: 13: 2a: db: 8c: f 4: d5: 86: d4: 5b: b2: 56: d5: 7a.Ar e you sur e you want t o cont i nue connect i ng ( yes/ no) ? yes Warni ng: Per manent l y added ' 10. 10. 10. 50' ( RSA) t o t he l i st of known host s.
Trying 10.10.10.50...Connected to 10.10.10.50.Escape character is '^]'.Linux 2.6.27.39-grsec (localhost) (00:04 on Thursday, 01 January 1970)Welcome to BCNSA-A AMC Command-LineUser: admin
Check after BSCA-A is recovered that bank 1 is active
root@BCNMB-A:~# ipmito ol -t 0x84 -b 7 raw 0x2e 0x1b 0x2a 0x6f 0x00
Activation command for Bank 0 is: ipmitool -t 0x84 -b 7 raw 0x2e 0x1C 0x2a 0x6f 0x000x00
After printout logs are taken from both PTUM 0’s flash banks connect to PTUM 1
(10.10.10.51) and take the logs.
• Updating th e eSW 2.5.3 to BSAC-A
When updating the BSAC-A both flash banks should be updated. You should not leavethe system in a state, where flash banks 0 and 1 contain different versions of the eSW.
Following BJC-A eSWs will be installed:
PIU/Units Program block Version Use Note OR Name in MML printou tBSAC-A / BNCSAUZZ 1.7-2 ucsw bcnsa-a_nk_ucsw_02.05.0003PTU AEM00047 1.8-0 mmcf bcnsa-a_nk_mmcf_02.02.0000
AEM00055 1.8-0 fru bcnsa-a_nk_frud_02.05.0003
Upgrade order is:
1. PTUM 12. PTUM 0
Check a active flash bank
Open local or remote MGT (LMP) or serial session to BNC box which is includingPTUM 1.
root@BCNMB-A:~# ipmito ol -t 0x84 -b 7 raw 0x2e 0x1b 0x2a 0x6f 0x00
Printout’s last digit indicates active flash bank.In example active flash bank is Bank 12a 6f 00 0 1
• Upgrade B SAC-A FRU eSW
Check PTUM 1 FRU version with the MML command:
ZWDP:UT=PTUM,UI=1;
FUNCTI ONAL PLUG- I N UNI T VERSI ONUNI T TYPE I NDEX CURRENT - > AFTER UPDATE- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PTUM- 1 BSAC_A- 0 bcnsa- a_nk_f r ud_02. 05. 0001 - >bcnsa- a_nk_ f r ud_02. 05. 0003 RBCNSA_A252
PTUM- 1 BSAC_A- 0 bcnsa- a_nk_ucsw Ver si on 02. 05. 0001bcnsa- a_nk_ucsw Ver si on 02. 05. 0001bcnsa- a_nk_ucsw Ver si on 02. 05. 0003UPDATED ( ACTI VE FLASH BANK 1)
If newer UCSW is available, update the eSW with the MML command:
ZWDU:UT=PTUM,UI=1,SW=UCSW;
LOADI NG PROGRAM VERSI ON 12. 95- 6
EXECUTI ON STARTED
1 VALI D PLUG- I N UNI TS FOUND
CONFI RM COMMAND EXECUTI ON: Y/ N ? Y
EXECUTI ON STARTED AT 2013- 07- 15 12: 55: 420% DONE, PLEASE WAI T 1 H, 0 MI N AND 0 SEC0% DONE, PLEASE WAI T 0 H, 59 MI N AND 44 SEC
##100% DONE, PLEASE WAI T 0 H, 0 MI N AND 0 SEC
FUNCTI ONAL PLUG- I N UNI TUNI T TYPE I NDEX RESULT- - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
PTUM- 1 BSAC_A- 0 UPDATED
COMMAND EXECUTED
Check the result of UCSW upgrade with the MML command ZWDT .
Change PTUM 1 to TE state with the MML command:
ZUSC;PTUM,1:TE;
Restart PTUM 1 with the MML command:
ZWDU:UT=PTUM,UI=1,DO=REBOOT;
Reboot command activate the second flash bank.
Open local or remote MGT (LMP) or serial session to BCN box which is includingPTUM 1.
root@BCNMB-A:~# ipmito ol -t 0x84 -b 7 raw 0x2e 0x1b 0x2a 0x6f 0x00
Printout’s last digit indicates active flash bank
In example active flash bank is Bank 12a 6f 00 0 1
Change PTUM 1 state to WO with the MML command:
ZUSC:PTUM,1:WO;
• Updatin g the eSW 2.5.3 to secon d flash bank and PTUM 0
Update BSAC-A FRU and UCSW software according to instruction above.
• Finalize the eSW upgrade
After the second flash bank update PTUM 1 reboot is not necessary to execute.
Check that BSAC-A (PTUM 1) configuration are similar than before eSW upgrade fromlogs taken previously.
If flash bank1 is active in PTUM 1 change flash bank 0 to active according toinstructions above.
Check that synchronization works in PTUM 1 before PTUM 0 eSW upgrade:
Pull out synchronization cable from PTUM 0. Check that PTUM 1 synchronizationcomes active with MML command:
ZDYI;
This may take for a while.
After synchronization is verified push the synchronization cable back to PTUM 0 andupgrade eSW 2.5.3 to PTUM 0 according to instructions above.
After BSAC-A eSW installation is done, compare the BSAC-A running configuration andprint out logs taken before eSW installation. If there is another difference than eSWversions, fix the configuration.
5.5.7 Updating BCN-A HIGIG con figurati on
NOTE ! ONLY RELATED FOR 7 BOX mcBSC
Open local or remote MGT (LMP) or serial session to BCN BOX 1
root@BCNMB-A:/opt# cp bsc-backplane-0.3.9/xmeshd /etc/init.droot@BCNMB-A:/opt# cp bsc-backplane-0.3.9/mesh7.xml . /’remembr take the lastdot into command*/
If there is permission denied error then executes below commands to enablepermission
root@BCNMB-A:/opt# cd /usr/bin root@BCNMB-A:/usr/bin# ls mesh root@BCNMB-A:/usr/bin# chmod 777 meshroot@BCNMB-A:~# cp /opt
Repeat
root@BCNMB-A:/opt# mesh -x m esh7.xml -m 10
NOTE!
mesh -x m esh7.xml -m 10 /*script f or BOX1*/ mesh -x m esh7.xml -m 20 /*script f or BOX2*/ mesh -x m esh7.xml -m 30 /*script f or BOX3*/ mesh -x m esh7.xml -m 40 /*script for BOX4*/mesh -x m esh7.xml -m 50 /*script f or BOX5*/ mesh -x m esh7.xml -m 60 /*script for BOX6*/mesh -x m esh7.xml -m 70 /*script f or BOX7*/
• Take the new BCNHIGIG configur ation i n us e.
root@BCNMB-A:/opt# cproot@BCNMB-A:~# reboot
or initialize the new BCNHIGIG configuration without reboot:
root@BCNMB-A:/opt# touch /var/run/cluster/ext/post.soc root@BCNMB-A:/opt# cd /var/run/cluster/ext root@BCNMB-A:/var/run/cluster/ext# ls
Repeat these steps wit h all BNC BOXes in the mcB SC
5.6 Cancell ing the Software Update
Note! If Multiple SW Updates are cancelled, check the cancelling instructions of eachUpdate and execute all required restarts. There may also be some special instructionsfor different SW Updates, which must be followed.
If the SW Update needs to be cancelled, follow the instructions below.
Change the status of the package, which was active before the SW Update installation, toBU. This can be done with the MML-command:
ZWSS:NAME=<previously_active_package>;
In order to activate the previous package into the system, the system restart is needed.
Note! By default, interface units are not restarted when their gateway computer isrestarted. If BSC has STMU, include parameter “STMU” at the end of ZUSS- command so
that all interface computers of the STMU type are also restarted. In the same way all
Delete the Software Update package, which now has the status UT. This can be done withMML command:
ZWQD:NAME=<cd_package>:MAFILE,PRINTS;
6. CHECKING OF THE PACKAGE CONSISTENCY
Verify the package using the new MAFILEGX with following command:
ZWQB:NAME= <new_package> :FORM=FAILED;
7. FALLBACK
It is highly recommended that a safecopy of the active package be made after theSoftware Update installation. The safecopy can be made by following the documentSafecopying in BSC. The safecopy document can be found from NED.
8. APPENDICES / REFERENCES
8.1 Module checksums in CDTEMP dir ectory
8.1.1 Module checksums (M98) in CDTEMP directory (ZMXV)
NAME EXT VER CHECKSUM STATUS ( D = DEFAULT VERSI ON )ABI _BXSX . I MG : 01 D: 35F0C02D: OKABKONFE1 . MTF : 01 D: 901BDDDD: OKABKONFES . MML : 01 D: DC1C8A9B: OKABM_BXSX . I MG : 01 D: FAA189CA: OK
RUMMANGX . I MG : 01 D: 10A5F936: OKRXFPRBG1 . I MG : 01 D: 7EA44AD5: OKRXSPRBGX . I MG : 01 D: EE7C7EFE: OKRYEPROGX . I MG : 01 D: 931D0AA7: OKRENFSTSX . I MG : 01 D: 3C97818D: OKS3CMANGX . I MG : 01 D: 35835089: OKSC7_BXSX . I MG : 01 D: 13D90169: OKSEMPERE1 . MTF : 01 D: 5E212FCC: OKSEMPERRS . MML : 01 D: 47BA1BFA: OKSG1000MP . CFL : 01 D: NO PI D STRI NGSG1000MPAL . LI S : 01 D: NO PI D STRI NGSI KALAGX . I MG : 01 D: 4B13BEC0: OKSORPROGX . I MG : 01 D: 3AA0E03C: OKSTHPRBGX . I MG : 01 D: BF2BCBB1: OKRYSSI XGX . I MG : 01 D: C8D53878: OKSWA_BGSX . I MG : 01 D: E27B2B51: OKSVATORGX . I MG : 01 D: 3E8A91E9: OKSWI COPGX . I MG : 01 D: EB0E91A9: OKSYE00000 . XML : 01 D: NO PI D STRI NG
SYE00001 . XML : 01 D: NO PI D STRI NGSYE00002 . XML : 01 D: NO PI D STRI NGSYE00003 . XML : 01 D: NO PI D STRI NGSYE00004 . XML : 01 D: NO PI D STRI NGSYE00005 . XML : 01 D: NO PI D STRI NGSUPPROGX . I MG : 01 D: 16C2B96C: OKSYE00007 . XML : 01 D: NO PI D STRI NGSYE00008 . XML : 01 D: NO PI D STRI NGSYE00009 . XML : 01 D: NO PI D STRI NGSYE00010 . XML : 01 D: NO PI D STRI NGSYE00011 . XML : 01 D: NO PI D STRI NGSYE00012 . XML : 01 D: NO PI D STRI NGSYE00013 . XML : 01 D: NO PI D STRI NGSYE00014 . XML : 01 D: NO PI D STRI NGSYE00015 . XML : 01 D: NO PI D STRI NGSYE00006 . XML : 01 D: NO PI D STRI NGSYE00017 . XML : 01 D: NO PI D STRI NGSYE00018 . XML : 01 D: NO PI D STRI NGSYECOFSD . XML : 01 D: NO PI D STRI NGSYEEMGSD . XML : 01 D: NO PI D STRI NGSYEFAI SD . XML : 01 D: NO PI D STRI NGSYI _BXSX . I MG : 01 D: 8551E3AC: OKSYODATSX . I MG : 01 D: C6709061: OKSYVHAND5 . MML : 01 D: 8A6F98C8: OKSYVHANE1 . MTF : 01 D: 32D0126C: OKSYE00016 . XML : 01 D: NO PI D STRI NG
T57_PXSX . I MG : 01 D: 0E11E1BE: OK T64_PXSX . I MG : 01 D: 875F1BF0: OK T65_PXSX . I MG : 01 D: 63F18354: OK TDP_BGSX . I MG : 01 D: EE7FC263: OK TFH_BXSX . I MG : 01 D: 22393548: OK TG4_EXSX . I MG : 01 D: C4C32ED8: OK TGYMANGX . I MG : 01 D: 735DC9DC: OK TLYLI BGX . I MG : 01 D: 840F8C5D: OK TQH_BXSX . I MG : 01 D: 38655036: OK T56_PXSX . I MG : 01 D: 7DABC00B: OK TR4_PXSX . I MG : 01 D: 97019E66: OK TSUPROGA . I MG : 01 D: CCEBF50E: OKUNELMAE1 . MTF : 01 D: 99F16EDA: OKUNELMAYF . MML : 01 D: AE5FAF59: OKUSAPROGX . I MG : 01 D: 56BE3425: OKWDUFRMGX . I MG : 01 D: 47AC4C36: OKXEHPRBSX . I MG : 01 D: E35C9063: OK
YEE_BXSX . I MG : 01 D: 3E7F8CFC: OK YOOHOOE1 . MTF : 01 D: 0E468BD7: OK TR3_PXSX . I MG : 01 D: 8ABB42BA: OKZLI BCDGX . I MG : 01 D: 54FBDF43: OKZYDEMI GX . I MG : 01 D: BE7933C5: OK
PONLI BGX . I MG : 01 D: F3A14F9B: OKPOXLI BGX . I MG : 01 D: BBD94CCE: OKPOXLI BJ X . I MG : 01 D: 630C50DC: OKPS0PRBGX . I MG : 01 D: FA6060C6: OKPSCPROGX . I MG : 01 D: CDA9D01A: OKPTI ABI SX . I MG : 01 D: B2F523F6: OKPOCBOLGX . I MG : 01 D: 9DB03E1C: OKPTRHANER . MML : 01 D: 575DA168: OKPUB_BXSX . I MG : 01 D: D6CA4B4F: OKPUM_B2SX . I MG : 01 D: AAD8B8DC: OKPVA_BXSX . I MG : 01 D: E1F518C0: OKPWUMMLE1 . MTF : 01 D: 77FFA089: OKPWUMMLQY . MML : 01 D: 3CE45F2A: OKPXNETMGX . I MG : 01 D: ED80AD46: OKPXSENDGX . I MG : 01 D: 64205136: OKPZ3PRODX . I MG : 01 D: 85E68A36: OKPTRHANE1 . MTF : 01 D: FEEA2009: OKRC0_BGSX . I MG : 01 D: D575ACAC: OKRCP_B2SX . I MG : 01 D: ABCBF200: OK
RCP_BFSX . I MG : 01 D: 3A8C4F1F: OKRCP_BGSX . I MG : 01 D: 5D304C16: OKRCS_BXSX . I MG : 01 D: 5466235E: OKRCXPROGX . I MG : 01 D: 038FF9F4: OKRDI SFSGX . I MG : 01 D: 0FDB260C: OKROG_B2SX . I MG : 01 D: BAC75354: OKROG_BFSX . I MG : 01 D: F6E185A7: OKQOF_BXSX . I MG : 01 D: 65F9F1A9: OKROL_ BXSX . I MG : 01 D: B180C25F: OKRRM_BXSX . I MG : 01 D: E7C710C8: OKRUMMANGX . I MG : 01 D: 10A5F936: OKRXFPRBG1 . I MG : 01 D: 7EA44AD5: OKRXSPRBGX . I MG : 01 D: EE7C7EFE: OKRYEPROGX . I MG : 01 D: 931D0AA7: OKRYSSI XGX . I MG : 01 D: C8D53878: OKS3CMANGX . I MG : 01 D: 35835089: OKSC7_BXSX . I MG : 01 D: 13D90169: OKROG_BXSX . I MG : 01 D: D934DD56: OKSEMPERRS . MML : 01 D: 47BA1BFA: OKSG1000MP . CFL : 01 D: NO PI D STRI NGSG1000MPAL . LI S : 01 D: NO PI D STRI NGSI KALAGX . I MG : 01 D: 4B13BEC0: OKSORPROGX . I MG : 01 D: 3AA0E03C: OKSTHPRBGX . I MG : 01 D: BF2BCBB1: OKSUPPROGX . I MG : 01 D: 16C2B96C: OKSWA_BGSX . I MG : 01 D: E27B2B51: OKSVATORGX . I MG : 01 D: 3E8A91E9: OKSEMPERE1 . MTF : 01 D: 5E212FCC: OKSYE00000 . XML : 01 D: NO PI D STRI NGSYE00001 . XML : 01 D: NO PI D STRI NGSYE00002 . XML : 01 D: NO PI D STRI NGSYE00003 . XML : 01 D: NO PI D STRI NGSYE00004 . XML : 01 D: NO PI D STRI NGSYE00005 . XML : 01 D: NO PI D STRI NGSYE00006 . XML : 01 D: NO PI D STRI NGSYE00007 . XML : 01 D: NO PI D STRI NGSYE00008 . XML : 01 D: NO PI D STRI NGSWI COPGX . I MG : 01 D: EB0E91A9: OKSYE00010 . XML : 01 D: NO PI D STRI NGSYE00011 . XML : 01 D: NO PI D STRI NGSYE00012 . XML : 01 D: NO PI D STRI NGSYE00013 . XML : 01 D: NO PI D STRI NGSYE00014 . XML : 01 D: NO PI D STRI NGSYE00015 . XML : 01 D: NO PI D STRI NGSYE00016 . XML : 01 D: NO PI D STRI NGSYE00017 . XML : 01 D: NO PI D STRI NGSYE00018 . XML : 01 D: NO PI D STRI NGSYE00009 . XML : 01 D: NO PI D STRI NGSYEEMGSD . XML : 01 D: NO PI D STRI NG
SYEFAI SD . XML : 01 D: NO PI D STRI NGSYI _BXSX . I MG : 01 D: 8551E3AC: OK
PZ3PRODX . I MG : 01 D: 85E68A36: OKQOF_BXSX . I MG : 01 D: 65F9F1A9: OKRC0_BGSX . I MG : 01 D: D575ACAC: OKRCP_B2SX . I MG : 01 D: ABCBF200: OKRCP_BFSX . I MG : 01 D: 3A8C4F1F: OKPUM_B2SX . I MG : 01 D: AAD8B8DC: OKRCS_BXSX . I MG : 01 D: 5466235E: OKRCXPROGX . I MG : 01 D: 038FF9F4: OKRDI SFSGX . I MG : 01 D: 0FDB260C: OKROG_B2SX . I MG : 01 D: BAC75354: OKROG_BFSX . I MG : 01 D: F6E185A7: OKROG_BXSX . I MG : 01 D: D934DD56: OKROL_ BXSX . I MG : 01 D: B180C25F: OKRRM_BXSX . I MG : 01 D: E7C710C8: OKRUMMANGX . I MG : 01 D: 10A5F936: OKRCP_BGSX . I MG : 01 D: 5D304C16: OKRXSPRBGX . I MG : 01 D: EE7C7EFE: OKRYEPROGX . I MG : 01 D: 931D0AA7: OKRYSSI XGX . I MG : 01 D: C8D53878: OK
S3CMANGX . I MG : 01 D: 35835089: OKSC7_BXSX . I MG : 01 D: 13D90169: OKSEMPERE1 . MTF : 01 D: 5E212FCC: OKSEMPERRS . MML : 01 D: 47BA1BFA: OKSG1000MP . CFL : 01 D: NO PI D STRI NGSG1000MPAL . LI S : 01 D: NO PI D STRI NGRXFPRBG1 . I MG : 01 D: 7EA44AD5: OKSORPROGX . I MG : 01 D: 3AA0E03C: OKSTHPRBGX . I MG : 01 D: BF2BCBB1: OKSUPPROGX . I MG : 01 D: 16C2B96C: OKSWA_BGSX . I MG : 01 D: E27B2B51: OKSVATORGX . I MG : 01 D: 3E8A91E9: OKSWI COPGX . I MG : 01 D: EB0E91A9: OKSYE00000 . XML : 01 D: NO PI D STRI NGSYE00001 . XML : 01 D: NO PI D STRI NGSYE00002 . XML : 01 D: NO PI D STRI NGSI KALAGX . I MG : 01 D: 4B13BEC0: OKSYE00004 . XML : 01 D: NO PI D STRI NGSYE00005 . XML : 01 D: NO PI D STRI NGSYE00006 . XML : 01 D: NO PI D STRI NGSYE00007 . XML : 01 D: NO PI D STRI NGSYE00008 . XML : 01 D: NO PI D STRI NGSYE00009 . XML : 01 D: NO PI D STRI NGSYE00010 . XML : 01 D: NO PI D STRI NGSYE00011 . XML : 01 D: NO PI D STRI NGSYE00012 . XML : 01 D: NO PI D STRI NGSYE00003 . XML : 01 D: NO PI D STRI NGSYE00014 . XML : 01 D: NO PI D STRI NGSYE00015 . XML : 01 D: NO PI D STRI NGSYE00016 . XML : 01 D: NO PI D STRI NGSYE00017 . XML : 01 D: NO PI D STRI NGSYE00018 . XML : 01 D: NO PI D STRI NGSYECOFSD . XML : 01 D: NO PI D STRI NGSYEEMGSD . XML : 01 D: NO PI D STRI NGSYEFAI SD . XML : 01 D: NO PI D STRI NGSYI _BXSX . I MG : 01 D: 8551E3AC: OKSYE00013 . XML : 01 D: NO PI D STRI NGSYVHAND5 . MML : 01 D: 8A6F98C8: OKSYVHANE1 . MTF : 01 D: 32D0126C: OK
TDP_BGSX . I MG : 01 D: 02796FD5: OK TFH_BXSX . I MG : 01 D: 22393548: OK TG4_MBSX . I MG : 01 D: AE75429D: OK TGYMANGX . I MG : 01 D: 735DC9DC: OK TLYLI BGX . I MG : 01 D: 840F8C5D: OK TQH_BXSX . I MG : 01 D: 38655036: OK TSUPROGA . I MG : 01 D: CCEBF50E: OKSYODATSX . I MG : 01 D: C6709061: OKUNELMAYF . MML : 01 D: AE5FAF59: OKUSAPROGX . I MG : 01 D: 56BE3425: OK
WDUFRMGX . I MG : 01 D: 47AC4C36: OKXEHPRBSX . I MG : 01 D: E35C9063: OK
SWI COPGX . I MG : 01 D: EB0E91A9: 10. 15- 0 11/ 10/ 18 PLAENVY1. PAC 2. 44- 11SYE00000 . XML : 01 D: NO PI D STRI NGSYE00001 . XML : 01 D: NO PI D STRI NGSYE00002 . XML : 01 D: NO PI D STRI NGSYE00003 . XML : 01 D: NO PI D STRI NGSYE00004 . XML : 01 D: NO PI D STRI NGSYE00005 . XML : 01 D: NO PI D STRI NGSUPPROGX . I MG : 01 D: 16C2B96C: 9. 44- 0 13/ 06/ 18 PLAENVY1. PAC 2. 44- 11SYE00007 . XML : 01 D: NO PI D STRI NGSYE00008 . XML : 01 D: NO PI D STRI NGSYE00009 . XML : 01 D: NO PI D STRI NGSYE00010 . XML : 01 D: NO PI D STRI NGSYE00011 . XML : 01 D: NO PI D STRI NGSYE00012 . XML : 01 D: NO PI D STRI NGSYE00013 . XML : 01 D: NO PI D STRI NGSYE00014 . XML : 01 D: NO PI D STRI NGSYE00015 . XML : 01 D: NO PI D STRI NGSYE00006 . XML : 01 D: NO PI D STRI NGSYE00017 . XML : 01 D: NO PI D STRI NGSYE00018 . XML : 01 D: NO PI D STRI NGSYECOFSD . XML : 01 D: NO PI D STRI NGSYEEMGSD . XML : 01 D: NO PI D STRI NGSYEFAI SD . XML : 01 D: NO PI D STRI NGSYI _BXSX . I MG : 01 D: 8551E3AC: 25. 21- 0 13/ 07/ 17 BXXENVSG. PAC 3. 10- 0SYODATSX . I MG : 01 D: C6709061: 1. 36- 0 13/ 07/ 12 BXXENVSG. PAC 3. 10- 0SYVHAND5 . MML : 01 D: 8A6F98C8: 1. 14- 0 13/ 06/ 24 BXXENVSG. PAC 3. 10- 0SYVHANE1 . MTF : 01 D: 32D0126C: 1. 14- 0 13/ 06/ 24 BXXENVSG. PAC 3. 10- 0SYE00016 . XML : 01 D: NO PI D STRI NG
BXXENVSG. PAC 3. 10- 0SEMPERRS . MML : 01 D: 47BA1BFA: 1. 4- 0 11/ 09/ 07 PLAENVY1. PAC 2. 44- 11SG1000MP . CFL : 01 D: NO PI D STRI NGSG1000MPAL . LI S : 01 D: NO PI D STRI NGSI KALAGX . I MG : 01 D: 4B13BEC0: 1. 51- 1 11/ 10/ 19 PLAENVY1. PAC 2. 44- 11SORPROGX . I MG : 01 D: 3AA0E03C: 23. 42- 0 13/ 04/ 11 PLAENVY1. PAC 2. 44- 11STHPRBGX . I MG : 01 D: BF2BCBB1: 16. 9- 0 13/ 06/ 13 PLAENVY1. PAC 2. 44- 11SUPPROGX . I MG : 01 D: 16C2B96C: 9. 44- 0 13/ 06/ 18 PLAENVY1. PAC 2. 44- 11SWA_BGSX . I MG : 01 D: E27B2B51: 21. 2- 0 13/ 05/ 06 BXXENVSG. PAC 3. 10- 0SVATORGX . I MG : 01 D: 3E8A91E9: 3. 14- 6 13/ 06/ 06 PLAENVY1. PAC 2. 44- 11SEMPERE1 . MTF : 01 D: 5E212FCC: 1. 4- 0 11/ 09/ 07 PLAENVY1. PAC 2. 44- 11SYE00000 . XML : 01 D: NO PI D STRI NGSYE00001 . XML : 01 D: NO PI D STRI NGSYE00002 . XML : 01 D: NO PI D STRI NGSYE00003 . XML : 01 D: NO PI D STRI NGSYE00004 . XML : 01 D: NO PI D STRI NGSYE00005 . XML : 01 D: NO PI D STRI NGSYE00006 . XML : 01 D: NO PI D STRI NGSYE00007 . XML : 01 D: NO PI D STRI NGSYE00008 . XML : 01 D: NO PI D STRI NGSWI COPGX . I MG : 01 D: EB0E91A9: 10. 15- 0 11/ 10/ 18 PLAENVY1. PAC 2. 44- 11SYE00010 . XML : 01 D: NO PI D STRI NGSYE00011 . XML : 01 D: NO PI D STRI NGSYE00012 . XML : 01 D: NO PI D STRI NGSYE00013 . XML : 01 D: NO PI D STRI NGSYE00014 . XML : 01 D: NO PI D STRI NGSYE00015 . XML : 01 D: NO PI D STRI NGSYE00016 . XML : 01 D: NO PI D STRI NGSYE00017 . XML : 01 D: NO PI D STRI NGSYE00018 . XML : 01 D: NO PI D STRI NGSYE00009 . XML : 01 D: NO PI D STRI NGSYEEMGSD . XML : 01 D: NO PI D STRI NGSYEFAI SD . XML : 01 D: NO PI D STRI NGSYI _BXSX . I MG : 01 D: 8551E3AC: 25. 21- 0 13/ 07/ 17 BXXENVSG. PAC 3. 10- 0SYODATSX . I MG : 01 D: C6709061: 1. 36- 0 13/ 07/ 12 BXXENVSG. PAC 3. 10- 0
RYEPROGX . I MG : 01 D: 931D0AA7: 3. 44- 0 13/ 06/ 21 PLAENVY1. PAC 2. 44- 11RYSSI XGX . I MG : 01 D: C8D53878: 5. 27- 0 13/ 07/ 25 PLAENVY1. PAC 2. 44- 11S3CMANGX . I MG : 01 D: 35835089: 6. 48- 0 13/ 05/ 24 PLAENVY1. PAC 2. 44- 11SC7_BXSX . I MG : 01 D: 13D90169: 22. 3- 0 13/ 05/ 22 BXXENVSG. PAC 3. 10- 0SEMPERE1 . MTF : 01 D: 5E212FCC: 1. 4- 0 11/ 09/ 07 PLAENVY1. PAC 2. 44- 11SEMPERRS . MML : 01 D: 47BA1BFA: 1. 4- 0 11/ 09/ 07 PLAENVY1. PAC 2. 44- 11SG1000MP . CFL : 01 D: NO PI D STRI NGSG1000MPAL . LI S : 01 D: NO PI D STRI NGRXFPRBG1 . I MG : 01 D: 7EA44AD5: 1. 6- 0 09/ 01/ 09 PLAENVY1. PAC 2. 44- 11SORPROGX . I MG : 01 D: 3AA0E03C: 23. 42- 0 13/ 04/ 11 PLAENVY1. PAC 2. 44- 11STHPRBGX . I MG : 01 D: BF2BCBB1: 16. 9- 0 13/ 06/ 13 PLAENVY1. PAC 2. 44- 11SUPPROGX . I MG : 01 D: 16C2B96C: 9. 44- 0 13/ 06/ 18 PLAENVY1. PAC 2. 44- 11SWA_BGSX . I MG : 01 D: E27B2B51: 21. 2- 0 13/ 05/ 06 BXXENVSG. PAC 3. 10- 0SVATORGX . I MG : 01 D: 3E8A91E9: 3. 14- 6 13/ 06/ 06 PLAENVY1. PAC 2. 44- 11SWI COPGX . I MG : 01 D: EB0E91A9: 10. 15- 0 11/ 10/ 18 PLAENVY1. PAC 2. 44- 11SYE00000 . XML : 01 D: NO PI D STRI NGSYE00001 . XML : 01 D: NO PI D STRI NGSYE00002 . XML : 01 D: NO PI D STRI NGSI KALAGX . I MG : 01 D: 4B13BEC0: 1. 51- 1 11/ 10/ 19 PLAENVY1. PAC 2. 44- 11
SYE00004 . XML : 01 D: NO PI D STRI NGSYE00005 . XML : 01 D: NO PI D STRI NGSYE00006 . XML : 01 D: NO PI D STRI NGSYE00007 . XML : 01 D: NO PI D STRI NGSYE00008 . XML : 01 D: NO PI D STRI NGSYE00009 . XML : 01 D: NO PI D STRI NGSYE00010 . XML : 01 D: NO PI D STRI NGSYE00011 . XML : 01 D: NO PI D STRI NGSYE00012 . XML : 01 D: NO PI D STRI NGSYE00003 . XML : 01 D: NO PI D STRI NGSYE00014 . XML : 01 D: NO PI D STRI NGSYE00015 . XML : 01 D: NO PI D STRI NGSYE00016 . XML : 01 D: NO PI D STRI NGSYE00017 . XML : 01 D: NO PI D STRI NGSYE00018 . XML : 01 D: NO PI D STRI NGSYECOFSD . XML : 01 D: NO PI D STRI NGSYEEMGSD . XML : 01 D: NO PI D STRI NGSYEFAI SD . XML : 01 D: NO PI D STRI NGSYI _BXSX . I MG : 01 D: 8551E3AC: 25. 21- 0 13/ 07/ 17 BXXENVSG. PAC 3. 10- 0SYE00013 . XML : 01 D: NO PI D STRI NGSYVHAND5 . MML : 01 D: 8A6F98C8: 1. 14- 0 13/ 06/ 24 BXXENVSG. PAC 3. 10- 0SYVHANE1 . MTF : 01 D: 32D0126C: 1. 14- 0 13/ 06/ 24 BXXENVSG. PAC 3. 10- 0
The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This documentation is intended for theuse of Nokia Solutions and Networks customers only for the purposes of the agreement underwhich the document is submitted, and no part of it may be used, reproduced, modified ortransmitted in any form or means without the prior written permission of Nokia Solutions andNetworks. The documentation has been prepared to be used by professional and properlytrained personnel, and the customer assumes full responsibility when using it. Nokia Solutionsand Networks welcomes customer comments as part of the process of continuous developmentand improvement of the documentation.
The information or statements given in this documentation concerning the suitability, capacity,or performance of the mentioned hardware or software products are given “as is” and all liabilityarising in connection with such hardware or software products shall be defined conclusively andfinally in a separate agreement between Nokia Solutions and Networks and the customer.
However, Nokia Solutions and Networks has made all reasonable efforts to ensure that theinstructions contained in the document are adequate and free of material errors and omissions.Nokia Solutions and Networks will, if deemed necessary by Nokia Solutions and Networks,explain issues which may not be covered by the document.
Nokia Solutions and Networks will correct errors in this documentation as soon as possible. INNO EVENT WILL NOKIA SOLUTIONS AND NETWORKS BE LIABLE FOR ERRORS IN THISDOCUMENTATION OR FOR ANY DAMAGES, INCLUDING BUT NOT LIMITED TO SPECIAL,DIRECT, INDIRECT, INCIDENTAL OR CONSEQUENTIAL OR ANY LOSSES, SUCH AS BUTNOT LIMITED TO LOSS OF PROFIT, REVENUE, BUSINESS INTERRUPTION, BUSINESSOPPORTUNITY OR DATA,THAT MAY ARISE FROM THE USE OF THIS DOCUMENT ORTHE INFORMATION IN IT.
This documentation and the product it describes are considered protected by copyrights andother intellectual property rights according to the applicable laws.
NSN is a trademark of Nokia Solutions and Networks. Nokia is a registered trademark of NokiaCorporation. Other product names mentioned in this document may be trademarks of theirrespective owners, and they are mentioned for identification purposes only.