saving error system

MaintenanceSystem

Saving of Error Symptoms

A30828-X1150-M588-5-7620

2 A30828-X1150-M588-5-7620

Saving of Error Symptoms MaintenanceSystem

f Important Notice on Product SafetyElevated voltages are inevitably present at specific points in this electrical equipment. Some of theparts may also have elevated operating temperatures.Non-observance of these conditions and the safety instructions can result in personal injury or in prop-erty damage.Therefore, only trained and qualified personnel may install and maintain the system.The system complies with the standard EN 60950 / IEC 60950. All equipment connected has to complywith the applicable safety standards.

The same text in German:Wichtiger Hinweis zur ProduktsicherheitIn elektrischen Anlagen stehen zwangslufig bestimmte Teile der Gerte unter Spannung. Einige Teileknnen auch eine hohe Betriebstemperatur aufweisen.Eine Nichtbeachtung dieser Situation und der Warnungshinweise kann zu Krperverletzungen undSachschden fhren.Deshalb wird vorausgesetzt, dass nur geschultes und qualifiziertes Personal die Anlagen installiert undwartet.

Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Angeschlossene Gertemssen die zutreffenden Sicherheitsbestimmungen erfllen.

Trademarks:All designations used in this document can be trademarks, the use of which by third parties for theirown purposes could violate the rights of their owners.

Copyright (C) Siemens AG 2001-2004.Issued by the Information and Communication Networks GroupHofmannstrae 51D-81359 Mnchen

Technical modifications possible.Technical specifications and features are binding only insofar asthey are specifically and expressly agreed upon in a written contract.

A30828-X1150-M588-5-7620 3

MaintenanceSystem


This document consists of a total of 52 pages. All pages are issue 5.

Contents1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.1 Entries in the error report . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.2 Overview of fault classes on the CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.3 Overview of the symptom files on the CP . . . . . . . . . . . . . . . . . . . . . . . . . . . 51.4 Overview of fault classes on the SSNC . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61.5 Overview of the Event Logs on the SSNC . . . . . . . . . . . . . . . . . . . . . . . . . . 71.6 Symptoms on the CP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.7 Symptoms on the SSNC - allocation of fault classes . . . . . . . . . . . . . . . . . . 9

2 Saving Error Symptoms SSNC / CP via NetManager. . . . . . . . . . . . . . . . . 102.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Symptom Saving Process. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 112.3 Task description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4 Parameter description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.1 Report Number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122.4.2 Exchange Name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4.3 Begin Date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4.4 Exchange Type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4.5 CP Fault Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4.6 SSNC Fault Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4.7 CP Symptom File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.4.8 SSNC Event Log. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4.9 Additional symptoms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.4.10 Symptoms Server . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142.5 Possible combinations of fault class and selective saving . . . . . . . . . . . . . 152.6 Fault classes and system type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15

3 Error Symptom Saving: Quick Start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.1 Saving the logging data (MLOG) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 163.2 Saving standard symptoms. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2.1 Start the task on the NetM . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2.2 Example: Fault on powernode . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 193.2.3 Working directories on NetM. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.2.4 Contents of working directory (Powernode) . . . . . . . . . . . . . . . . . . . . . . . . 213.2.5 Postprocessing . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 233.3 Saving additional symptoms . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.4 Manual file transfer to the Symptrans PC . . . . . . . . . . . . . . . . . . . . . . . . . . 283.5 Sending symptoms using the Symptrans PC . . . . . . . . . . . . . . . . . . . . . . . 293.5.1 Sending a normal symptom packet. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 303.5.2 Sending a split symptom packet . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31

4 Causes of Script Truncation / Fault Clearance . . . . . . . . . . . . . . . . . . . . . . 344.1 Faulty inputs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.1.1 Fault class not selected . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.1.2 Parameter combination not possible. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 344.1.3 Fault class not possible for this exchange type . . . . . . . . . . . . . . . . . . . . . 35

4 A30828-X1150-M588-5-7620


4.1.4 Begin date was not entered . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 354.1.5 Invalid begin date . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.1.6 Invalid report number . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 364.1.7 Invalid exchange name . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.2 General fault reports . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 374.2.1 The working directory could not be created . . . . . . . . . . . . . . . . . . . . . . . . . 374.2.2 The configuration file cannot be opened . . . . . . . . . . . . . . . . . . . . . . . . . . . 384.2.3 Invalid exchange type . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 394.2.4 The CP command file CG.SA.HMAST could not be copied. . . . . . . . . . . . . 394.2.5 The command could not be sent . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.2.6 The exchange does not respond . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 404.2.7 The command file was stopped manually . . . . . . . . . . . . . . . . . . . . . . . . . . 414.2.8 The command file was stopped by the NetManager . . . . . . . . . . . . . . . . . . 414.2.9 Parallel processing of command files. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.2.10 The CP symptom files are empty . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 424.2.11 Reception of the CP symptom files was unsuccessful. . . . . . . . . . . . . . . . . 434.2.12 The symptoms could not be compressed . . . . . . . . . . . . . . . . . . . . . . . . . . 434.2.13 The FTP client could not be started . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.2.14 The FTP server is not available . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 444.2.15 Login to the FTP server is not possible . . . . . . . . . . . . . . . . . . . . . . . . . . . . 454.2.16 The FTP destination directory does not exist . . . . . . . . . . . . . . . . . . . . . . . 454.2.17 FTP file transfer unsuccessful . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46

5 IndsysNT Symptom Saving for NetManager . . . . . . . . . . . . . . . . . . . . . . . . 475.1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.2 Installation of IndsysNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 475.2.1 Local installation. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 485.2.2 Central installation . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.3 Start IndsysNT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 495.3.1 Local start. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 505.3.2 Central start . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.4 IndsysNT restrictions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 515.5 IndsysNT abbreviations and variables . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

A30828-X1150-M588-5-7620 5

MaintenanceSystem


1 IntroductionThis manual describes the saving of symptoms after an error in the network element. Assoon as an error is detected, and if the error has not yet been registered and reported,an error report must be created. The efficiency of error report processing depends onhow well the malfunction is described and what symptoms are supplied.The strategy of the error symptom procedure is to be able to provide the error symptomsrequired for analysis immediately, together with the error report. Standard error symp-toms must be supplied with every error report.If possible, error symptom files should be generated, delivered and forwarded electron-ically (by e-mail) from the customer to the system manufacturer. The central address forerror symptoms is SIEMENS AG Munich, where the error symptoms are collected andpassed on.

1.1 Entries in the error reportAn error report should be prepared at the same time as the error symptoms are saved.Each error report should contain the following standard entries: description of the malfunction operator actions any problems in the network environment basic diagram of the network environment any other actions (if they can be traced) where the logging data is saved (e.g. MLOG)

1.2 Overview of fault classes on the CPError symptoms should be saved after any system event that results in an error report: CP problems / CP recovery Problems in the peripherals Call processing / charging / traffic OSI application problems CCNC problems Miscellaneous (incl. BOP)

1.3 Overview of the symptom files on the CP AD.RESTART

The file contains a collection of plausibility errors. AD.ZZK

The file contains a collection of messages from the #7 signaling section. DC.V0n

The file contains a collection of symptoms after an interrupted ISTART. DC.B0n

The file contains a collection of error symptoms occurring during basic operation(n = 0, 1).

HF.ARCHIVEThe file contains a collection of all system messages, operator inputs and associat-ed outputs.

6 A30828-X1150-M588-5-7620


HF.MCP.HWERRORThe file contains a collection of all sporadic CP hardware error messages.

HF.Q3ASThe file contains messages relating to errors that can occur during processing of Q3commands.

HF.SMMLThe file contains messages relating to errors that can occur during processing ofSMML jobs.

HF.TRANSFILEThe file contains transfer jobs (beginning, interruption, continuation and terminationof file transfers).

HF.VSD.STATEThe file contains statistical data of the VSD database.

PT.AMTINDThe file contains general system data (capacity stage, patch status... ). This tempo-rary file is created after the start of the command file CG.SA.HMAST.

PT.X25INDThe file contains information on the X.25 database. This temporary file is created af-ter the start of the command file CG.SA.HMAST.

SG.BX25The file contains a collection of SW error symptoms from the IOP-LAU section. Thefile is generated as soon as an error is detected in the IOP:LAU section.

SG.SESYMPThe file contains a collection of SW error symptoms from the central section.

SG.OPERThe file contains a collection of safeguarding messages from the operating phase(without CCS7 safeguarding).

TM.MNT.PCMThe file contains a collection of system messages specifically for PCM links.

TM.MNT.PORTThe file contains a collection of system messages from ports from the Maintenancesection, e.g. killer trunks, threshold values etc.

1.4 Overview of fault classes on the SSNCError symptoms should be saved after any system event that results in an error report: SSNC #7 problems SSNC administration / security SSNC hardware problems SSNC software problems SSNC recovery

A30828-X1150-M588-5-7620 7

MaintenanceSystem


1.5 Overview of the Event Logs on the SSNCUnlike the symptoms on the CP, the SSNC error symptoms are not simple files. TheSSNC symptoms are referred to as Event Log instances.

System-internal event logsThe system-internal event logs are created automatically when the system is started forthe first time. If the system-internal event logs have been deleted, they can only be cre-ated again using Q3 scripts. sgSesympe

Symptoms for software errors: SWINC, SWERR sgSwfpe

Software Fault Processing: symptoms from local recoveries of SSNC units SgSupe

Safeguarding messages during recovery sgAudite

Audit error messages sgOpere

Safeguarding messages between SSNC units sgEnbe

Error Notebook data DCE.Vxx

Symptoms of interrupted recoveries of the system (Loadrec2 / Loadrec3)DDEV00 - DDEV07 - are created by MP:SADDEV10 - DDEV17 - are created by the MP:Ds

Administrable event logsThe administrable event logs are a part of the OAM database. AIALARM

Hardware alarms, software alarms, status change of units, startup messages DET_AIALRM

like AI_ALARM, without status change/startup messages SAL_AIALARM

Security alarms AI_CCS7

No. 7 alarms AI_MAINT

Maintenance, clock alarms, diagnosis results from the units, HW fault processing AI_REC

Recovery progress reports, end reports AI_ACTION

Database modifications AI_UPGR

Upgrade messages, APS backup reports AI_ARCHIVE

Common messages SAT_SECAUDIT

Security messages Q3ETR

Data of the Q3 error tracer

8 A30828-X1150-M588-5-7620


1.6 Symptoms on the CP

CP fault class Symptom files NetM fileAZSTOExx

Switch settingsSET CFOPT: ON=xfor CG.SA.HMAST

CP problems / CP re-covery

AD.RESTART .RES 1,3,4,5,10,12DC.V0n,DC.B0n .DCx/BCxHF.ARCHIVE .HFAHF.MCP.HWERROR .HFHPT.AMTIND .AIN

SG.SESYMP .SGSProblems in the periph-erals

HF.ARCHIVE .HFA 4,10,13,15PT.AMTIND .AIN

SG.OPER .SGOTM.MNT.PCM/PORT .PCM/.PRT

Call processing / charg-ing / traffic

HF.ARCHIVE .HFA 4,9,10HF.VSD.STAT .VSDPT.AMTIND .AIN

OSI application prob-lems

HF.Q3AS .XQ3 6,7,8,10,11,14HF.SMML .XSMHF.TRANSFILE .XTRPT.AMTIND .AIN

PT.X25IND .XIN

SG.BX25 .X25CCNC problems AD.ZZK .ZZK 2,4,10,13

HF.ARCHIVE .HFAPT.AMTIND .AIN

SG.OPER .SGOMiscellaneous (incl.BOP)

AD.RESTART .RES 1,3,4,5,9,10,12,13DC.V0n, DC.B0n .DCx/BCxHF.ARCHIVE .HFAHF.MCP.HWERROR .HFHHF.VSD.STAT .VSDPT.AMTIND .AIN

SG.SESYMP .SGSSG.OPER .SGO

Tab. 1.1 CP symptoms

A30828-X1150-M588-5-7620 9

MaintenanceSystem


1.7 Symptoms on the SSNC - allocation of fault classes

Log instance Nr.7 error HWfault

Security andAdministration

SW er-ror

SSNC Re-covery

sgSesympe X XsgOpere X XsgSupe X X XsgSwfpe X XsgEnbe X XsgAudite XDCE.Vxx X X X X XAI_REC X XAIALARM X X X X X

Q3-ETR XAI_ACTION X X X XAI_UPGR X XAI_ARCHIVE X XSAT_SECAUDIT XSAL_AIALARM XDET_AIALARM X X X X X

AI_CCS7 XAI_MAINT X X X X

Tab. 1.2 SSNC fault class log instances

10 A30828-X1150-M588-5-7620


2 Saving Error Symptoms SSNC / CP via Net-Manager

2.1 IntroductionSaving error symptoms via NetManager was implemented with the task "Save ErrorSymptoms". Using this task, error symptoms can be saved as follows: Saving of standard symptoms for EWSD Innovation and EWSD Classic Selective saving of symptoms from files (CP) and Event Logs (SSNC)Features of error symptom saving via NetManager: Covers the products EWSD Innovation and EWSD Classic Automatic compression of error symptom files Automatic file transfer to any FTP server

A30828-X1150-M588-5-7620 11

MaintenanceSystem


2.2 Symptom Saving Process

Fig. 2.1 Symptom saving process

1

3

2

4

5

6

7

8

Start of exchange-specific tasks

Command files on the CP are started and data stored on the CP-MDD

SSNC Event Logs are read out

Event Logs of the SSNC are written into a file on the NetM

CP symptom files are copied to the NetM by file transfer

Attach additional symptoms (optional)

All error symptom data on the NetM for CP and SSNC is compressed

Optional file transfer to Symptrans PC or another FTP server

12 A30828-X1150-M588-5-7620


2.3 Task description

Fig. 2.2 Task description

2.4 Parameter description

2.4.1 Report NumberEnter the AZSTOE No. according to the following conventions:8-digit numerical quantity YMMIIIxx

Do not use blanks!

1 2

9

7

5

3 4

6

8

10

Enter the begin date for symptom saving

Enter the exchange name

Select CP fault class

Select exchange type

Select SSNC fault class

Select CP symptom file (only for selective savingSelect SSNC Event Log (only for selective saving)Attach additional symptoms (optional)Enter the parameters for automatic file transfer (optional)

Enter the report (AZSTOE) No1

3

2

4

5

6

7

8

9

10

Y end figure of yearMM monthIII serial numberxx version number

A30828-X1150-M588-5-7620 13

MaintenanceSystem


2.4.2 Exchange NameEnter the name of the exchange with 11 characters.Example:9121.N2W..DDo not use blanks!

2.4.3 Begin DateEnter the begin date:6-digit number YYMMDD

Do not use blanks!

2.4.4 Exchange TypeSelect the exchange type: Classic Powernode STP

2.4.5 CP Fault ClassSelect the CP fault class: CP problems / CP recovery Problems in the peripherals Call processing / charging / traffic OSI application problems CCNC problems Miscellaneous (incl. BOP)

2.4.6 SSNC Fault ClassSelect the SSNC fault class: SSNC #7 problems SSNC administration / security SSNC hardware problems SSNC software problems SSNC recovery

2.4.7 CP Symptom FileSelect the CP file for selective symptom saving. AD.RESTART AD.ZZK DC.Vxx/DC.Bxx HF.ARCHIVE

YY yearMM monthDD day

14 A30828-X1150-M588-5-7620


HF.MCP.HWERROR HF.Q3AS HF.SMML HF.TRANSFILE HF.VSD.DAT PT.AMTIND PT.X25IND SG.BX25 SG.SESYMP SG.OPER TM.MNT.PORT/.PCM

2.4.8 SSNC Event LogSelect the SSNC Event Log instance for selective symptom saving. SgSesympe SgSwfpe SgSupe SgAudite SgOpere

2.4.9 Additional symptomsIf other symptoms are to be added to the standard symptoms,such as: tracer output screen shotsselect "yes". The TASK will be stopped so that further files can be copied into the work-ing directory.

2.4.10 Symptoms ServerDefault values:HOST USERID PASSWORD PATHInput parameter for automatically file transfer. If there was no changes in the standardvalues, no file transfer will carried out.

Example:139.21.206.211 anonymous guest symptomsSpecification of the path is optional.

HOST Enter the IP address or the host nameUSERID Enter the user namePASSWORD Enter the passwordPATH Enter the directory on the FTP server; if no value is entered, the de-

fault FTP directory will be used

A30828-X1150-M588-5-7620 15

MaintenanceSystem


2.5 Possible combinations of fault class and selective savingStandard symptom saving for the CP and simultaneous saving of a CP file is not possi-ble. It is also not possible to save SSNC standard symptoms and an individual eventlog of the SSNC at the same time.Possible combinations: CP fault class and SSNC fault class CP fault class und SSNC event log CP file and SSNC fault class CP file and SSNC event log

2.6 Fault classes and system type

Fault Classes Classic Powernode STP

CP problems / CP recovery X XProblems in the peripherals X XCall processing / charging / traffic X XOSI Application problems X XCCNC problems XMiscellaneous (incl. BOP) X XSSNC #7 problems X XSSNC administration / security X XSSNC hardware problems X XSSNC software problems X XSSNC recovery problems X X

Tab. 2.1 Fault classes and system type

16 A30828-X1150-M588-5-7620


3 Error Symptom Saving: Quick Start

3.1 Saving the logging data (MLOG)In order to be able to save all the tasks performed on a system, you must log in as a userin the user group ENM Administrators.

Fig. 3.1 User group ENM Administrators1. Starting the LOG VIEWER

Fig. 3.2 Start Log Viewer2. Confirm the message with

A30828-X1150-M588-5-7620 17

MaintenanceSystem


3. Select Log>Select User, select and confirm with

Fig. 3.3 Select user4. Call up filter with View > Set filter5. Set the time period and the destination system

Confirm with and click

Fig. 3.4 Set filter

18 A30828-X1150-M588-5-7620


6. Select the tasks, call up the context-sensitive menu with the right mouse but-tonSelect

Fig. 3.5 Select task7. Save the data in the TEMP directory of the file server

TEMP directory of the file server:\\PC name FileServer\ENMBase(NetMBase)\temp

Confirm with

Fig. 3.6 Save the dataThe MLOG is sent as described in section 3.3 "Saving additional symptoms"

A30828-X1150-M588-5-7620 19

MaintenanceSystem


3.2 Saving standard symptoms

3.2.1 Start the task on the NetM

Fig. 3.7 Start task

3.2.2 Example: Fault on powernode CP problems / CP recovery SSNC software problemsEnter: Report Number Exchange Name Begin Date Exchange Type SSNC fault class Symptoms Server

20 A30828-X1150-M588-5-7620


Fig. 3.8 Enter parametersThe symptoms are to be sent automatically to an FTP server.

3.2.3 Working directories on NetMThe following temporary directory of the NetM is used:

NetM 3.2:\\"Name FileServer"\ENMBase\temp\symptoms\"Exchange Name"\"Report Number"\Example: \\ENM_FS\ENMBase\temp\symptoms\T9002\01010101\

NetM V4N:\\"Name FileServer"\NetMBase\temp\symptoms\"Exchange Name"\"Report Number"\Example: \\ENM_FS\NetMBase\temp\symptoms\STP1\01010101\

HOST: IP address (e.g.139.21.206.211)USERID: anonymousPASSWORD: guestPATH: optional

A30828-X1150-M588-5-7620 21

MaintenanceSystem


3.2.4 Contents of working directory (Powernode)

Fig. 3.9 Contents of working directory

FIles in the working directory:

CP symptoms01010100.ain PT.AMTIND01010100.hfa HF.ARCHIVE01010100.hfh HF.MCP.HWERROR01010100.res AD.RESTART01010100.sgs SG.SESYMP

SSNC symptoms01010100.AI_ARCHIVE AI_ARCHIVE01010100.AI_MAINT AI_MAINT01010100.AIALARM AIALARM01010100.DET_AIALARM DET_AIALARM01010100.sgSupe sgSupe01010100.ssnc_exchdata General SSNC exchange data

Other files/directoriesSystem_Log Directory

All actions carried out on the system are recorded inthis directory.

01010100_System_Log Packed files of the System_Log directory

22 A30828-X1150-M588-5-7620


*.ind Packed files for the Symptrans PC*.zip ZIP file containing all error symptom filesSplitted files Directory

If the packed symptom file exceeds 4096 KB in size,it is automatically split up. This directory contains theindividual split files of the symptom packet.

Contents of the directory "Splitted_Files":

#SPLIT#_*_xx_xx - split files of the symptom packet

Other files/directories

A30828-X1150-M588-5-7620 23

MaintenanceSystem


3.2.5 Postprocessing1. Check the CP error symptoms

DISP FILE:FILE=AZSTOExx.;

The CP files that are indicated must be present in the working directory. If all the CPfiles have been copied, delete the files on the CP.

DEL FILEFILE=AZSTOExx.;

If the files have not all been copied, start symptom saving again.

2. Check the error symptom data of the SSNCThe files SSNC_in_XXXXX.txt in the directory System_Log contain all the com-mands that were executed on the SSNC.Example:File SSNC_in_basic.txt:STAT MP;DISP MPSTAT LIC

The outputs of the commands must be contained in the file AZS-TOExx.ssnc_exchdata.File AZSTOExx.ssnc_exchdata:T002/DBPCBK1V_1531_P 2001-07-12 09:21:392-55299 ENM_CS/ct2

STATMP; STARTED

Make a random check of the command outputs.

command repetition EXECD

USED SPACE : 208 PAGES FOR 1 FILES

FILE GEN SIZE VSN000 VSN001 CLASS TYPE-----------------+--------+-------+-------------+-------------+----+----

AZSTOExx 208 X SYNCHRONIZING SAM

command repetition ACCEPTED

FILE-----------------

AZSTOExx.HFAcommand repetition EXECD

MP Admin. state Operational state Availability status Standby status Alarm status1 Unlocked Enabled providing service Critical2 Unlocked Enabled providing service Cleared

24 A30828-X1150-M588-5-7620


3. Delete the SSNC Eventlog entriesAfter successful saving of the SSNC Eventlogs, delete the entries in the eventlogsagain. This ensures that in the event of a new error only the current data are stored.Example:CAN EVREC:Event log=String:"sg.Sesympe" STARTED

CAN EVREC: EXECDENDJOB

4. Check file transfer Open a DOS window

START -> Programs -> Command Prompt Start the FTP session

Make the inputs in the DOS window- FTP IP address (e.g. 139.21.206.211)- Userid (anonymous) - Password (guest) - cd indizien (change directory on the Symptrans-PC)>

Check the file *.ind on the Symptrans PCMake the inputs in the DOS window !- ls - quit (quit the session)

Fig. 3.10 Check file transferFile transfer was successful if the output of the command ls indicates the file *.indfrom the working directory. If the file is not indicated, file transfer was not successful.In this case, carry out manual file transfer as described in section 3.4 "Manual filetransfer to the Symptrans PC".

Event Log Admin. state"sg.Sesympe" Event Log records deleted

A30828-X1150-M588-5-7620 25

MaintenanceSystem


5. Delete the working directory on the file serverAfter successful data transfer to the Symptrans PC, the temporary working directorycan be deleted. Use the Windows Explorer to do this.Temporary working directory:NetM 3.2:\\"Name FileServer"\ENMBase\temp\symptoms\"Exchange Name"\"Report Num-ber"\Example: \\ENM_FS\ENMBase\temp\symptoms\T9002\01010101\NetM V4N:\\"Name FileServer"\NetMBase\temp\symptoms\"ExchangeName"\"Report Number"\Example: \\ENM_FS\NetMBase\temp\symptoms\STP1\01010101\

3.3 Saving additional symptomsThese symptoms must be present in the form of files on the file server. In the followingexample a screenshot of a NetManager error and an MLOG have been saved..

Fig. 3.11 Additional symptoms

26 A30828-X1150-M588-5-7620


1. Enter the task parametersEnter: Report Number Exchange Name Begin Date Exchange Type Additional symptoms: yes Symptoms ServerThe symptoms are to be sent automatically to an FTP server.

Fig. 3.12 Enter parameters2. Start the task

The following working directory is created:\\"PC name FileServer"\ENMBase(NetMBase)\temp\symptoms\" ExchangeName"\"Report Number "\Example:\\ENM_FS\ENMBase(NetMBase)\temp\symptoms\testexchange_TA9005\01010102\

3. Copy the symptoms into the working directoryThe task is stopped, do not confirm with !

HOST: IP address (e.g. 139.21.206.211)USERID: anonymousPASSWORD: guestPATH: optional

A30828-X1150-M588-5-7620 27

MaintenanceSystem


Fig. 3.13 Additional symptomsAfter the symptoms have been copied, the working directory has the following con-tents:

Fig. 3.14 Working directoryConfirm the information block with . The symptoms will now be compressedand forwarded.

28 A30828-X1150-M588-5-7620


3.4 Manual file transfer to the Symptrans PCNormally the error symptoms are sent automatically to the Symptrans PC (FTP server).If the error symptoms are to be sent manually, carry out FTP file transfer to theSymptrans PC.

1. Open a DOS window Start-> Programs-> Command Prompt

2. Start the FTP sessionMake the entries in the DOS window! FTP IP address of the Symptrans PC (e.g. 139.21.206.211) anonymous (Userid) guest (Password) cd indizien (change directory on the Symptrans-PC)

3. Send the file *.indMake the entries in the DOS window! bin (binary mode) put \\"PCnameFileServer"\ENMBase(NetMBase)\temp\symptoms\" Ex-

change Name"\"Report Number "\*.ind quit (quit session)

Fig. 3.15 FTP file transferEND

A30828-X1150-M588-5-7620 29

MaintenanceSystem


3.5 Sending symptoms using the Symptrans PCThe following instructions are only a summary of the online documentation for theSymptrans software and therefore do not claim to be complete.Following the introduction of NetManager V4N, symptom packages larger than 4096 KBare automatically split. Therefore, before a symptom packet can be sent, it must bechecked to see if it is split.All inward symptom packets are saved in the "Folder for inward archives" of theSymptrans software. This folder is specified in the Symptrans software settings. TheSymptrans software is located on the symptom PCs.Starting the Symptrans software:START -> Programs -> SympTrans -> SympTransConfiguration settings for the Symptrans software:Options -> Configurations

Fig. 3.16 Folder for inward symptom packetsIn the example shown:W:\SympTrans\Inboxis the folder for inward archives.This folder can be opened with the "Windows NT Explorer" so as to check its contents.If the folder contains only an *.ind file, as shown below, it is a normal symptom packet.In this case, continue with 3.5.1 "Sending a normal symptom packet".

Fig. 3.17 Normal symptom packet

30 A30828-X1150-M588-5-7620


However, if the folder contains an *.ind file and several other files that start with#SPLIT#*, as shown below, this is a split symptom packet.

Fig. 3.18 Split symptom packetIn this case, continue with 3.5.2 "Sending a split symptom packet".

3.5.1 Sending a normal symptom packet1. Start the Symptrans software

START -> Programs -> SympTrans -> SympTrans2. Open the symptom packet

File -> Open Archive -> "Select Archive" -> Open

Fig. 3.19 Opening an archive3. Extract the contents of the symptom packet

File -> Extract contentsThe data contained in the symptom packet are automatically unpacked into the"Folder for automatically extracted archives".In the example shown:W:\SympTrans\Rootis the folder for automatically extracted archives. This folder contains sub-folderswhose names correspond to the exchange in question.

Fig. 3.20 Contents of an unpacked symptom packet4. Convert the symptom packet

The symptom packet must be zipped before it is sent.File -> Convert to ZIPThis may take several seconds, depending on the size of the symptom packet. Theprocedure is complete once the "Send" button can be selected.

A30828-X1150-M588-5-7620 31

MaintenanceSystem


5. Send the symptom packetEnter a string of up to 6 characters in the "Fault Report Number" field.

Fig. 3.21 Entering the fault report numberThen press the "Send" button. This procedure may take several seconds; the send-ing of the symptom packet is acknowledged with the following message:

Fig. 3.22 Successful sending of a symptom packet

3.5.2 Sending a split symptom packetIf the symptom packet is split, the folder for inward symptom packets contains the fol-lowing files: *.ind - symptom packet #SPLIT#_*_01_xx , #SPLIT#_*_02_xx ....The *.ind file is only used for automatically unpacking the contents of the symptom pack-et into the "Folder for automatically extracted archives". Due to its size, this archivecan no longer be sent by e-mail.All files whose name begins with #SPLIT# are the split parts of the symptom packet. Thelast part of the name indicates which part it is and the total number of sub-packets.Example:#SPLIT#_*_01_03This file is the first of a total of 3 sub-packets.

Fig. 3.23 Split symptom packet1. Start the symptom software

START -> Programs -> SympTrans -> SympTrans2. Open the symptom packet

File -> Open Archive -> "Select Archive" -> Open

32 A30828-X1150-M588-5-7620


Fig. 3.24 Opening an archive3. Extract the contents of the symptom packet

File -> Extract contentsThe data contained in the symptom packet are automatically unpacked into the"Folder for automatically extracted archives".In the example shown:W:\SympTrans\Rootis the folder for automatically unpacked archives. This folder contains sub-folderswhose names correspond to the exchange in question.

Fig. 3.25 Contents of an unpacked symptom packet4. Send the sub-packets

A new archive must be created for each #SPLIT# file.Create a new archive:File -> NewInsert a #SPLIT# file:Actions -> AddThis opens the folder for inward archives; the first sub-packet can now be selected."Select Archive" -> Open

A30828-X1150-M588-5-7620 33

MaintenanceSystem


Fig. 3.26 Contents of an unpacked symptom packetEnter a string of up to 6 characters in the "Fault Report Number" field.

Fig. 3.27 Entering the fault report numberThen press the "Send" button. This procedure may take several seconds; the send-ing of the symptom packet is acknowledged with the following message:

Fig. 3.28 Successful sending of a symptom packetContinue sending the individual sub-packets until they have all been sent. Only one#SPLIT# file can be added to an archive at a time.Then all #SPLIT# files should be removed from the folder for inward archives.

34 A30828-X1150-M588-5-7620


4 Causes of Script Truncation / Fault Clearance

4.1 Faulty inputs

4.1.1 Fault class not selected

Fig. 4.1 Fault class not selectedAn attempt was made to carry out symptom saving without selecting a fault class or anerror symptoms file, or without selecting "Additional symptoms -yes". Select a fault class/ error symptoms file and start the task again

4.1.2 Parameter combination not possible

Fig. 4.2 Parameter combination not possibleSimultaneous standard symptom saving and selective symptom saving for the samepart of the exchange is not possible. For example, it is not possible to simultaneouslyselect a CP fault class and a CP symptoms file. On the other hand, for example, thecombination of a CP fault class and an SSNC Event Log is possible. Change the param-eter combination and start the task again.

A30828-X1150-M588-5-7620 35

MaintenanceSystem


4.1.3 Fault class not possible for this exchange type

Fig. 4.3 Fault class not possibleThe selected fault class is not possible in combination with the selected exchange type.For example, CCNC symptom saving cannot be carried out for a Powernode. The faultclasses that are possible for the different exchange types are described in section2.6 "Fault classes and system type".

4.1.4 Begin date was not entered

Fig. 4.4 Begin date was not enteredWhen saving SSNC symptoms you must enter the begin date, because the symptomfiles can be larger than 100 MBytes. Enter a begin date and start the task again.

36 A30828-X1150-M588-5-7620


4.1.5 Invalid begin date

Fig. 4.5 Invalid begin dateThe date that was entered is invalid or is in the future. Enter a valid date and start thetask again

4.1.6 Invalid report number

Fig. 4.6 Invalid report numberThe report number that is entered must not be longer than eight characters and mustnot contain any blanks. Enter a valid report number and start the task again.

A30828-X1150-M588-5-7620 37

MaintenanceSystem


4.1.7 Invalid exchange name

Fig. 4.7 Invalid exchange nameThe exchange name that is entered must not contain any blanks. Enter a valid exchangename and start the task again.

4.2 General fault reports

4.2.1 The working directory could not be created

Fig. 4.8 The working directory could not be createdThe directory already exists and is not empty. Check the contents of the directory. Thendelete the directory and start the task again

38 A30828-X1150-M588-5-7620


4.2.2 The configuration file cannot be opened

Fig. 4.9 The configuration file cannot be openedThe file Symptom32cfg.ini is located on the file server. This file contains all the com-mands/command files that are used in the symptoms processDo not modify this file, because otherwise symptom saving will not be possible.Storage location on the file server:NetM3.2:\\"Processor Name FileServer"\ENMBase\temp\symptoms\" Exchange Name"\"ReportNumber "\Example: \\ENM_FS\ENMBase\bin\Symptom32cfg.iniNetM V4N:\\"Processor Name FileServer"\NetMBase\temp\symptoms\" Exchange Name"\"ReportNumber "\Example: \\ENM4_FS\NetMBase\ bin\Symptom32cfg.iniContents of the file Symptom32cfg.ini:/************************************************************ **

** DESCRIPTION: CONFIG FILE FOR SYMPTOM32.EXE **** VERSION : 1.0 **** NETMOS : NETM3.2 **** HINTS : DO NOT CHANGE THIS FILE **** **

** AUTHOR : BAUMANN, THOMAS ICN WN S CS 1 **** SUBSTITUTE : **** **

** HISTORY : 04.07.2002 FINAL VERSION NETM3.2 **** **

**********************************************************/

[TIMEOUT]12[END]

[CPERROR]CRFILE:FILE=CPHIND.[reportnr],TYPE=DOUBLE,SIZE=1;...

A30828-X1150-M588-5-7620 39

MaintenanceSystem


The file was deleted, or entries in the file were edited manually. Cancel any modifica-tions that were made in the file. Check the patch status of the NetManager and updateit if necessary.

4.2.3 Invalid exchange type

Fig. 4.10 Invalid exchange typeAn attempt was made to carry out Q3 tasks on a Classic exchange or MML tasks on anSTP. Check the exchange type and start the task again.

4.2.4 The CP command file CG.SA.HMAST could not be copied

Fig. 4.11 The CP command file CG.SA.HMAST could not be copiedFor CP symptom saving the current CP command file is copied onto the CP before eachstart. The current command file is contained in the configuration file. The fileCG.SA.HMAST is located in the System_Log directory of the working directory. De-pending on the type of exchange, file transfer is repeated if it is unsuccessful.

Classic 1st attempt FTNEA 2nd attempt FTAM Fault reportPowernode 1st attempt FTP 2nd attempt FTNEA 3rd attempt FTAM Fault report

40 A30828-X1150-M588-5-7620


The command file CG.SA.HMAST has already been started, or the failure is due to filetransfer problems on the NetManager. Wait until the command file has been executed,or check the NetManager administration. For important information about the cause, re-fer to the System_Log directory in the files SENDFILE1_out.txt, SENDFILE2_out.txt andSENDFILE3_out.txt.

4.2.5 The command could not be sent

Fig. 4.12 The command could not be sentThe SSNC or CP is unavailable because of network problems. Faulty NetManager ad-ministration can also be the reason for non-availability. Clear any network problems orcheck the NetManager administration. Then start the task again.

4.2.6 The exchange does not respond

Fig. 4.13 The exchange does not respondA command (CP/SSNC) was sent to the exchange and there has been no response for120 minutes. This is due to a recovery on the CP/SSNC. Start the task again.

A30828-X1150-M588-5-7620 41

MaintenanceSystem


4.2.7 The command file was stopped manually

Fig. 4.14 The command file was stopped manuallyThe operator stopped the command file manually. Start the task again.

4.2.8 The command file was stopped by the NetManager

Fig. 4.15 The command file was stopped by the NetManagerThe command file was stopped by the NetManager. Start the task again.

42 A30828-X1150-M588-5-7620


4.2.9 Parallel processing of command files

Fig. 4.16 Parallel processing of command filesOnly one command file can be processed within a CP session. A multiple start is notpossible. Alternatively, the maximum number of command files that can be started onthe CP has been reached. Wait until the command file that was started has been exe-cuted. Start the task again.

4.2.10 The CP symptom files are empty

Fig. 4.17 The CP symptom files are emptyThe requested symptom files are empty. Select a different fault class/symptom file. Startthe task again.

A30828-X1150-M588-5-7620 43

MaintenanceSystem


4.2.11 Reception of the CP symptom files was unsuccessful

Fig. 4.18 Reception of the CP symptom files was not successfulSymptom files were created successfully on the CP. The subsequent file transfer to theNetManager was not successful. Termination is due to recovery on the CP or file trans-fer problems on the NetManager. Depending on the exchange type, file transfer is re-peated if it is unsuccessful:

For important information on the cause of termination, refer to the System_Log directoryin files: RECEIVE1_out.txt, RECEIVE2_out.txt and RECEIVE 3_out.txt .

4.2.12 The symptoms could not be compressed

Fig. 4.19 The symptoms could not be compressedThe working directory is empty, no files could be compressed. If, for example, only ad-ditional symptoms are to be saved, and if no additional symptoms were copied into theworking directory, this fault report appears.

Classic 1st attempt FTNEA 2nd attempt FTAM Fault reportPowernode 1st attempt FTP 2nd attempt FTNEA 3rd attempt FTAM Fault report

44 A30828-X1150-M588-5-7620


4.2.13 The FTP client could not be started

Fig. 4.20 The FTP client could not be startedInternal problems of the Windows operating system are preventing the start of the FTPclient. It may be necessary to restart Windows.

4.2.14 The FTP server is not available

Fig. 4.21 The FTP server is not availableThe address specified for the FTP server is invalid or unavailable. Clear any networkproblems or specify a valid address. Send the symptoms manually as described in3.4 "Manual file transfer to the Symptrans PC"

A30828-X1150-M588-5-7620 45

MaintenanceSystem


4.2.15 Login to the FTP server is not possible

Fig. 4.22 Login to the FTP server is not possibleCheck the user ID and the user password. Send the symptoms manually as describedin section 3.4 "Manual file transfer to the Symptrans PC".

4.2.16 The FTP destination directory does not exist

Fig. 4.23 The FTP destination directory does not existThe FTP destination directory does not exist, the files were copied to the standard direc-tory of the FTP server. Send the symptoms manually as described in section3.4 "Manual file transfer to the Symptrans PC".

46 A30828-X1150-M588-5-7620


4.2.17 FTP file transfer unsuccessful

Fig. 4.24 FTP file transfer unsuccessfulFile transfer to the FTP server was unsuccessful. Send the symptoms manually as de-scribed in section 3.4 "Manual file transfer to the Symptrans PC".

A30828-X1150-M588-5-7620 47

MaintenanceSystem


5 IndsysNT Symptom Saving for NetManager

5.1 IntroductionIndsysNT is used for collecting standard symptoms on NetManager 3.2 or V4N and sup-ports both single and Client/Server NetM.The collected data is used exclusively for analyzing the underlying malfunction. The col-lected data is not passed on without prior consent.The following steps are carried out when IndsysNT is started: Check user information (first name, family name, organization / customer, telephone

number, e-mail, a short description of the problem (max. 255 characters) and Oraclepassword when starting on an FS)

Automatic collection of the standard symptoms (local or central from the FS of se-lected PCs in the NetM OS)

Compression and storage of the symptoms as a *.ZIP file in the directory %System-Drive%\#Symptoms#

Function for collecting additional symptoms:Because not all symptoms (e.g. X.25 database of the CP or the Netconfig file of the MP)can be collected automatically by IndsysNT, IndsysNT can be stopped before compres-sion is started. The additional data can then be copied manually into a prepared subdi-rectory (%SystemDrive%\#Symptoms#\\AddSymptoms). After you haverestarted IndsysNT and selected option "c", the symptoms are compressed.Entry of the user information is not optional, and the information is used for identifyingthe symptoms in the event of queries. Therefore, please always enter the name of aperson who can provide information about the problem if necessary. The information isstored in the file UserInfo.txt. The Oracle password (password for the Oracle user IN-TERNAL) is only used for reading out the NetM database. It is not stored in the symp-toms files.

5.2 Installation of IndsysNTIndsysNT can be installed in two ways: Locally on the PC (e.g. SingleMachine, FS) Centrally from the FS in the whole NetM OS

48 A30828-X1150-M588-5-7620


5.2.1 Local installationInstallation takes about 15 seconds1. Log on as domain administrator2. Start Setup_IndsysNTvX.x.exe

Fig. 5.1 : Installation of IndsysNT - Start3. Click Next.4. Leave the preset destination directory!!! (C:\#IndsysNT#)

Fig. 5.2 Installation IndsysNT - destination directory

A30828-X1150-M588-5-7620 49

MaintenanceSystem


5. Click Next (or, where applicable, "Yes to All" )IndsysNT is copied into the directory C:\#IndsysNT#\.

5.2.2 Central installationInstallation takes about 10 - 20 seconds per PC.1. Install IndsysNT on the FS as described in section 5.2.1 "Local installation"2. Log on as domain administrator at the FS3. Start IndsysNT by clicking on "Start/Programs/IndsysNT/IndsysNT4. Select the option "I" (capital I).5. Confirm the question with "y".

The system tries to install IndsysNT on all machines known to the FS.6. Press "y" in order to check the logfile (%temp%\IndsysNT_RInstall.log) for faults. If

faults have occurred (e.g. PC not available), you can simply repeat installation.7. Press a key to return to the main menu

5.3 Start IndsysNTIndsysNT can be started in two ways: Local start (e.g. SingleMachine, FS) Central start from the FS (all NetM-PCs in the OS except for the FS)Start IndsysNT on the PC on which you have detected problems. In addition to this, youshould also always start it on the associated CS (also ProxyCS) and FS, because manyfunctions are directly connected with the CS and the FS.

i In the case of central installation, no link is created in the start menu on the centrallyinstalled machines. This can be done later (if necessary) by means of a double click onthe file C:\#IndsysNT#\script\1st_Run.cmd.

!For each fault report, please supply the following standard symptoms

PC type Startal-

ways

Startwhen re-quired

Remarks

CS/FS X necessary for analysis of the base systemProxyCS X positive and negative case if possibleAPPLS XMFS XCT X positive and negative case if possible

Tab. 5.1 NetManager - standard symptoms

50 A30828-X1150-M588-5-7620


5.3.1 Local start1. Log on as domain administrator2. Click "Start/Programs/IndsysNT/IndsysNT"

3. Select the option "s" (small s)

Fig. 5.3 IndsysNT - local start4. Enter the required information. Confirm each item with [Enter].

Symptoms are collected.5. Press 'y' to have the symptoms compressed at once or 'n' if you want to copy other

symptoms into the directory beforehand. if you press 'y' the symptoms are compressed and are then available in the direc-

tory %SystemDrive%\#Symptoms#\*.ZIP. if you press 'n', continue with point 6)

6. Collect the additionally required symptoms and give the files an appropriate name.7. Copy the additional symptoms into the directory %SystemDrive%\#Symp-

toms#\\AddSymptoms.8. Start IndsysNT again, click "Start/Programs/ IndsysNT/IndsysNT"9. Select the option "c" (small c)

The symptoms are compressed and are then available in the directory %System-Drive%\#Symptoms#\*.ZIP.

The compressed symptoms can be sent away as described in section 3.3 "Saving addi-tional symptoms".

i In some cases, no link is created in the Start menu during installation. This can be donelater by means of a double click on the file C:\#IndsysNT#\script\1st_Run.cmd.

A30828-X1150-M588-5-7620 51

MaintenanceSystem


5.3.2 Central startIn this case IndsysNT must be started on the file server and can then collect the symp-toms from all machines that are known in the NetM OS.1. Log on as domain administrator2. Click on "Start/Programs/IndsysNT/IndsysNT"

3. Select the option "r" (small r)

Fig. 5.4 IndsysNT - central start4. Enter the host name of the NetM-PC from which you want to collect the symptoms

and confirm with [Enter]5. Enter the required information. Confirm each item with [Enter].

Symptoms are collected, compressed and transferred to the file server.6. Press either "y" to collect further symptoms (then continue with 4) or "n" if you want

to quit IndsysNT now.

5.4 IndsysNT restrictions1. Central installation needs a network that is working and NetM-PCs with activated ad-

ministration releases, i.e. the PCs must be available via the network. If this is not thecase, IndsysNT can only be installed locally.

2. In the case of central installation, no link is created in the Start menu on the centrallyinstalled machines. This can be done later at any time (if necessary) by means of adouble click on the file C:\#IndsysNT#\script\1st_Run.cmd.

3. If symptoms are collected centrally from an MFS, the response times may be longwhen you enter user information. However, this behavior does not affect the pro-cessing of IndsysNT.

i In some cases, no link is created in the Start menu during installation. This can be donelater by means of a double click on the file C:\#IndsysNT#\script\1st_Run.cmd.

52 A30828-X1150-M588-5-7620


5.5 IndsysNT abbreviations and variables

The name of the ZIP file consists of the following elements:%OSName%_%HOSTNAME%.ABCDE.yyyymmdd_hhmm.zip

APPLS Application ServerCS Communication ServerCT Craft TerminalFS File ServerMFS MetaFrame Server%SystemDrive% Contains the drive on which Windows NT is installed (usually

C:\%TEMP% System variable contains the path to the default temporary di-

rectory (usually C:\Temp)%OSName% Name of the NetManager OS%HOSTNAME% Computer name%MType% Machine type (F=FS, C=CS, T=CT, M=MFS) Subdirectory in which all symptoms are collected.

The name consists of the following elements:%OSName%_%HOSTNAME%.%MTYPE%

A = F IndsysNT detects function FSB = C IndsysNT detects function CSC = T IndsysNT detects function CT)D = M IndsysNT detects function MFSE = L/R L started locally / R started centrally

Saving of Error SymptomsContentsIntroductionEntries in the error reportOverview of fault classes on the CP Overview of the symptom files on the CPOverview of fault classes on the SSNCOverview of the Event Logs on the SSNCSymptoms on the CPSymptoms on the SSNC - allocation of fault classes

Saving Error Symptoms SSNC / CP via NetManagerIntroductionSymptom Saving ProcessTask descriptionParameter descriptionReport NumberExchange NameBegin DateExchange TypeCP Fault ClassSSNC Fault ClassCP Symptom FileSSNC Event LogAdditional symptomsSymptoms Server

Possible combinations of fault class and selective savingFault classes and system type

Error Symptom Saving: Quick StartSaving the logging data (MLOG)Saving standard symptomsStart the task on the NetMExample: Fault on powernodeWorking directories on NetMContents of working directory (Powernode)Postprocessing

Saving additional symptomsManual file transfer to the Symptrans PCSending symptoms using the Symptrans PCSending a normal symptom packetSending a split symptom packet

Causes of Script Truncation / Fault ClearanceFaulty inputsFault class not selectedParameter combination not possibleFault class not possible for this exchange typeBegin date was not enteredInvalid begin date Invalid report numberInvalid exchange name

General fault reports The working directory could not be createdThe configuration file cannot be openedInvalid exchange typeThe CP command file CG.SA.HMAST could not be copiedThe command could not be sentThe exchange does not respondThe command file was stopped manuallyThe command file was stopped by the NetManager Parallel processing of command filesThe CP symptom files are emptyReception of the CP symptom files was unsuccessfulThe symptoms could not be compressedThe FTP client could not be startedThe FTP server is not availableLogin to the FTP server is not possible The FTP destination directory does not existFTP file transfer unsuccessful

IndsysNT Symptom Saving for NetManager IntroductionInstallation of IndsysNTLocal installationCentral installation

Start IndsysNTLocal startCentral start

IndsysNT restrictionsIndsysNT abbreviations and variables

saving error system

Documents

ssnc fault class

error symptoms ssnc

overview of fault classes

fault classes92

additional symptoms

standard symptoms

symptoms server

cp fault class132