generic failure report

5/28/2018 Generic Failure Report

1/20

Nokia MMS Center 2.1

Generic Failure Report

Release Documents

DN00148914Issue 4a-0 en

Nokia Corporation 1 (20)


2/20


The information in this document is subject to change without notice and describes only theproduct defined in the introduction of this documentation. This document is intended for theuse of Nokia's customers only for the purposes of the agreement under which the document issubmitted, and no part of it may be reproduced or transmitted in any form or means withoutthe prior written permission of Nokia. The document has been prepared to be used by

professional and properly trained personnel, and the customer assumes full responsibilitywhen using it. Nokia welcomes customer comments as part of the process of continuousdevelopment and improvement of the documentation.

The information or statements given in this document concerning the suitability, capacity, orperformance of the mentioned hardware or software products cannot be considered bindingbut shall be defined in the agreement made between Nokia and the customer. However,Nokia has made all reasonable efforts to ensure that the instructions contained in thedocument are adequate and free of material errors and omissions. Nokia will, if necessary,explain issues which may not be covered by the document.

Nokia's liability for any errors in the document is limited to the documentary correction oferrors. NOKIA WILL NOT BE RESPONSIBLE IN ANY EVENT FOR ERRORS IN THISDOCUMENT OR FOR ANY DAMAGES, INCIDENTAL OR CONSEQUENTIAL (INCLUDINGMONETARY LOSSES), that might arise from the use of this document or the information in it.

This document and the product it describes are considered protected by copyright accordingto the applicable laws.

NOKIA logo is a registered trademark of Nokia Oyj.

Other product names mentioned in this document may be trademarks of their respectivecompanies, and they are mentioned for identification purposes only.

Copyright Nokia Oyj 2002. All rights reserved.

2 (20) Nokia Corporation DN00148914Issue 4a-0 en


3/20

Contents

Contents

Summary of changes .............................................................................................4

1 Corrected from MMS Center 2.0............................................................51.1 5477 Control stops and restarts all processes when an

application is added..................................................................................51.2 6007 MGW receiver filters out addresses in the recipient list ..................61.3 6195 Addresses in the recipient list are filtered out in mail-

terminated cases......................................................................................61.4 10872 Reinitialising an application interface with invalid

parameters gives a wrong starting status.................................................71.5 11147 Disk space allocation for smart blobs: metadata fills up

too early ...................................................................................................81.6 11315 xscmanmx.cf actions-parameter does not work

correctly............................................................................. .......................81.7 11565 Delivery report corrupted if the message is routed

through inter-MMS Center, e.g., due to incorrect configuration .............101.8 11625 Event log full does not generate an alarm to the GUI .................11

2 Open problem reports..........................................................................122.1 8208 Database exceptions cause a generic alarm instead of a

database-specific alarm .........................................................................122.2 10859 One event log is lost if writing into the database fails..................122.3 11337 Scripts run by crontab in a stand-alone database node,

write / send error messages generated..................................................13

2.4 12677 Xlw_show tool: Pipe error when used with more ........................142.5 12784 Content adaptation logs are not shown correctly ........................142.6 13092 Small memory leak in the kernel .................................................152.7 13239 Sometimes the GUI is not able to show alarms ..........................162.8 13408 Loading event logs from tape gives an error...............................162.9 13442 IBM script does not work every time ...........................................172.10 13558 Content adaptation does not support cid references for

media components in SMIL....................................................................182.11 13599 COT drops lines from host-specific files......................................19




4/20


Summary of changes

Date Issue Summary of changes

March 2001 1-0 First issue.

May 2001 1a-0 Corrected problem reportsremoved from document.

October 2001 2-0 en Revised for release MC1 CD1.

November 2001 2a-0 en List of problem reports updated.

May 2002 3-0 en Revised for MMS Center 2.0.

June 2002 3a-0 en Updated after pilot phase.

November 2002 4-0 en Updated for MMS Center 2.1.

December 2002 4a-0 en List of problem reports updated.



5/20

Corrected from MMS Center 2.0

1 Corrected from MMS Center 2.0

1.1 5477 Control stops and restarts all processeswhen an application is added

Priority

B2

Visible to end user

No

Created

30.3.2001

Description

When the user adds a new application instance using the graphical user interface

(GUI), the GUI will first update the control configuration file and then

reinitialise the control. The control stops all the processes, reads its own

configuration and then restarts the processes. This causes a total traffic outage

every time a new application instance is added and started.

Resolution

The problem was that the control did not reread the queues when a process

was added to it on-the-fly. This is now fixed, and the control also removes the

queue from its internal list when the process is removed. Like other MMS

Center processes, the applications must have the control queue through which

the control can manage them.

The action flag in the control is not the correct way to solve the problem. There

are several processes running with the same binary name. When they are started




6/20


using script, the control cannot know which instance belongs to which script (no

parent pid is used).

1.2 6007 MGW receiver filters out addresses in therecipient list

Priority

B2

Visible to end user

Yes

Created

25.10.2001

Description

When the mail gateway (MGW) receiver receives a message containing an

address list that has both MSISDN and e-mail addresses, it only adds the

MSISDN addresses to the multimedia message (MM) that it sends to the MMS

Center and discards the e-mail addresses. Therefore the recipient does not

receive the full recipient list.

Resolution

Feature change.

1.3 6195 Addresses in the recipient list are filteredout in mail-terminated cases

Priority

B2

Visible to end user

Yes

Created

25.10.2001



7/20


Description

The MMS Center receives a message with several recipient addresses, some of

which are e-mail addresses. The MMS Center / mail gateway (MGW)

transmitter filters out all extra recipient addresses when the message is sent to

an e-mail server. The recipient will see that the message was only sent to this

particular recipient, other addresses are lost.

Resolution

Feature change.

1.4 10872 Reinitialising an application interface with

invalid parameters gives a wrong starting status

Priority

B2

Visible to end user

No

Created

23.05.2002

Description

When an application interface has been modified with an invalid parameter

value (for example, if SSL has been specified as the protocol even though it is

not licensed), the application interface instance is reinitialised. The application

interface instance shuts down after it has detected an invalid configuration, but

the GUI displays the message Application interface modified successfully.

Reinitialisation result of (ASIF) 1 = Aid:trueeven though the application

interface instance has shut down.

Resolution

The process status with multiple instances of running binary corrected. If one

instance of the EAIF process went down, the control still gave status info

PROC_STARTED, since it checked only if a certain process was alive or not.

Now the control maintains a flag to say which processes have been started or

not. If the control cannot restart the process (5 tries in a minute), it gives up and

marks the process as non-started.




8/20


This problem is caused by the lack of the specification when one binary is run

in several purposes. To solve this in a better way, the control must be completed

by the functionality that allows the processes to register themselves in the

control (name + pid).

1.5 11147 Disk space allocation for smart blobs:metadata fills up too early

Priority

B2

Visible to end user

No

Created

06.05.2002

Description

The IDS.2000 version 9.21 uses fixed size metadata vs. user-data area divisions

for smart blobs. If one of those gets full, the disk will be full. (In the version

9.30 the disk allocation for metadata and user-data is more flexible).

Resolution

The metadata and user data areas need not to be re-defined, because in

the future message sizes will increase. According to the Informix

documentation the size is optimal for 64 Kb messages. That is why it is

not reasonable to reduce the userdata area in this phase.

1.6 11315 xscmanmx.cf actions-parameter does notwork correctly

Priority

B2



9/20


Visible to end user

No

Created

22.05.2002

Description

A version of the graphical user interface (GUI) in which the GUI sets the

actions parameter in the [APPLICATIONS] section of xscmanmx.cf

to 55 is needed.Currently the GUI sets the Actionsparameter to 51 (because55 does not work correctly with the new control in the MMS Center 2.0. The

value 55 was used in MC1 and CD1 and worked as expected).

A more detailed description:

When adding application interface instances (yacmanmx and yasmanmxprocesses), the GUI should set the Actionsparameter to 55 so that the

process will be restarted if it goes down.

When a new instance is added, the GUI adds the processes to xscmanmx.cf

and reinitialises the control so that the yacmanmx/yasmanmx processes are

started. The yasmanmx (ASIF) process starts normally, but the yacmanmx

(ACIF) process is not started and the GUI displays the following:

Application instance added successfully.

Start result of (ACIF) test: N/A

Start result of (ASIF) test:true

If the control had attempted to start yacmanmx, then yacmanmx would have

created a trace log file in $SC_LOGPATH at start-up. However, the trace log

file does not exist. Yacmanmx is present in the Component Mgmt window with

status not running.

After this, when the control is reinitialised through the Component Mgmt

window, yacmanmx is started normally, but occasionally there are two instances

of the same yasmanmx processes running. The control does not always stop the

process which is already running when it is reinitialised.

Resolution

Same resolution as in 5477.




10/20


1.7 11565 Delivery report corrupted if the message isrouted through inter-MMS Center, e.g., due to

incorrect configuration

Priority

C3

Visible to end user

No

Created

18.06.2002

Description

A multimedia message (MM) is sent, for example, due to a configuration error

or an error in the exported numbers file, from an originating MMS Center

(MMS Center 1) to an intermediate MMS Center (MMS Center 2) through the

inter-MMS Center application.

The kernel in the intermediate MMS Center notices that the recipient is not

local to the intermediate MMS Center and reroutes it to the inter-MMS Center.

The resent MM stays identical to the MM originating from the MMS Center 1

except that it is assigned a new message ID (message ID 2) that is local to the

MMS Center 2. This time the MM is routed to the correct destination - the

terminating MMS Center (MMS Center 3).

The terminating MMS Center never receives the original message ID. It

generates a delivery report containing a message ID (message ID 2) that is local

to MMS Center 2.The delivery report is sent directly from MMS Center 3 to

MMS Center 1.The originating MMS Center (MMS Center 1) fails to recognise

the message ID 2 and fails to forward the delivery report to the sender.

Resolution

The EAIF was changed to transmit two message-IDs related to m-send-req:

a) a local message ID that is used as described above

b) the message ID received from the originating MMS Center which is

forwarded to the terminating MMS Center in a MM4_forward.REQ

generated by the inter-MMS Center. This original message ID will be used

by the terminating MMS Center when generating an m-delivery-ind if one

is requested.



11/20


The inter-MMS Center was changed to pass the original message ID as the

message ID of the MM4_forward.REQ and to pass the local message ID as the

transaction ID of the MM4_forward.REQ. The transaction ID will be echoed

back in the MM4_forward.RES sent by the terminating MMS Center.

1.8 11625 Event log full does not generate an alarm tothe GUI

Priority

C3

Visible to end user

No

Created

18.06.2002

Description

When eventdbs is full, event logs are written to

$SC_LOGPATH/evlog/CFXXXX.DAT. An alarm should also be raised, but

it is missing.

Resolution

Error handling routine fixed.




12/20


2 Open problem reports

2.1 8208 Database exceptions cause a generic alarm

instead of a database-specific alarm

Priority

C3

Visible to end user

No

Created

25.10.2001

Description

When a database exception occurs, the kernel, WAPGWIF and EAIF processes

send the alarm RUNTIME_ERROR, Exception caught.Fatal error. instead

of an alarm that explicitly tells that a database error has occurred.

Resolution

Will be fixed in MMS Center 3.0.

2.2 10859 One event log is lost if writing into thedatabase fails

Priority

C3



13/20

Open problem reports

Visible to end user

No

Created

06.05.2002

Description

If the database writing permanently fails and the back-up system is taken into

use, the situation where 50 events are lost can be coped with without losing the

CDRs.

Resolution


2.3 11337 Scripts run by crontab in a stand-alonedatabase node, write / send error messagesgenerated

Priority

C3

Visible to end user

No

Created

18.06.2002

Description

When a database node in a cluster is defined with ServiceGuard, crontab entries

are added to both database nodes. Only the active node can execute the scriptsdefined in crontab successfully. The passive node tries to execute the scripts,

but the execution fails because there is no connection to the database. This

generates error logs and error e-mails even though the situation is ok.

The unnecessarily generated error logs and e-mails should be prevented in a

stand-alone database node.

Resolution

Documented in MMS Center 2.1.




14/20



2.4 12677 Xlw_show tool: Pipe error when used withmore

Priority

C3

Visible to end user

No

Created

17.10.2002

Description

When the xlw_show tool is used for checking the content adaptation logs with

the | mor eoption, a 'broken pipe' error is displayed and records cannot beshown.

Resolution

Content adaptation logs can be printed first to the file and then use the | mor eoption. For example:

sc%> $SC_BINPATH/xlw_show -d 1 > ca_log.txt

sc%> $SC_BINPATH/cat ca_log.txt |more


2.5 12784 Content adaptation logs are not showncorrectly

Priority

C3



15/20


Visible to end user

No

Created

17.10.2002

Description

When the xlw_show tool is used for checking the content adaptation logs by

using the -doption, there are some extra characters at the end of originator

address line.

Resolution


2.6 13092 Small memory leak in the kernel

Priority

B2

Visible to end user

No

Created

05.11.2002

Description

During the stability test, the memory used by the kernel grows when different

types of traffic are being tested :

CPU usage: 82%

Memory usage: 58%

Disk usage: 3%

(all of these are averages)

That happens when there is profile based carbon copies and forwardings set in

subscriber DB. The memory leak is about 1-2 MB a day.




16/20


Resolution

Will be fixed with a Change Note in MMS Center 2.1 or in MMS Center 3.0.

2.7 13239 Sometimes the GUI is not able to showalarms

Priority

B2

Visible to end user

No

Created

14.11.2002

Description

Sometimes it happens that the graphical user interface (GUI) cannot show any

alarms although ad1manmx is running, alarms are written and can be found in

$SC_LOGPATH/syslog.

Resolution

To get the alarms to come to GUI again, stop the MMS Center and stop the

JRun default server. Remove all message queues by using the command:

$SC_SCRIPTPATH/ymcRmMMSCQueues 1 10000

Start the JRun default server and then the MMS Center processes.

Instructions added to the Troubleshooting.MMS Centerdocument. Will be fixed

in MMS Center 3.0.

2.8 13408 Loading event logs from tape gives an error

Priority

C3



17/20


Visible to end user

No

Created

27.11.2002

Description

The xdb_upgrade_load_logs_mx.shscript, which is used for loading

the events log from tape to the system, gives an error to the screen that there is a

duplicate event log in the database, but no event log was lost. Event logs were

loaded earlier by the xdb_upgrade_load_tables_mx.shscript.

The problem occurs because the scripts

xdb_upgrade_archive_tables_mx.shand

xdb_upgrade_unload_tables_mx.shboth unload event logs duringthe upgrade in order to shorten the downtime. The

xdb_upgrade_archive_tables_mx.shscript archives all event logs at

the beginning of its execution to a tape device, and the

xdb_upgrade_unload_tables_mx.sh script unloads any additional event logs

created after that to an ASCII file. The scripts overlap slightly, so that a small

number of logs already archived to tape are also archived to an ASCII file. This

may cause some error messages when the

xdb_upgrade_load_logs_mx.shscript, which loads the event logs

stored to tape back to the database, is executed.

Because of a unique primary key constraint, these duplicate rows are not

inserted to the database and database integrity is sustained. No data is lost

either, because the rows that cannot be inserted already have identical duplicates

in the database. Because of this and the one-time nature of the upgrade process,

the problem is mostly aesthetic.

Resolution


2.9 13442 IBM script does not work every time

Priority

C3

Visible to end user

No




18/20


Created

29.11.2002

Description

The index cleaner script sometimes fails with errors written to the log. The

problem is that if a shell function unexpectedly fails partway through, error

checking will not take place and the script continues with uninitialised

variables. Writing a kshinternal file to /tmpsometimes fails, which causes

the shell function to fail. Among other things, this causes errors in the

generation of some SQL statements.

Resolution


2.10 13558 Content adaptation does not support cidreferences for media components in SMIL

Priority

B2

Visible to end user

Yes

Created

10.12.2002

Description

Currently the SMIL plugin assumes that there is only one way to refer to

content, a URL. To fix this, first of all the MessageDecomposer needs to read

the Content-ID field from the component headers and copy it to the attributes of

the media component in the adaptation context, and secondly, the SMIL pluginneeds to recognize the cid references and compare them against the Content-ID

instead of the URL.

Information about the Content-ID type of reference model is available in

RFC2557.

Resolution




19/20


2.11 13599 COT drops lines from host-specific files

PriorityC3

Visible to end user

No

Created

12.12.2002

Description

In a clustered environment, if you save a common file that contains a section

with only commented lines, the section name and all the commented lines above

it are dropped until the next uncommented line above is met.

Resolution

This might happen, for example, with a new xscmanmx.cffile, where all

processes in the [APPLICATIONS]section are commented out by default.

Before saving the file for the first time, add application instances or take out the

comments.

Will be fixed in a Change Note in MMS Center 2.1 or in MMS Center 3.0.




20/20

