MMN:MB

MaintenanceCall & Feature Control

MMN:MB

A30828-X1187-M510-1-7620

2 A30828-X1187-M510-1-7620

MMN:MB MaintenanceCall & Feature Control

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 2004.Issued by the Communications Group Hofmannstrae 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-X1187-M510-1-7620 3


MMN:MB

Reason for UpdateSummary:

Details:

Chapter/Section Reason for Update

Issue HistoryIssueNumber

Date of issue Reason for Update

4 A30828-X1187-M510-1-7620


A30828-X1187-M510-1-7620 5


MMN:MB

This document consists of a total of 179 pages. All pages are issue 1.

Contents1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 References to Additional Documentation . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Information on Module Replacement . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.3 MBD Safeguarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.4 MBB Safeguarding . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81.5 Output of a Caution. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.6 Rejection of Configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.7 Rejection of the Diagnosis . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 122 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 132.1 MBB Fault Clearance Procedure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14

MB1102.2 MBB Fault Clearance Procedure: Diagnosis is not executed . . . . . . . . . . . 27

MB1202.3 MBB Error Message after Configuration Request. . . . . . . . . . . . . . . . . . . . 38

MB1302.4 MBB Diagnosis Progress Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39

MB1502.5 MBD Fault Clearance: MBIA or MBIH suspect . . . . . . . . . . . . . . . . . . . . . . 40

MB2102.6 MBIA Fault Clearance. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

MB2112.7 MBIA Fault Clearance: ATMB on module MBDA is suspect. . . . . . . . . . . . 58

MB2122.8 ATMB statistic failure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 67

MB2142.9 MBD Fault Clearance: MBIC suspect . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 69

MB2152.10 MBD Fault Clearance: MBICG suspect . . . . . . . . . . . . . . . . . . . . . . . . . . . 81

MB2252.11 MBD Error Message after Configuration Request . . . . . . . . . . . . . . . . . . . 93

MB2302.12 MBD Failure of Clock Reference . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 94

MB2352.13 MBD Fault Clearance Procedure: MBIE suspect . . . . . . . . . . . . . . . . . . . . 95

MB2402.14 MBIE Fault Clearance: IP DATA Error . . . . . . . . . . . . . . . . . . . . . . . . . . . 101

MB2412.15 MBIE Fault Clearance: MCH Failure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . 105

MB2432.16 MBIE Fault Clearance: Loss of Signal . . . . . . . . . . . . . . . . . . . . . . . . . . . 111

MB2442.17 MBD Fault Clearance Procedure: MBIECH Total Fault . . . . . . . . . . . . . . 118

MB2452.18 MBD Fault Cearance Procedure: MBIECH Partial Fault . . . . . . . . . . . . . 119

6 A30828-X1187-M510-1-7620


MB2462.19 MBD Fault Clearance Procedure: MGIF Failure Messages. . . . . . . . . . . . 124

MB2472.20 MBD Diagnosis Progress Message . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 126

MB2502.21 Determine MB Type for Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 127

PR:MB2.22 Test Procedure for MBB. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 128

PR:MBB2.23 Test Procedure for MBD . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 135

PR:MBD

3 Table . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1473.1 Distribution of the MBUs to the MB Frames and Racks. . . . . . . . . . . . . . . 148

AL:MBB3.2 Allocation MBD Unit - Modules . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 150

AL:MBD3.3 Allocation MBIE - LTGSET. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151

AL:MBIE3.4 Allocation LTG - GPP. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 152

AL:LTG3.5 Allocation ATM-Bridges on module MBDA . . . . . . . . . . . . . . . . . . . . . . . . 153

AL:ATMB3.6 Fault List MBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 154

FL:MBB3.7 Fault list MBD. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 158

FL:MBD3.8 Suspect SNA Modules-Interface MBB . . . . . . . . . . . . . . . . . . . . . . . . . . . . 160

FL:SNA13.9 Suspect SNA modules - Interface MBD. . . . . . . . . . . . . . . . . . . . . . . . . . . 167

FL:SNA23.10 Suspect SNB Modules - Interface MBB . . . . . . . . . . . . . . . . . . . . . . . . . . . 170

FL:SNB13.11 Suspect SNB modules - Interface MBD. . . . . . . . . . . . . . . . . . . . . . . . . . . 175

FL:SNB23.12 Suspect SNMUXA modules - Interface MBD . . . . . . . . . . . . . . . . . . . . . . 177

FL:SNDB3.13 Suspect SNMUXA modules - Interface MBD . . . . . . . . . . . . . . . . . . . . . . 178

FL:SND13.14 Suspect SNMUXB Modules - Interface MBD . . . . . . . . . . . . . . . . . . . . . . 180

FL:SND2

A30828-X1187-M510-1-7620 7


MMN:MB

1 Introduction

1.1 References to Additional Documentation

If you are familiar with the basic principle of the fault clearance you can start withfault clearance at once. Otherwise we advise that you read the appropriate registerin Documentation Overview in order to be able to use the manual effectively for faultclearance purposes. The Documentation Overview contains detailed information onall general aspects of fault clearance.

When replacing or handling modules please observe the Safety Instructions for per-sonal and products (EN60950/IEC60950).

1.2 Information on Module Replacement

Pay special attention (type label) to the HW/FW status of the modules when replacing.The replacement module must be compatible with the modules in the frame (same codenumber both for HW/FW and for functional status). The HW/FW status can also be takenfrom the exchange specific document of the network node. In exceptional cases deter-mine whether the functional status of the replacement module (regarding HW/FW) iscompatible with that of the other modules.

1.3 MBD Safeguarding

During the entire information exchange between the CP and the connected periphery,the MB checks for correct transmission of messages. This is done by validity checks ofthe transferred message bytes.The hardware and firmware of the MB are monitored by means of internal fault indicators(these are checkpoints, watchdogs, etc.) and with on-line statistics counters. In on-lineoperation, an internal routine test makes a continuous section-by-section check of theinternal program memories of the MB firmware.The CP automatically executes an additional routine test: Every 20 seconds the command LOOP checks the MB functions for each MB unit in

their entity. The command STAGCG is sent to the controller module MBDC which initiates an

interrogation and a check of the corresponding equipment (during the low-traffic pe-riod). All MB units are diagnosed. The modules are taken out of service one after theother and a diagnosis is started. The internal interfaces of the modules are checkedas well. The routine test checks especially the redundancy and safeguarding mea-surements, which are not used in normal operation and usually only activated whenfailures are detected.

Continuous monitoring or regular testing of the MB by the operator is therefore not nec-essary!If the system detects a malfunction, it initiates an MB alarm message containing the ex-isting information on the nature of the fault. If necessary, it automatically switches off thefaulty MB unit.

8 A30828-X1187-M510-1-7620


Fault clearance and restoral of the switched-off equipment is then carried out by craftpersonnel in accordance with the fault clearance procedure specified in the fault print-out.

Switching off a redundant MB unit does not degrade the system; therefore system soft-ware usually immediately removes the MB unit involved from service by configuring it toUNA when an MB fault is detected.Exceptions to this are: If a failure is detected in the 8 MHz clock reference FA:CCG is informed. Provided

there is redundancy in the CCG the active CCG is configured to UNA. Since the faultis probably not in the clock generator module MBDCG of the MBD, there is no rea-son for configuration.

If the redundant MB unit is already UNA or MBL and if the fault is not serious, a alarmmessage output. The affected unit is not configured. If the MB unit were to be con-figured down, there would be a partial failure or a total system failure. The MB unittherefore remains in ACT .

If serious faults are detected on module MBDH, MBDC and MBDCG, ISTART1 is per-formed, if no redundancy exists!

1.4 MBB Safeguarding

During the entire information exchange between the CP and the connected periphery,the MB checks for correct transmission of messages. This is done by validity checks ofthe transferred message bytes.The hardware and firmware of the MB are monitored by means of internal fault indicators(these are checkpoints, watchdogs, etc.) and with on-line statistics counters. In on-lineoperation, an internal routine test makes a continuous section-by-section check of theinternal program memories of the MB firmware.The CP automatically executes an additional routine test: Every 20 seconds the command LOOP checks the MB functions for each MBU in

their entirety. The command STAGCG to those MBU:LTGs which monitor a module with group

clock generator initiates an interrogation and a check of the corresponding equip-ment (during the low-traffic period).

Continuous monitoring or regular testing of the MB by the operator is therefore not nec-essary!If the system detects a malfunction, it initiates an MB alarm message containing the ex-isting information on the nature of the fault. If necessary, it automatically switches off thefaulty unit.Fault clearance and restoral of the switched-off equipment is then carried out by craftpersonnel in accordance with the fault clearance procedure specified in the fault print-out.

Switching off a redundant MBU does not degrade the system; therefore system softwareusually immediately removes the MBU involved from service by configuring it to UNAwhen an MBU fault is detected.

A30828-X1187-M510-1-7620 9


MMN:MB

Exceptions to this are: If a fault is detected in the group clock generator, the system software outputs a fault

information with GCG:MBG FAILURE. No MBU is configured. Since the fault is prob-ably not in the MBU, there is no reason for configuration. The MBU specified in thefault information monitors only the group clock generator and reports the fault.

If the redundant MBU is already UNA or MBL and if the fault is not serious, a alarmmessage with the code word MBU ERROR is output. The affected MBU is not con-figured. If the MBU were to be configured down, there would be a partial failure or atotal system failure. The MBU therefore remains in ACT (emergency service).

If serious faults are detected, ISTART1 is performed, if no redundancy exists!

1.5 Output of a Caution

Under certain circumstances, during configuration from ACT to MBL the system outputsa CAUTION and confirms the command before final execution. There are two types ofCAUTION messages:

CAUTION: THIS REQUEST MAY REMOVE THE SWITCHINGPERIPHERY FROM SERVICE !DO YOU WANT IT TO BE EXECUTED ? (YES: +/NO: -)

Documents

MMN:MB