Data Collection Guideline for SIU T12A

154 43-LZA 104 102/7 Uen A

Copyright

© Ericsson AB 2011. All rights reserved. No part of this document may bereproduced in any form without the written permission of the copyright owner.

Disclaimer

The contents of this document are subject to revision without notice due tocontinued progress in methodology, design and manufacturing. Ericsson shallhave no liability for any error or damage of any kind resulting from the useof this document.

Trademark List

All trademarks mentioned herein are the property of their respective owners.These are shown in the document Trademark Information.

154 43-LZA 104 102/7 Uen A | 2011-11-17

Contents

Contents

1 General 1

1.1 Product Scope 1

2 Workflow 3

3 Mandatory Data 5

3.1 Data to be Collected 5

4 Data Collected Based on Specific Problem Types 7

4.1 Traffic Related 7

Glossary 9

Reference List 11

154 43-LZA 104 102/7 Uen A | 2011-11-17

Data Collection Guideline for SIU T12A

154 43-LZA 104 102/7 Uen A | 2011-11-17

General

1 General

The purpose of this document is to provide a guideline for collectingtroubleshooting data that is to be enclosed in a Customer Service Request(CSR). A CSR is written when a problem is experienced with the product.

1.1 Product Scope

This guideline is applicable for the following product release:

• T12A application software for Site Integration Unit (SIU 02).

1154 43-LZA 104 102/7 Uen A | 2011-11-17

Data Collection Guideline for SIU T12A

2 154 43-LZA 104 102/7 Uen A | 2011-11-17

Workflow

2 Workflow

The workflow for collecting troubleshooting data is as follows:

1. Collect mandatory data that is needed in connection to any problemsexperienced. Go to Section 3 on page 5.

2. Collect specific data based on the type of problem that is experienced.Go to Section 4 on page 7.

3154 43-LZA 104 102/7 Uen A | 2011-11-17

Data Collection Guideline for SIU T12A

4 154 43-LZA 104 102/7 Uen A | 2011-11-17

Mandatory Data

3 Mandatory Data

The data described in this chapter should always be included in a CSR. Thisrequirement is independent of the CSR problem type.

3.1 Data to be Collected

This section describes how to collect CSR data using the Command LineInterface (CLI). For more information about the commands used, see Reference[2].

1. Print active alarms:

OSmon> getalarmlist

2. Print current time:

OSmon> gettime

3. Print last synchronization date:

OSmon> caldate

4. Print revision of software:

OSmon> rev

5. Enter debug mode and print system information. The commands that areenabled in debug mode can affect traffic when executed.

OSmon> debugDBG:OSmon> sysinfoDBG:OSmon> debug offOSmon>

6. Print uptime for the system:

OSmon> uptime

7. Print the configuration to the log:

OSmon> traceallmoattributeinlog

8. Print the log with complete configuration:

OSmon> syslog read -s systemOSmon> syslog read -s eventOSmon> syslog read -s messages

5154 43-LZA 104 102/7 Uen A | 2011-11-17

Data Collection Guideline for SIU T12A

9. Provide crash dumps if available using the dump command.

Retrieve a list of all dump files saved in the node:

Example:OSmon> dump -l[PRIMARY DUMP ID 0x1]user called : 1error code : 0x33844984extra : 0x00000000[PRIMARY DUMP ID 0x2]user called : 1error code : 0x33844983extra : 0x00000000[PRIMARY DUMP ID 0x3]user called : 0error code : 0x00000048extra : 0x00000000For each dump entry, retrieve the specific dump by adding the ID:

Example:OSmon> dump 0x1[PRIMARY DUMP ID 0x1]

[ERROR HANDLER PARAMETERS]user called : 1error code : 0x33844984extra : 0x00000000......[End Of Dump]

10. Attach syslog and dump printouts to the CSR.

6 154 43-LZA 104 102/7 Uen A | 2011-11-17

Data Collected Based on Specific Problem Types

4 Data Collected Based on Specific ProblemTypes

The data described in this chapter should be included in a CSR, depending onwhat type of problem is experienced.

4.1 Traffic Related

If the problem is traffic related, time synchronized trace captures from allinterfaces related to the fault should be collected and included in the CSR.

Examples of tools to use for log extraction are Wireshark/Ethereal or NethawkM5/Tektronix K15.

Attach a description of the network setup.

7154 43-LZA 104 102/7 Uen A | 2011-11-17

Data Collection Guideline for SIU T12A

8 154 43-LZA 104 102/7 Uen A | 2011-11-17

Glossary

Glossary

See Reference [1].

9154 43-LZA 104 102/7 Uen A | 2011-11-17

Data Collection Guideline for SIU T12A

10 154 43-LZA 104 102/7 Uen A | 2011-11-17

Reference List

Reference List

[1] Glossary

[2] Command Descriptions

11154 43-LZA 104 102/7 Uen A | 2011-11-17