MSC 13A IPA04 Package Information

Ericsson Internal TECHNICAL INFO

1 (25)

Prepared (also subject responsible if other) No.

IXG/PLM Alexia Magkina 109 29-04/CXR 101 1489/IPA Uen Approved Checked Date Rev Reference

IXG/PLM Dimitris Filopoulos XMARSPI 2015-07-10 A

D:\AdobeLCES2_Config_Data\lc_temp\pdfg-edfsadmin\3b\e539-2668ea-f05606-0e7aa5-810ed2-d190c8\238dc838e0.doc

MSC 13A IPA04 Package Information MSC Package Information Document describes the contents of one update package. The revision of the document does not follow the package revision.

Contents 1 Package Status ................................................................................... 2 2 Package Information ........................................................................... 2 2.1 General Information ............................................................................. 2 2.2 Applicability ......................................................................................... 3 2.3 Applicable Base Levels ....................................................................... 3 2.4 Signaling Standard Verification ........................................................... 3 2.5 Reference to Write a Trouble Report on this Package ........................ 3 3 Package Special Handling .................................................................. 4 3.1 Pre-Requisites ..................................................................................... 4 3.2 Implementation Time ........................................................................... 4 3.3 Implementation Warnings .................................................................... 4 3.4 Traffic Impacting Warnings ................................................................ 15 3.5 Manual Handling ............................................................................... 15 3.5.1 Start extra command handling terminal ............................................. 15 3.5.2 Manual Parameter settings ............................................................... 16 3.5.3 Manual Clean-up procedures needed for all environments. .............. 16 3.5.4 Manual Clean-up procedures needed only for Dual Blade and SPX . 17 4 Package Revision History ................................................................. 21 4.1 Package Revision A .......................................................................... 21 5 General Warnings ............................................................................. 21 5.1 CP software implementation warnings .............................................. 21 5.1.1 Traffic handling .................................................................................. 21 5.1.2 Fallback ............................................................................................. 21 5.2 Other implementation warnings ......................................................... 21 5.2.1 Exchange requirements and preparation .......................................... 21 5.2.2 Error handling .................................................................................... 22 6 General Warnings for MSC-S BC ...................................................... 22 6.1 CP software implementation warnings .............................................. 22 6.1.1 Traffic handling .................................................................................. 23 6.1.2 Fallback ............................................................................................. 23 6.2 6.2 RP software implementation warnings ........................................ 23 6.3 Other implementation warnings ......................................................... 23 6.3.1 MSC-SBC specific warnings ............................................................. 23 6.3.2 Exchange requirements and preparation .......................................... 24 6.3.3 Error handling .................................................................................... 25


2 (25)





1 Package Status • 2015-07-10: IPA04 is released in Rev. A.

2 Package Information 2.1 General Information

This is a scheduled package for MSC 13A that consists of APT/APZ ACs, and APT/APZ RPs.

To see a list of all Trouble Reports and the list of all included packages, please see the Package Description (PDE) which is part of the package content delivered via Software Gateway.

IPA04 includes the APZ19.0 ICM906, ICM907, ICM908 and ICM909 level.

IPA04 is an accumulated package. It includes also IPA01, IPA02, IPA03 and EPAs 1, 2, 3, 6, 7, 10, 12, 13, 16, 19, 20, 21, 22, 23, 25, 28, 29, 34, 35, 36, 37, 38, 40, 46, 49, 52, 56, 58, 59, 60, 61, 63, 66, 68, 71, 72, 73, 74,76,79, 81, 82, 84, 85, 86, 87, 88, 91 and 92 meaning that user has the option to select the packages to be implemented. The available options are: - IPA04 only - IPA04 (only or with any combination of EPAs) - IPA03 (only or with any combination of EPAs) - IPA02 (only or with any combination of EPAs) - IPA01 (only or with any combination of EPAs) - EPAs (without selecting any IPA) In case user selects IPA04 package to be implemented then all previous released EPAs packages will be selected also for loading. For further information about the Packages dependency, please refer to the Package_Contents_MSC13A_MSC13AUP_BJ document, Package_dependency sheet, placed in the DOC folder of the package.

In case user selects for implementing a package that does not deliver APZ ACs then no APZ loadfile will be created. The user during the cp_script execution should ignore the Fault Code 8 on the IOCMI command for the APZ loadifles and should press APPLY to continue with the script execution. A popup window will appear saying that “Command file does not exist, execute correct file manually, and then press APPLY “(for example 13A5I000AL01.COR and 13A5I000AS01.COR in case the APZ type of the node is APZ21250).

IPA04 does not include any MW software. Though, there are EPA93 (21403 latest MW), EPA100 (21250 latest MW) and EPA115 (21260 latest MW) included in the Accumulation.


3 (25)





Important information:

• IPA04 uses only the cloning method on BC nodes.

• In case of MSC-BC system, the apg_update script will be executed only for blade and not for SPXs.

• SPX only: A large restart will be issued in SPXs in order to clear corruptions after IPA03 loading. That restart will not happen at the same time to both SPXs. So the traffic impacts will be minimal.

IPA04 includes several solutions which require special handling, for further information, please refer to chapter 3.3 Implementation Warnings.

IPA04 can be loaded using the Unattended Update feature. Further documentation on this feature is provided in the DOC folder of the package.

2.2 Applicability This package is applicable to the following configurations. However, please note that PLM has not tested all possible configurations.

MSC Release: MSC 13A Signaling Standard: ETSI, ANSI, TTC, CWTS Node type: MSC, MSC-BC APZ: APZ21250, APZ21260, APZ21403 IO: APG40, APG43 OSS RC: 13.0 and onwards

2.3 Applicable Base Levels The minimum base level for this package is GA.

2.4 Signaling Standard Verification NOTE: Please be aware that the package may not have been verified in all signaling standards.

ETSI: NOT Verified. ANSI: NOT Verified. CWTS: NOT Verified. TTC: NOT Verified.

This package is SEA verified at the moment. Though, there will take place ETSI verification in the future.

2.5 Reference to Write a Trouble Report on this Package In order to issue a Trouble Report on this package, please use the following references:


4 (25)





Product ID: 04/CXR 101 1489/IPA AS/SS: CXC 132 3333/1 R1A MHO: EED-REM-UPD

3 Package Special Handling 3.1 Pre-Requisites

There are no pre-requisites for loading this EPA.

3.2 Implementation Time

The table below shows the implementation time needed on the different APZ types for a dual CP Times (in minutes) below are indicative. (GA level to IPA04)

APZ TYPE

PACKAGE SELECTION NSLOPE HEALTH

CHECK DOWNLOAD CP CLEANUP

21250 3 60 5 30 80 5 21260 3 60 5 30 90 5

The table below shows the implementation time needed for a Blade System

Times (in minutes) below are indicative. (GA level to IPA04) APZ

TYPE PACKAGE

SELECTION NSLOPE HEALTH CHECK DOWNLOAD CP CLEANUP

21403 BC 3 60 5 30 95 5 SPX 3 60 5 30 95 5

Note that implementation times for BC 21403 depend on the number of blades in the node.

3.3 Implementation Warnings

IPA04 Warning1: IPA04 delivers, via EPA79, AC RWANV-1308 which replaces R01MCXJN-8840 in MTB and R01MCXJN-8839 in MTBSS. After AC loading, the functionality is by default deactivated. Activation of the AC can be performed by setting in block MTB the dummy variable CDUMMY4 to 1.

- Activation commands (ONLY in case customer wishes to activate the AC):

TEST SYSTEM; PRINT VAR MTB 125; SET VAR MTB 125=1; PRINT VAR MTB 125; END TEST;

- De-activation commands (In case customer wants to deactivate AC functionality without removing AC):


5 (25)





TEST SYSTEM; PRINT VAR MTB 125; SET VAR MTB 125=0; PRINT VAR MTB 125; END TEST;

Warning2: IPA04 delivers, via EPA79, APZ AC Z02BL-1379 which demands the signal CPDATLOCKINF to be loaded. This action is hard-copied in the AC loadfile. In case the signal CPDATLOCKINF is already loaded, the script will stop with the following warning message:

NOT ACCEPTED FAULT CODE 512 SIGNAL NAME ALREADY USED

A pop-up window will appear and the user then should select to continue. On the displayed pop-up window choose the option:

“Correct the fault manually and Continue reading of command file by IOCCI”. The script will continue with rest of execution.

Warning3: IPA04 delivers, via EPA85, RWAXC-2299. Command DBTSC to change data on SHDTPS table should not be used while loading the AC. Warning4: IPA04 delivers, via EPA85, RWAZJ-0624-M0001 and RWAZJ-0624-M0002. Those ACs do not clear any possible corruption due to the reported fault. In case event h'0009 h'09b8 h'927f or h'0009 h'0e03 h'927f (see fault code 0001 and 0008) in block BID/BIDI or hanging command BIMTE has been detected, contact with next line of support in order dedicated clean up procedure to be provided.

In case command BIMTP:USER=ALL; indicates that BICC monitoring of test call exist, the following step should be performed after AC loading, depending of used environment : - at least small restart in case of dual blade environment (or wait for the next scheduled restart). - large restart of each blade after performed blade traffic isolation (automatically ordered by the script due to cloning method).

Warning5: IPA04 delivers AC RWAUA-2870 which loading may cause possible hangings in blocks HRRGAP3 and HMAPTC (due to fault solved with the AC), with low possibility to happen, will be cleared in the next system restart


6 (25)





Warning6: IPA04 delivers RWAUA-2896, RWAUA-2898 and RWAUA-2899. The fault solved with these ACs is possible to introduce hanging, which may make any activity (e.g. printouts, provisioning, traffic) for affected subscription not possible. The fault can happened when feature SMS HOME ROUTING is active (AXE parameter GSMHRSC:SMSHRACT enabled, value 1) and it affects APZ 212 family only. Small restart is recommended to clear all possible hangings.

Warning7: IPA04 delivers RWAXC-2424 and RWAXC-2429 which fix a rare problem and may create difficult to detect and verify hangings. In case there are indications of hanging records in SAE 604, Block SHMM, design maintenance should be contacted to provide further instructions. Alternatively, the hangings may be released by a large system restart.

Warning8: IPA04 delivers RWAYJ-1758. System Restart Large should be executed if hanging of SIPBC-SIPHOT-SIPHIT-SIPCO-TPD-TPC, TPMON individuals are observed before AC loading.

Warning9: IPA04 delivers RWAXC-2158 with scripted procedure before AC loading. During execution of scripted procedure no MSC administration commands (MGNMI, MGNMC, MGNMP, MGNME) or size alteration commands (SAAII/SAADI) for SAE 274 should be ongoing.

Warning10: IPA04 delivers RWAXC-2518 with scripted procedure, after AC loading. No commands from block MERNA (MGECI, MGECC, MGECE, MGECP, MGRCI, MGRCC, MGRCE, MGRCP) should be executed during CUP execution.

Warning11: IPA04 delivers RWAYJ-1817 with scripted clean up procedure, after AC loading. No commands IHADE, IHADI, IHAPC, IHAPP, IHASC, IHBIE, IHBII, IHCLP, IHLPC, IHLPP, IHSSP, M3ASC, M3ASP, M3RAE, M3RAI, M3RSC, M3RSE, M3RSI, M3RSP should be ordered during execution of scripted procedure.

IPA03 Warning1: IPA03 delivers AC RWANV-1286 (via EPA47) which replaces R01MCXJN-3732 never delivered by PLM

Warning2: IPA03 delivers AC RWAUA-2739 (via EPA56). During AC loading, messages will be discarded with resource limitation reason. Any Time Subscription Interrogation operations request should be reattempted.

Warning3: IPA03 delivers AC RWAYJ-1733 (via EPA63) which clashes with R01MCXJN-8933.


7 (25)





Warning4: IPA03 delivers AC NWAJQ-0748 which replaces N1ATCADL-0123.

Warning5: IPA03 delivers AC RWAXC-2166. If MSC administration commands (MGECI, MGECC, MGECP, MGECE, MGRCI, MGRCC, MGRCE, MGRCP) returns FUNCTION BUSY without obvious reason, execute the following commands to set variables CBLOCKPROCESSSTATE (BAN=1) and COMMANDSTATE(BAN=2) of block MERNA to zero:

TEST SYSTEM; PRINT VAR MERNA 0-:2; SET VAR MERNA 0-:2=0; PRINT VAR MERNA 0-:2; PRINT VAR MERNA 1; SET VAR MERNA 1=0; PRINT VAR MERNA 1; END TEST;

No MSC administration commands (MGECI, MGECC, MGECP, MGECE, MGRCI, MGRCC, MGRCE, MGRCP) and no system backup (SYBUP) should be ongoing at the time of the above procedure.

Proceed with the following implementation instruction only if TTC feature is active. Warning6: IPA03 delivers AC NWAXC-2023 (via EPA56). This AC needs to be followed by a restart when TTC feature is active. The value of AXE parameter TTCSPECIFICFEAT should be checked with the following command DBTSP:TAB=AXEPARS,SETNAME=AMCCHSF,NAME=TTCSPECIFICFEAT; If the value is 1 a restart is needed in order to clear possible corrupted MOUS records. If the value is 0 there is no need of a restart.

Proceed with the following implementation instruction only in case of HLR environment. Warning7: IPA03 delivers AC RWAUA-2774 (via EPA58). This AC modifies File Output function in the HLR. It is recommended to perform the file output after AC loading.

During the script execution several faults or corruptions may be detected. Also some cleanup procedures included in the script execution may fail. In these cases proper pop-up windows will inform the user for the way forward or the proposed workaround. Below you can see a list of all the possible pop-up windows you may meet during the package deployment.


8 (25)





Warning8: IPA03 delivers AC RWAZJ-0613 (via EPA48) with scripted clean up procedure. If the procedure detects conditions which could lead to corruption, a pop-up window will inform the costumer to contact Design Maintenance to check whether corruption exists or not.

Warning9: IPA03 delivers AC RWABW-0193 (via EPA59) with scripted clean up procedure. If the procedure fails, a pop-up window will indicate that next line of support should be contacted.

Warning10: IPA03 delivers ACs RWAYJ-1741 and MWAUA-2731 (via EPA72) with scripted clean up procedure. This AC is only valid for CWTS standard. If the procedure fails, a pop-up window will indicate that next line of support should be contacted.

Warning11: IPA03 delivers ACs RWAXC-2104 and RWAXC-1768 (via EPA72) with scripted clean up procedure. In case of three unsuccessful attempts of SAADI failure, a pop-up window will inform the customer that the CUP has failed (partly executed), so the previous steps should be performed manually by the costumer, after the package loading.

Warning12: IPA03 delivers AC MWAOH-0108-M0001 which provides solution for the created DIP quality supervision alarm when DIPS are not connected. If the cleanup procedure detects at least one faulty alarm "DIGITAL PATH QUALITY SUPERVISION", a popup will inform the customer that actions mentioned in the DOC folder MWAOH0108_cleanup_IPA03.txt should be followed manually.

During the script execution several commands are not allowed to be given due to scripted procedures included in the cp-script. All these cases are below highlighted in order for the user not to order a command which shouldn’t be ordered at all. Warning13: IPA03 delivers AC RWABW-0193 (via EPA59) with scripted clean up procedure. During cleanup execution, no SAAEP command or modification of SAE 604 in block SHCC should be executed.

Warning14: IPA03 delivers AC RWAYJ-1748 (via EPA68). S7HPI or S7HPP commands shouldn't be ordered during AC loading.

Warning15: IPA03 delivers AC RWAUA-2800 (via EPA68). Commands HGSDP and HGSDC should not be executed during AC loading.

Warning16: IPA03 delivers AC RWAXC-2104 and RWAXC-1768 (via EPA72) with scripted clean up procedure. Commands ERESC, EREPI, EREPE, ERESP should not be given during cleanup procedure. Warning17: IPA03 delivers AC MWAUA-2731 (via EPA72) with scripted clean up procedure. SAE 261, SAE 600 and SAE 601 in HCUG block should not be increased. Commands HGCUI, HGCUE and HGCSC should not be executed during cleanup execution


9 (25)





Warning18: IPA03 delivers AC RWAYJ-1741 (via EPA72) with scripted clean up procedure. During cleanup procedure SAAxx, UAXXX or C7Nxx should not be executed.

Warning19: IPA03 delivers AC RWAQA-0324 with scripted clean up procedure. During execution of procedure C'EXANP shouldn't be given.

Warning20: IPA03 delivers AC RWAXC-2126 with scripted clean up procedure. No size alterations on SAE 36 or SAEs in block MTV should be executed during procedure execution.

Warning21: IPA03 delivers AC RWAMH-0980 (via EPA58). EXRBC command should not be ordered while loading AC. Corruption may exist if parameter DNSEF is/was set on any SIP route with the below possible effect: EXROP shows incorrect value of generic parameter or generic parameter which is not supported on outgoing route. In case of above described problems please contact DM.

Warning22: IPA03 delivers AC RWAYJ-1723 (via EPA59). SAAEP and EXRBC commands should not be ordered during execution of scripted procedure included in cp_script. SAEs in TPC should not be altered during SII execution.

Below you can see all the actions needed after the package deployment which demands a Large Restart. The customers of Dual Blade environment can skip all the following needed actions if they plan a Large Restart. (The customers of Blade Cluster environment should ignore all the below warnings, a Large Restart has already cleaned all the following issues.) Warning23: IPA03 delivers ACs RWABW-0193 (via EPA59), RWAYJ-1628 and RWAYJ-1616 (via EPA52, also delivered with EPA10). The above AC’s need restart to be introduced.

Warning24: IPA03 delivers AC MWAOI-0053. Possible MUP hanging will be cleared after the performance of a restart.

Warning25: IPA03 delivers AC NWAXC-2038. Possible hanging records in blocks SHSMS and CHVIEW may exist. These hangings will be cleared during next small/large restart.

Warning26: IPA03 delivers AC RWAOI-0054 and RWAMU-0334. Restart is needed to clear possible hangings/corruption. Warning27: IPA03 delivers AC RWAOI-0055. In case hanging command GSxxx occurs, small restart is needed to clear it.

Warning28: IPA03 delivers AC RWAXC-2022. Possible hanging records in blocks SHSMS and CHVIEW may exist. These hangings will be cleared during next small/large restart.


10 (25)





Warning29: IPA03 delivers RWAXC-2141. After AC loading a system restart is required in order the NRNTSRRS2UTOT counter to be operational and get correct values.

Warning30: IPA03 delivers AC RWAXC-2170 which requires restart to be introduced.

Warning31: IPA03 delivers AC RWAXC-2130. In case of counter RCNTNTRAL corruption, SMALL restart needs to be performed in order to clear the corruption.

IPA02 Warning1: IPA02 delivers AC RWAYJ-1657 (via EPA19) with scripted clean up procedure. No commands M3Rxx should be executed.

Warning2: IPA02 delivers AC RWAED-0164 (via EPA19) with detection and clean up procedure. If the detection or the cleanup procedure fails, a pop-up window will indicate that next level of support should be contacted in order to raise a TR and request a dedicated clean up procedure. No size alterations on SAE 36 or SAEs in blocks MTV/ MTVLCS/ MTVCO should be executed.

Warning3: IPA02 delivers AC RWAJQ-0738 (via EPA28) with clean up procedure. If the cleanup procedure fails, a pop-up window will indicate that next level of support should be contacted.

Warning4: IPA02 delivers RWAXC-1866 and RWABW-0185. These ACs have a scripted detection procedure to check whether automatic release of hanging software records needs to be initiated manually by the user. The customers will be informed via pop up window in order to manually execute the command SYFDC:START,AUTOREL=IMMREL;

Warning5: IPA02 delivers RWAYJ-1567 (via EPA34). This AC has a scripted cleanup procedure. During cleanup procedure do not use any C7x command for define, undefine, change and print signaling points, associated adjacent signaling points, signaling links, link sets, routes, MTP restart data or any other MTP related commands. Also, no size alterations on SAE 164 should be executed during cleanup procedure.

Warning6: IPA02 delivers RWAXC-1927 (via EPA36). When All blades have finished updating, a pop up will appear (only in BC environment) and the user must perform some manual actions before continuing. The needed actions are described in RWAXC1927_manual_EPA36.txt in the DOC folder.

Warning7: IPA02 delivers RWABW-0181. During clean up execution no SAAEP command should be executed. If the cleanup procedure fails, a pop-up window will indicate that next level of support should be contacted.


11 (25)





Warning8: IPA02 delivers NWAVI-0018. Cleanup Procedure is included in the cp ex update script. AC conflicts with TC N1ATCAHI-0010 which is never delivered by PLM. AEBOC command should not be executed during AC loading. If the cleanup procedure fails, a pop-up window will indicate that next level of support should be contacted.

Warning9: IPA02 delivers RWAXC-1840 (via EPA19). This AC increases number of Location Update Rejects, as a result of unsuccessful busymarking for Location Update of subscribers marked for disconnection in VLR due to Location Cancellation.

Warning10: IPA02 delivers RWANV-1268. This AC should not be loaded together with the MDE:12483,12369,12167.

Warning11: IPA02 delivers RWAXC-1835. Possible corruption will be cleared with large restart in MSC or cleared automatically when a successful positioning is made towards subscriber with current location only.

Warning12: IPA02 delivers RWAMH-0965. In case that STS counters show ‘0’ for route name (for object type SIPCODSTAT), please contact Design Maintenance to provide clean up procedure.

Warning13: IPA02 delivers RWAXC-1918. After AC loading a restart is required only for the blades in Blade Cluster environment to reset hanging variable ALARM(BAN 8) after AC loading.

Warning14: IPA02 delivers RWAHE-1725. After large restart is needed on BC nodes, on each blade (in isolated mode) after AC loading

Warning15: IPA02 delivers RWAXC-1847 that replaces EC-HR45122 never delivered by PLM. Any possible faulty values of the counters will be corrected after large restart for Blade environment, small or large for Dual Blade.

Warning16: IPA02 delivers RWAUA-2687. SMALL restart is required to inform external application about changes. After restart Statistics and Traffic Measurement, Translation Tables should by updated by APG: stmttu command.

Warning17: IPA02 delivers NWANV-1253 that clashes with Market Corrections: N01XJ-3389 and N01XJ-1486.

Warning18: IPA02 delivers RWAXC-1814. If DBRS functionality (Destination Based Routing of MO-SMS) is active and restart with RELOAD has occurred before AC loading, then it is possible variable NUMRECLIST to be corrupted. This could lead to event "H'0008 H'0E14 H'1C10" or similar events. Rebuild of DBRS data with commands MGDRE/MGDRI will be required, in this case. For possible alternative, contact with DM. DBRS functionality is active when command DBTSP indicates that the value of AXE PARAMETERS DBRSF, DBRSACT, DBRSSCCN and DBRSSTRESC is equal to 1.


12 (25)





Warning19: IPA02 delivers RWAXC-1910. If the operator observes abnormal behaviour of commands HGSTI, MGSTI, then a TR should be created towards DM in order to take specific measures for this particular corruption

Warning20: IPA02 delivers RWAXC-1923. Possible corruption of Counter BPSAECOUNTERSFILESAECNTTRAL will be cleared with a large restart for Cluster environment, and a small one for Classical environment

IPA01 Warning1: IPA01 package delivers SCR file for the Statistic Counters. Before implementing IPA01 customer should check with command SAAEP:SAE=888,BLOCK=LASCS; the value of the NI (Size of Statistics Counter Rules (SCR) file areas) and increase it if needed to NI=1000 with command SAAII:SAE=888,BLOCK=LASCS,NI=1000;

Warning2: IPA01 delivers AC Z02BL-1298 which defines the signal READRPBTEST. The user might observe a signal conflict during IPA01 deployment, since this signal has been wrongly defined on the GA dumps.

Reason: On APZ P19.0, during APZ LSV phase, RPCPD had been opened to CAAZA 107 3200 M08S R1A01. Due to this, Z02BL-1127 is no longer valid and does not exist in P19.0 track. But the definition of signal READRPBTEST has not been removed accordingly. And such fault has been inherited till P19.0 GA

The script may stop with fault:

LASAL:SIGNAL=READRPBTEST,FORMAT=0,INTWK=CPCP,MULT=NO,TYPE=CF;

NOT ACCEPTED

FAULT CODE 512

SIGNAL NAME ALREADY USED

The user then should select to continue. On the displayed pop-up window choose the option:

“Correct the fault manually and Continue reading of command file by IOCCI”

The script will continue with rest of execution.

Warning3: IPA01 delivers RWAXC-1624. After loading the AC, command NRGGP:MGG=ALL; should be given and the structure of Media Gateway Groups should be validated against the DT of the exchange. Any deviation from the DT should be corrected accordingly.

Warning4: IPA01 delivers RWAZI-0014. After loading the AC, the possible hanging will be cleared in next system restart.


13 (25)





Warning5: IPA01 delivers RWAFZ-0391. After loading the AC, small restart should be performed for clasic MSC and SPX after AC loading in order counter CMSGREROUTCNT to be operational and get correct values

Warning6: IPA01 delivers RWAUA-2587. After loading the AC, small system restart is needed to clear possible existing corruption caused by hanging process

Warning7: IPA01 delivers RWAUA-2585. After loading the AC, Small Restart is needed to clear corruption in C7TCP block.

Warning8: IPA01 delivers RWAXC-1656. This AC requires restart in order to be activated.

Warning9: IPA01 delivers RWAJQ-0724. The counters IUOCC, OTRALCNT_BS and OTRALCNT are not cleared with the AC, however they are cleared with LARGE system restart.

Warning10: IPA01 delivers RWAXC-1692. Possible CB hangings will be cleared automatically, or in next System Restart. A system restart (of any type) should to be performed if congestion on SAE 500 is observed.

Warning11: IPA01 delivers RWAJQ-0719. Possible ABL devices will be recovered during normal maintenance customer procedure.

Warning12: IPA01 delivers RWAFZ-0381. Possible CB hangings will be cleared automatically, or in next System Restart.

Warning13: IPA01 delivers RWAXC-1732. During loading of the AC no MGSI* commands should be ordered. If the fault solved with the AC occurred MGSIE may need to be ordered again to remove the cooperating SGSN from the MSC/VLR.

Warning14: IPA01 delivers RWAXC-1646 Small restart is recommended after loading this AC in order to restore counter SAECNTRECORDCNTTRAL.

Warning15: IPA01 delivers RWAUA-2559. This AC has a Cleanup procedure included in the cp_ex remote script. In case of failure popup window will indicate that the procedure should be repeated manually RWAUA2559_cleanup_IPA01.txt. SAE600 in SDA block should not be increased during cleanup.

Warning16: IPA01 delivers RWAXC-1781. Possible corruptions may exist in MCVLRD. If there is abnormal behavior during definition/removal/printout of cooperating VLRs (e.g.MGCVI, MGCVE or MGCVP fail) then a TR should be created towards DM in order to create a specific cleanup procedure.

Warning17: IPA01 delivers RWANV-1230. This AC requires a RESTART to be activated.


14 (25)





Warning18: IPA01 delivers RWAXC-1759-M0001 and RWAXC-1759-M0002. These AC’s require RESTART to be activated.

Warning19: IPA01 delivers RWAFT-0161-M0001 and RWAFT-0161-M0002. Any possible existing hangings will be cleared in next system restart for classic environment.

Warning20: IPA01 delivers RWAFT-0165-M0001 and RWAFT-0165-M0002. Any possible existing hangings will be cleared in next system restart for classic environment.

Warning21: IPA01 delivers RWAEF-0264. It is recommended after AC loading, that a Large restart should be performed in order to clean up faulty statistics from MAIPCM routes.

Warning22: IPA01 delivers Z02QP-0044. Command ALLIP; should NOT be executed during AC loading

Warning23: IPA01 delivers Z02OG-0122. Restart is needed in order to activate the feature.

Warning24: IPA01 delivers RWAYJ-1616. The AC has a Cleanup procedure included in the cp_ex remote script. This AC requires Restart in order to be introduced.

Warning25: IPA01 delivers RWAUA-2638. The AC has a Cleanup procedure included in the cp_ex remote script. During cleanup execution, SAE increase, print or decrease must not be performed for SAE 500 in block HRSMAP. In case of failure, a popup window will indicate that next level of support should be contacted.

Warning26: IPA01 delivers RWABW-0170 and RWABW-0166. These AC’s have a scripted detection procedure to check whether automatic release of hanging software records needs to be initiated manually by the user. The customers will be informed via pop up window in order to manually execute the command SYFDC:START,AUTOREL=IMMREL;

Warning27: IPA01 delivers X02QP-0043. EC-HN67073 should be removed before loading this AC

Warning28: IPA01 delivers Z02BL-1316. The AC has a Cleanup procedure included in the cp_ex remote script. The procedure detects if a conflict between ETHB-n's IP address and PING-A's exists. If the procedure detects conflict, a popup window will indicate that a manual clean up procedure Z02BL1316_cleanup_IPA01.txt included in the DOC folder should be followed.


15 (25)





Warning29: IPA01 delivers AC RWAUA-2620 with scripted detection and clean up procedure. During execution: - no CAMEL data provisioning neither subscriber removal must be ongoing. - no change of CSI Activation state with HGSDC command must be ongoing - no SAE 261 size change must be ongoing. The script checks if reactivation of the CSI Activation status with HGSDC would be needed. (e.g. in case it is observed that CAMEL data is not sent to the network (VLR/SGSN) despite subscriber, who is allowed to use CAMEL, is provisioned with CAMEL data ). In that case, a pop-up window will inform the user accordingly. Please then order HGSDC manually. Also if the scripted cleanup procedure fails, a pop-up window will indicate that next level of support should be contacted in order to raise a TR and request a dedicated clean up procedure.

Warning30: IPA01 delivers AC RWAHE-1704 with scripted detection and clean up procedure applicable only for classical environment (non BC). If detection or the cleanup procedure fails, a pop-up window will indicate that a small restart is needed in order to clear any possible corruption.

Warning31: IPA01 delivers AC RWAUA-2624 with scripted cleanup procedure included in the cp_ex remote script. HGHSE, HGHSI, HGMHE, HGMHI commands must not be performed during execution of SII (halted state of Redundancy function should not be initiated or ended during execution of SII).

Warning32: IPA01 delivers AC RWAOI-0048. Please before loading this AC refer to RWAOI0048_manual_IPA01.txt. In this file, manual actions before and after AC loading are described.

3.4 Traffic Impacting Warnings No traffic impacting warnings were observed during package implementation.

3.5 Manual Handling In case any manual activity is needed, it should be performed using an extra command handling terminal. Manual intervention might be necessary in a fault situation or to perform a special implementation or clean up.

3.5.1 Start extra command handling terminal Start a Command handling terminal (Tools -> AXE Management Tools -> Command handling) from the workspace menu in OSS and connect to the desired Network Element.

All actions that are to be taken towards this terminal are mentioned in the instruction as 'take action from "other" terminal'


16 (25)





3.5.2 Manual Parameter settings There are no manual parameter settings.

3.5.3 Manual Clean-up procedures needed for all environments. Below is a list of all manual procedures which are needed for all environments. All the following manual procedures should be executed after AC loading.

Package ID AC ID Comments IPA04 RWANV-1329 RWANV1329_manual_IPA04.txt is included

in the DOC folder. The procedure is updating the counter NODBCCTOT.

EPA92

RWAHE-1759

Manual procedure is applicable only for ANSI, in case screening masks are loaded. The procedure is included in the DOC folder of the package (RWAHE1759_manual_EPA92.txt)

EPA92 RWAYJ-1773

Manual clean up procedure included under the DOC/HELP folder of the package (Help_procedure_RWAYJ1773_EPA92.txt)

EPA92 RWAXC-2297 RWAXC2297_manual_EPA92.txt is included in the DOC folder of the package

EPA58 RWAHE-1735 RWAHE1735_manual_EPA58.txt is included in the DOC folder. This manual loading procedure describes all the necessary steps for the successful loading of this AC, and should be followed only by JAPAN market.

EPA56 RWAXC-2039 RWAXC2039_manual_EPA56.txt is included in the DOC folder.

EPA47 RWAHE-1729 RWAHE1729_cleanup_EPA47.txt is included in the DOC folder of the package. This manual cleanup procedure fixes the problem where UPD24R devices are incorrectly connected to RTDMA external SNTs supporting DIP connection.

IPA03 RWAXC-2138 RWAXC2138_cleanup_IPA03.txt is included in the DOC folder. This manual cleanup secures that the reported faults will not occur, by the initialization of the affected variables through the redefinition of existing TRDIP measurements.

IPA02 NWANV-1253 NWANV1253_manual_setting_IPA02.txt is included in the DOC folder. This manual


17 (25)





setting changes the SSN value to the new value of '147'.

IPA01 RWAUA-2559 RWAUA2559_cleanup_IPA01.txt is included in the DOC folder. This cleanup procedure checks value of XMSYSMODE AXE parameter. If it is active, size of SAE600 in SDA block is checked. If this size is greater then zero, SAE600 is decreased to zero and database table AXEPARFAULTS is checked for the fault 'VALUE REJECTED DURING FC' for XMSYSMODE AXE Parameter.

IPA01 RWAOI-0048 RWAOI0048_manual_IPA01.txt is included in the DOC folder.This manual action is used in order to keep the value of 644(x) printed before SET VAR during AC loading. This value (x) will be used during AC removal (if needed) or if customer wants to recover previous value.

IPA01 RWAHE-1689 RWAHE1689_cleanup_EPA06.txt is included in the DOC folder. This manual cleanup procedure clears the corruption that exists in case customer has received FC on EXDRI command. UPD24R is a multiple block meaning that this cleanup procedure should be executed for all applicable clones.

3.5.4 Manual Clean-up procedures needed only for Dual Blade and SPX Below you can find the manual procedure which is needed only for Dual Blade environment and SPX. The following manual procedure should be executed after AC loading (after the package deployment).

Package ID AC ID Comments IPA02 RWAOH-0096 RWAOH0096_manual_EPA34.txt is

included in the DOC folder. This manual cleanup procedure clears all ATM fault supervision alarms on not connected VC individuals.

In case a Large Restart is planned or can be given manually (regarding Dual Blade environment), you can skip all the below described actions (no action is needed regarding SPX since a Large Restart is given automatically via the script)

Package ID AC ID Comments


18 (25)





IPA03 MWAOH-0103 MWAOH0103_detection_IPA03.txt is included in the DOC folder. This clean up procedure checks for any LPs wrongly shown as ABL + UNEQ and clears the possible corruption.

IPA03 RWAXC-2109 RWAXC2109_cleanup_IPA03.txt is included in the DOC folder. This clean-up procedure clears possible hanging in block LAD when a MT SMS is handled by a blade other than the primary of the subscriber.

IPA03

RWAMU-0334

RWAMU0334_cleanup_IPA03.txt is included in the DOC folder. This AC solves the issue where we had incorrect charging since STOPCHARG was not received in Block CHUPATT. This manual procedure clears possible corruption that leads to continuous sending of signal CHUNITS due to individual hangings in block CHUPAT.

IPA03 MWAOI-0053 MWAOI0053_cleanup_IPA03.txt is included in the DOC folder. Restart is needed to clear possible previous MUP hangings.

EPA47 RWAYJ-1684 RWAYJ1684_cleanup_EPA47.txt is included in the DOC folder. This manual procedure clears possible hangings of SAE605 and corruptions of variables and linked lists.

IPA02 Z02BL-1341 Z02BL1341_manual_cleanup_IPA02.txt included in the DOC folder. This manual cleanup triggers signal FIXSREGBOARD so that the required information for the registered boards is updated.

IPA02 RWAHE-1721 RWAHE1721_cleanup_EPA29.txt is included in the DOC folder. This manual cleanup procedure clears possible hanging in UPDNAMR block. UPDNAMR is a multiple block meaning that this cleanup procedure should be executed for UPDNAR1 clone when applicable.

IPA02 RWAYJ-1676 RWAYJ1676_cleanup_EPA25.txt, procedure included in the DOC folder. This manual cleanup procedure clears corruption in block SIPCO.

IPA01 RWAYJ-1624 RWAYJ1624_cleanup_IPA01.txt, included in the DOC folder. This manual cleanup procedure clears corruption in block TPLAT.


19 (25)





IPA01 RWAXC-1361 RWAXC1361_cleanup_IPA01.txt, included in the DOC folder. This manual cleanup blocks and de-blocks every SCB-RP. It should be executed after AC loading.

IPA01 RWAYJ-1641 RWAYJ1641_cleanup_EPA10.txt, included in the DOC folder. This manual cleanup procedure clears common store variables CLSINIT and CMTPREQPEND. It should be executed after AC loading.

Below you can find all the manual cleanup procedures which use SYFAP- SYFIP- SYFRI command sequence in order to clear all the following possible hangings. In case a Large Restart is planned or can be given manually, you can skip all the following described actions.

Package ID AC ID Comments IPA04 RWAXC-2553

RWAXC2553_manual_IPA04.txt is included in the DOC folder of the package. This procedure clears possible hangings may occur in MSDH chain (MSDH and MTV) during a Location update, if disconnection is received from BSC

IPA04 RWAXC-2450 RWAXC2450_manual_IPA04.txt is included in the DOC folder of the package. This procedure clears possible hangings may occur in MMM block during the unsuccessful transmission of a location report message

IPA04 RWAXC-2429 RWAXC2429_manual_IPA04.txt is included in the DOC folder of the package. Hanging may occur in MUSSPAP block during a Mobile Initiated USSD. This hanging clears with this manual procedure.

IPA04 RWAXC-2380 RWAXC2380_manual_IPA04.txt is included in the DOC folder of the package. This procedure clears possible hangings in MSGSPRO chain (MSGSPRO and MSGSMH) during a CS-FB when an unsuccessful Mobile Originating SMS is also ongoing

IPA04 RWAXC-2341 RWAXC2341_manual_IPA04.txt is included in the DOC folder of the package. This


20 (25)





procedure clears possible hangings in MBPAG-MUPAG-MPAG blocks during MT-LR

IPA03 RWAXC-2176 RWAXC2176_cleanup_IPA03 included in the DOC folder. This procedure clears possible hangings in MTACC-MSLRAP block.

IPA03 RWAXC-2087 RWAXC2087_cleanup_IPA03.txt included in the DOC folder. This procedure clears possible hangings in MSMO block.

IPA03 RWAXC-2027 RWAXC2027_cleanup_IPA03.txt included in the DOC folder. This procedure clears possible hangings MREPR block.

EPA49 NWAXC-2006 NWAXC2006_cleanup_EPA49.txt is included in the DOC folder. This procedure clears possible hangings in MSMOAP block.

IPA02

RWAXC-1945 RWAXC1945 _cleanup_IPA02.txt is included in the DOC folder. This manual cleanup procedure clears possible hanging in MFRNAP block.

IPA02 RWAUA-2706 RWAUA2706_ cleanup _IPA02.txt included in the DOC folder. This manual cleanup procedure clears possible hanging.

IPA02 RWAZJ-0608 RWAZJ0608_cleanup_IPA02.txt included in the DOC folder. This manual cleanup procedure clears possible hanging in BIPHT block. BIPHT is a multiple block meaning that this cleanup procedure should be executed for BIPHTI clone when applicable.

IPA01 RWAXC-1752 RWAXC1752_cleanup_IPA01.txt, included in the DOC folder. This manual cleanup procedure clears possible hangings in C7CO block.

IPA01 RWAFZ-0384 RWAFZ0384 _cleanup_IPA01.txt, included in the DOC folder. This manual cleanup procedure clears possible hanging in TPC block.

IPA01 RWAFT-0153 RWAFT0153_cleanup_IPA01.txt, included in the DOC folder. This manual cleanup procedure reset the value of variable SESSP:ACTIVELINK properly.

IPA01 RWAED-0157

RWAED-0157_cleanup_IPA01.txt, included in the DOC folder. This manual cleanup procedure clears possible hanging in MGPRO block.


21 (25)





IPA01 RWAZJ-0594 RWAZJ0594_cleanup_IPA01.txt, included in the DOC folder. This manual cleanup procedure clears possible hanging in BIPHT block. BIPHT is a multiple block meaning that this cleanup procedure should be executed for BIPHTI clone when applicable.

IPA01 RWAEF-0248 Manual Clean Up procedure included in package DOC folder, RWAEF0248_cleanup_EPA06.txt

IPA01 RWAEF-0240 Manual Clean Up procedure included in package DOC folder, RWAEF0240_cleanup_EPA06.txt

4 Package Revision History 4.1 Package Revision A

Updated: 2015-07-10

IPA04 has been released in Rev. A.

5 General Warnings 5.1 CP software implementation warnings

The CP must be working in normal/parallel state.

The latest system backup of CP must be available in RELFSW0 and should not be older than 36 hours.

No other activity than package loading shall be ongoing in the exchange.

Separation of the CP is needed to implement the package.

5.1.1 Traffic handling The CP-EX procedure does not cause any restarts. This implies that corrections which need a restart to function properly cannot be implemented.

There will be no disturbances in traffic handling.

NOTE: The package shall be introduced during low traffic hours. 5.1.2 Fallback

In case of fallback the system will perform a LARGE RESTART.

5.2 Other implementation warnings 5.2.1 Exchange requirements and preparation

The exchange shall be free of any major faults. In particular:


22 (25)





• During the implementation all data links that are not needed for the implementation should be blocked. NMC and local staff should be informed.

• It is recommended to perform an output of TT-files to movable media prior to the implementation.

5.2.2 Error handling An Error message will be displayed if the system cannot automatically recover from a problem.

Each implementation script is also provided with a FALLBACK part that allows a menu driven fallback (see FALLBACK section of the relevant script or implementation instruction).

A fallback will always be performed in steps. Thereby the user can decide at certain key points if he wants to fallback a step further or to continue with the execution.

There are the following possibilities to access the FALLBACK menu:

• At a major fault: if the script detects a fault which can not be automatically solved, an error menu will pop up. If the detected problem is considered as major fault the pop up menu will have a FALLBACK option.

• At any time: with the help of the DESPERADO subroutine the FALLBACK menu can be called by pressing the disconnect button.

Furthermore, a recover routine is able to recall the old script status if the script has been aborted abnormally. This could be for example after the reboot of the UNIX system caused by a central power failure.

6 General Warnings for MSC-S BC 6.1 CP software implementation warnings

The CP must be working in normal/parallel state.

The latest system backup of CP must be available in RELFSW0 and should not be older than 36 hours.

No other activity than package loading shall be ongoing in the exchange.

Separation of the SPX is needed to implement the package.

Isolation of the Blades is needed for implementation.


23 (25)





6.1.1 Traffic handling Isolation of the Blades is needed for implementation. Traffic could be disturbed, depending on the timer set for isolation.

SPX only: A large restart will be issued in SPXs in order to clear corruptions after IPA01 loading. That restart will not happen at the same time to both SPXs. So the traffic impacts will be minimal.

6.1.2 Fallback In case of fallback the system will perform a LARGE RESTART.

6.2 6.2 RP software implementation warnings It shall be verified that the APZ is functioning without major alarms and disturbances in

6.3 Other implementation warnings 6.3.1 MSC-SBC specific warnings

When updating the Blade Cluster, only one job at a time should be run. Running parallel jobs on one Blade Cluster might affect the traffic, because of the loss of the control over the traffic isolation.

Within one job only Blades that belong to the same Blade cluster should be included.

PLM MSC recommends that an experienced operator chooses the update parameter values at the beginning of the implementation. For example, the following values for the parameters can be chosen within the SMOinfo.xml execution:

User Interaction Level - the level of pop-ups appearing during the implementation (1-all, 4-none). The default one is 3 for all scripts, though in order to have better overview for the CP activity 2 can be used.

♦ Traffic_Delay - the time given after the command CQTII is issued. After that much time passes, the ongoing calls will be stopped. The default value is 20 minutes, though normally most of the calls are ended after 10 minutes.

♦ Traffic_Test_Duration - is the time given to the operator to run manually Traffic Tests after the implementation.

♦ New_Exchange_Header - is the name of the new dump that is going to be active after the implementation of the package.

The following issues may occur during an implementation:


24 (25)





If the connection to an AD device is lost, choose the option: "Try to reconnect to other device".

♦ If the report of the execution of "PTCPL" or "PTCOE" sometimes fails, please choose to repeat the command again.

♦ If any AP command fails because of loss of connection, "Try to reconnect" or "Repeat the command again"

Before the implementation of the package, dump the current dump in RELFSW0, so that you have a correct reload dump after the MW implementation. If you are sure that the correct dump is already in the RELFSW0, then perform SYREI:RANK=RELOAD, so that you are sure that the level of corrections in RELFSW0 and the working dump are the same.

How to show the NE name within the OPS GUI & Pop-up windows:

♦ open the OPS GUI (from workspace menu -> Tools -> AXE management Tools -> Operations Procedure Support)

♦ Now chose View -> Options and select the Pop-up tab.

♦ Tick at least the boxes for External System or even all 5 boxes for maximum information.

In a case you do not use the default User Interaction Level (UIL) - "Display All Message Types" but you decide to change to a higher one, please note that you need to specify the dump header in the SMO application when the job is created - in the CP tab: NE Parameters.

Details: The script automatically gives a new name in the exchange header when a higher Interaction Level (ie 3 - Display warnings - errors) is used. The default UIL for the CP script is the lowest (1). It is possible to define the name of the exchange header for each CP in SMO application when the job is created: In the "Job Parameters" window - CP tab - select the "NE Parameters" tab. Then choose one of the listed CP's and edit the field "New Exchange Heading". If this is not specified the script will dump with a default name (the existing one plus adding this "_V1" at the end).

6.3.2 Exchange requirements and preparation The exchange shall be free of any major faults. In particular:


25 (25)





• During the implementation all data links that are not needed for the implementation should be blocked. NMC and local staff should be informed.

6.3.3 Error handling An Error message will be displayed if the system can not automatically recover from a problem.

Each implementation script is also provided with a FALLBACK part that allows a menu driven fallback (see FALLBACK section of the relevant script or implementation instruction).

A fallback will always be performed in steps. Thereby the user can decide at certain key points if he wants to fallback a step further or to continue with the execution.

There are the following possibilities to access the FALLBACK menu:

• At a major fault: if the script detects a fault which can not be automatically solved, an error menu will pop up. If the detected problem is considered as major fault the pop up menu will have a FALLBACK option.

• At any time: with the help of the DESPERADO subroutine the FALLBACK menu can be called by pressing the disconnect button.

Furthermore, a recover routine is able to recall the old script status if the script has been aborted abnormally. This could be for example after the reboot of the UNIX system caused by a central power failure.

MSC 13A IPA04 Package Information

Documents

update package

package status

package special handling

package revision history

general warnings

manual handling

general information

traffic handling