bscit

GERAN

Installation TestBase Station Controller

ITMN:BSC

A50016-G5100-A250-01-7630

2 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d80580086195

f Important Notice on Product SafetyDANGER - RISK OF ELECTRICAL SHOCK OR DEATH - FOLLOW ALL INSTALLATION INSTRUCTIONS.The system complies with the standard EN 60950 / IEC 60950. All equipment connected to the system must comply with the applicable safety standards.Hazardous voltages are present at the AC power supply lines in this electrical equipment. Some components may also have high operating temperatures.Failure to observe and follow all installation and safety instructions can result in serious personal injury or property damage.Therefore, only trained and qualified personnel may install and maintain the system.

The same text in German:Wichtiger Hinweis zur ProduktsicherheitLEBENSGEFAHR - BEACHTEN SIE ALLE INSTALLATIONSHINWEISE.Das System entspricht den Anforderungen der EN 60950 / IEC 60950. Alle an das System angeschlossenen Gerte mssen die zutreffenden Sicherheitsbestimmungen erfllen.In diesen Anlagen stehen die Netzversorgungsleitungen unter gefhrlicher Spannung. Einige Komponenten knnen auch eine hohe Betriebstemperatur aufweisen.Nichtbeachtung der Installations- und Sicherheitshinweise kann zu schweren Krperverletzungen oder Sachschden fhren.Deshalb darf nur geschultes und qualifiziertes Personal das System installieren und warten.

Caution:This equipment has been tested and found to comply with EN 301489. Its class of conformity is defined in table A30808-X3247-X910-*-7618, which is shipped with each product. This class also corresponds to the limits for a Class A digital device, pursuant to part 15 of the FCC Rules.These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment.This equipment generates, uses and can radiate radio frequency energy and, if not installed and used in accor-dance with the relevant standards referenced in the manual Guide to Documentation, may cause harmful inter-ference to radio communications.For system installations it is strictly required to choose all installation sites according to national and local require-ments concerning construction rules and static load capacities of buildings and roofs.For all sites, in particular in residential areas it is mandatory to observe all respectively applicable electromagnetic field / force (EMF) limits. Otherwise harmful personal interference is possible.

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

Copyright (C) Siemens AG 2006Issued by the Communications GroupHofmannstrae 51D-81359 Mnchen

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

Copyright (C) Siemens AG 2006Issued by the Communications GroupHofmannstrae 51D-81359 Mnchen

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

A50016-G5100-A250-01-7630

3

ITMN:BSC

Id:0900d80580086195

Table of ContentsThis document has 54 pages.

Reason for Update . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.1 Purpose of the Document . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2 Precautions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.1 Access to Electrical Installations. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71.2.2 Handling Modules with Electrostatically Sensitive Components. . . . . . . . . . 71.2.3 Check List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 91.2.4 Required Instruments . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 9

2 Tasklist . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.1 Visual Control of BSC1 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.2 Bring-up: the BSC1 Activation Process . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.3 Data Base Completion . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.4 Alarm Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 102.5 BSC1 Restart Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10

3 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.1 Check of Modules and Auxiliary Equipment for High-Capacity (C20-X rack)

configurations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 113.2 Check of Modules and Auxiliary Equipment for BSC/72, BSC/120 HC 2nd Step

(S30861-C36/C40-X) configuration. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 143.3 Check of Modules and Relevant Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . 173.4 Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 183.5 Check of the Jumper Settings. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 203.6 BSC1 "Bring-Up". . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 213.7 MPCC Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 253.8 BSC1 Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 273.9 Download of a SW load header file on BSC1 disk . . . . . . . . . . . . . . . . . . . 283.10 Check of SW images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 293.11 Inventory Data: Preparation to use Remote Inventory Feature . . . . . . . . . 303.12 Module State Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 393.13 Module Quantity Expansion for BSC/72 and BSC/120 HC. . . . . . . . . . . . . 403.14 Alarm Panel Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 423.15 Module Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 433.16 Module Switch. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 453.17 External Alarm Check for C20-X rack . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 463.18 External Alarm Check for BSC/120 HC C36/C40-X rack . . . . . . . . . . . . . . 483.19 Power On/Off Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

4 Appendix . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 534.1 EPROM Firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

4 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d80580086195

List of FiguresFigure 1 IDF Editor Evolution - Edit. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 31Figure 2 Edit nob_RIU dialog box . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32Figure 3 Export IDF File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 4 Reminv command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33Figure 5 File menu: Attach command . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34

A50016-G5100-A250-01-7630

5

ITMN:BSC

Id:0900d80580086195

List of TablesTable 1 Input and output data of the IDF Editor . . . . . . . . . . . . . . . . . . . . . . . . . 30Table 2 List of nob_RIUs for BSC/72, BSC/120 HC . . . . . . . . . . . . . . . . . . . . . . 34Table 3 BSC1 firmware. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53

6 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800eaf00

Reason for Update

Reason for UpdateIssue History

Issue 1 for Release BR9.0 (12/2006)

Issue Date Summary01 12/2006 New release BR9.0

A50016-G5100-A250-01-7630

7

ITMN:BSC Introduction

Id:0900d805800df1dd

1 Introduction

1.1 Purpose of the DocumentThis document is intended as a guide to the operating phases, for the benefit of the installation commissioning personnel.g This manual is valid only for the GSM BSC1.The manual is divided into the following sections: Section 1: Introduction. This section provides general background information

relevant to precautions in handling the modules and to the list of commissioning checks.

Section 2: Tasklist. The Tasklist section provides the list of the commissioning acti-vities.

Section 3: Commissioning Procedures & Hardware Expansion Procedures. This section describes the procedures used to install and check the equipment of a Base Station Controller. The last procedures describe the installation of new hard-ware. The user is guided to add and configure new modules to meet any increased performance requirements when the system is on-line handling calls.

Section 4: Appendix. This section provides information relevant to firmware and EPROMs to be equipped on the modules.

1.2 Precautions

1.2.1 Access to Electrical InstallationsCertain parts of equipment in electrical installations must remain powered. Some parts may also operate at high operating temperatures.Physical injuries and/or damage to the product may occur if this situation and the appro-priate warnings are not observed.It is assumed that the system is installed, switched on and maintained only by suitably trained and qualified personnel.

1.2.2 Handling Modules with Electrostatically Sensitive ComponentsThe modules are to be handled with extreme care as each one contains a number of electrostatically sensitive components.All integrated modules used (including TTL) are electrostatically sensitive devices (ESDs). All modules are marked with the ESD symbol. The following precautions are to be taken: Personnel should avoid wearing synthetic clothing and shoes with plastic soles, as

these foster the build-up of electrostatic charge. Before handling modules, personnel should be freed of any electrostatic charge. For

this reason, personnel should always put on a grounded wrist strap before changing a module.

Before touching modules, printed circuits or components, the wrist strap must be con-nected to the ground potential of the rack by means of a flexible lead integrating a high-value discharge resistor. The discharging socket in the holder of the special tool for

8 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800df1dd

Introduction

changing modules must be used for connecting the wrist strap to the ground potential. This holder is located on the right vertical strut of the module side of the rack. Note that the conducting parts of the split pin should not be touched when plugging it in (by-passing the discharge resistor).IMPORTANT:Modules with the ESD symbol are to be handled with extreme care. Static or external voltage may lead to long-term damage to the modules.In general, the printed circuits and components of modules should not be touched. Modules should be held only by their edges.Removed modules are to be placed in covers made of conductive plastic (provided) and then stored or sent off in special transport boxes or cases bearing the ESD symbol.Faulty modules are to be treated with as much care as new ones, so as to prevent further damage.All tools, measuring devices and metal objects that come in contact with removed modules are to be discharged to the ground potential before being used.To summarize:1. ESDs should not be allowed to touch electrostatically charged or chargeable

objects.2. ESDs should only come in contact with high-value discharging material ("gentle" dis-

charging), i.e. should not undergo "harsh" discharging with, for example, a metal plate.

3. ESDs should be set down on grounded surfaces only (flexible bases with a ground-ing connection for servicing purposes).

4. ESDs should only be transported in authorized packaging. A grounded wrist strap must be put on before removing ESDs.

5. ESDs should not be brought near strong DC electrical fields, e.g. cathode-ray tubes/monitors (safety distance at least 10 cm/ 3.9).

6. Maintenance personnel should check the discharge resistance of the wrist straps at regular intervals.

7. Even discharges that are considerably lower than the detection limit can damage or destroy ESDs!

A50016-G5100-A250-01-7630

9

ITMN:BSC Introduction

Id:0900d805800df1dd

1.2.3 Check Listg The CE declaration of conformity for the product will be fulfilled if the setup and

cabling is executed in accordance with the specification in the manual and the do-cumentation listed here, such as mounting instructions, cable lists etc. Where nec-essary, account should be taken of project-specification documentation. Deviations from the specifications or independent changes during setup, such as use of cable types with lower screening values, for example, can lead to the CE requirements being violated. In such cases, the CE declaration of conformity is invalidated and the responsibility passes to the person who has caused the deviations.

g This equipment has been tested and found to comply with the limits for a Class A digital device, pursuant to Part 15 of the FCC Rules. These limits are designed to provide reasonable protection against harmful interference when the equipment is operated in a commercial environment. This equipment generates, uses, and can radiate radio frequency energy and, if not installed and used in accordance with the instruction manual, may cause harmful interference to radio communications. Ope-ration of this equipment in a residential area is likely to cause harmful interference in which case the user will be required to correct the interference at his own expense.

The commissioning personnel follows the Commissioning Check List to carry out any activity.The Commissioning Check List includes the following activities: Visual Control; BSC1 Bring-UP and Module State Verification; Database Completion; Alarm Verification; Restart Verification.

g All commissioning tasks on site have to be confirmed in the Unit ATMN.

1.2.4 Required InstrumentsThe required test equipment and tools for the Installation Test of the BSC1 are: LMT Evolution (laptop + V.11 Interface Card; see OGL:LMT Evolution); a digital multimeter.

10 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b7018

Tasklist

2 Tasklist

2.1 Visual Control of BSC11 Check of Modules and Auxiliary Equipment for C20-X rack . . . . . . . 3.11 Check of Modules and Auxiliary Equipment for C36/C40-X rack . . . . 3.22 Check of Modules and Relevant Codes . . . . . . . . . . . . . . . . . . . . . . . 3.33 Check of Power Supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.44 Check of Jumpers Setting . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.55 Inventory Data: Preparation to the Use of Remote Inventory Feature 3.116 Firmware EPROM Position . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4.1

2.2 Bring-up: the BSC1 Activation Process1 BSC1 Bring Up . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.62 MPCC Loading . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.73 Download of a SW load header file on BSC1 disk . . . . . . . . . . . . . . . 3.94 Check of SW images . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.105 BSC1 Reload . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.86 Module State Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.12

2.3 Data Base Completion2 Module Quantity Expansion for BSC/72, BSC/120 HC . . . . . . . . . . 3.133 Module Test . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.154 Module Switch . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.16

2.4 Alarm Verification1 Alarm Panel Verification . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.142 External Alarm Check for C20-X rack . . . . . . . . . . . . . . . . . . . . . . . 3.173 External Alarm Check for C36/C40-X rack . . . . . . . . . . . . . . . . . . . 3.18

2.5 BSC1 Restart Verification1 Power On/Off Sequence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3.19

A50016-G5100-A250-01-7630

11

ITMN:BSC Procedures

Id:0900d805800b2a30

3 ProceduresThe procedures described in the following pages are primarily related to commissioning activities.

3.1 Check of Modules and Auxiliary Equipment for High-Capacity (C20-X rack) configurationsThe following rules only refer to the currently available BSC1 configurations, and in par-ticular to the types of equipment provided.

Mandatory Hardware changes in BR 8.0From BR 8.0 on: SN16, PPLD, PPCU and PPCC boards are no more supported; the High Capacity

boards PPXX and SNAP have to be used. Only the latest versions of TDPC and MPCC /TDPCV9 and MPCCV9) are sup-

ported. The standard rack S30861-C14-X is no more supported (must be noticed that the

HW configuration of S30861-C14-X is frozen at BR6.01).PrerequisitesThe BSC1 unit must have been installed following the rules and methods specified in the IMN:BSC manual.

1 BSC1 Equipment for high-capacity (72 TCH) With reference to MMN:BSC, chapter Hardware Equipment , check for the

presence of the following elements: LP Lamp Panel in pos. T. BSCE Expansion Subrack in pos. A, B (equipped as necessary). BFAP Fuse and Alarm Panel in pos. D. BSCB Base Subrack in pos. F, G. OPDS Open Door Sensor in pos. O (only if requested). FG flame guard door, fans in pos. H, T (only if requested).

2 BSCB: Base Subrack for BSC/72, BSC/120 HC (high capacity)

- Check for the presence of the following modules in the Subrack:

The BSCB is always equipped, as it shown in the MMN:BSC, chapter Hardware Equipment, F and G positions.

Modules QuantityDK40 Led Alarm Panel Control 1 (only side

0)IXLT O&M Interface to OMS-B and to LMT Evolution 1+1UBEX Universal Bus Extender Module 1+1

12 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3 BSCE: Expansion Subrack for BSC/72, BSC/120 HC (high capacity)The BSCE is equipped as necessary. In the MMN:BSC, chapter Hardware Equipment, A and B positions, it is shown the maximum configuration.Check for the presence of the following modules in the Subrack:

4 BFAP fuse and alarm panelg Refer to MMN:BSC, chapters Fuse and Alarm Panel and Lamp Panel.Check for the presence of the following components: The LEDs displaying the equipment alarms; The fuses through which the power is fed to the BSC equipment; The connector interfacing the LMT Evolution; The LAMP TEST switch.

The LEDs located on BFAP are of 3 colors having the following meaning: Green for Equipment alarms; Amber for Minor alarms; Red for Major and Critical alarms.

5 LAMP panelg Refer to MMN:BSC, chapter Lamp Panel.Check for the presence of the LAMP Panel that displays the BSC1 system general alarm status.

On the top of the rack check the cables interconnecting the PM2 sockets and the PM3 sockets as well as that on PF1 coming from temperature sensors.

SNAP Switching Network 1+1TDPC Telephony Distribution Processor 1+1MEMT Memory of the Telephony Processor 1+1MPCC Administrative Processor 1+1PWRS Power Supply 1+1PLLH Clock Unit 1+1QTLP QuadTrunk Line Interface 2+1PPXL Peripheral Processor LAPD/SS7 1+1

Modules QuantityEPWR Power Supply 1+1QTLP QuadTrunk Line Interface 7+1PPXU Peripheral Packet Control Unit used at PPCU Evolution 6

A50016-G5100-A250-01-7630

13

ITMN:BSC Procedures

Id:0900d805800b2a30

6 OPDS: Open Door Sensorg The Open Door Sensor is an optional component.

Refer to MMN:BSC, chapter Hardware Equipment , lower position.Check for the presence of the Open Door Sensor.The Open Door Sensor Alarm is associated with a condition relating to an enclosure in which the equipment resides.

7 FG: Flame-Guard kitg The FG is an optional kit made up of flame-guard door, fans assembly and ground-

ing collector. Refer to IMN:BSC, chapter Grounding collector and fire protection kit.Check for the presence of the flame-guard door, fans assembly in position H and grounding collector on the top of the rack in T position.

8 System ResponseThis procedure consists of a visual check for the physical presence of all the BSC com-ponents; therefore, no response messages are generated by the system.

END

14 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.2 Check of Modules and Auxiliary Equipment for BSC/72, BSC/120 HC 2nd Step (S30861-C36/C40-X) configurationThe following rules only refer to the currently available BSC1 configurations, and in par-ticular to the types of equipment provided.PrerequisitesThe BSC1 unit must have been installed following the rules and methods specified in the IMN:BSC manual.

Mandatory Hardware changes in BR 8.0From BR 8.0 on: SN16, PPLD, PPCU and PPCC boards are no more supported; the High Capacity

boards PPXXv2 and SNAP have to be used. Only the latest versions of TDPC and MPCC (TDPCV9 and MPCCV9) are sup-

ported. The standard rack S30861-C14-X is no more supported (must be noticed that the

HW configuration of S30861-C14-X is frozen at BR6.01).

New feature in BR8.0With BR 8.0 High Speed Gb Interface feature is managed; in order to provide the Ethernet connectivity needed for HS Gb, two HW modules and two cabling kits have been developed: ESAM board, that replaces CPEX board in BSC/72 and DK40 board in BSC/120 HC; PPXXv2 board, that replaces PPXXv1 board; Cabling Kit connection between the ESAM boards and the Top of the Rack; Cabling Kit connection between the ESAM boards and PPXXv2 boards.

1 BSC1 Equipment With reference to MMN:BSC, chapter Hardware Equipment, check for the

presence of the following elements: LP Lamp Panel in position T; BSCUV3 Expansion Subrack in pos. A, B,C; DCP Alarm Panel in pos. D; BSCLV3 Base Subrack in pos. E, F, G; OPDS Open Door Sensor in pos. H; Fans in pos. H.

2 BSCB: Base Subrack (BSCLV3) for GSM- Check for the presence of the following modules in the Subrack:

Modules QuantityIXLT O&M Interface to OMS-B and to LMT Evolution 1+1UBEX Universal Bus Extender Module 1+1SNAP Switching Network 1+1

A50016-G5100-A250-01-7630

15

ITMN:BSC Procedures

Id:0900d805800b2a30

- Check for the presence of. the connecting cables between TDPC copy o/1 and between MPCC copy 0/1.

3 BSCEB: Expansion Subrack (BSCUV3) for GSM systemThe BSCEB is equipped as necessary.Check for the presence of the following modules in the Subrack:

4 BFAP breakers and alarm panelg Refer to MMN:BSC, chapter DC Panel of the BSC120 HC 2nd Step.Check for the presence of the following components: the LEDs displaying the equipment alarms; the breakers through which the BSC1 equipment is fed; the connector interfacing the LMT Evolution; the LAMP TEST switch.

The LEDs are of 3 colors having the following meaning: Green for Equipment alarms; Amber for Minor alarms; Red for Major and Critical alarms.

5 LAMP panelg Refer to MMN:BSC, chapter Lamp Panel.Check for the presence of the LAMP Panel that displays the BSC1 system general alarm status.

On the top of the rack check the cables interconnecting the PM2 sockets and the PM3 sockets as well as that on PF1 coming from temperature sensors.

TDPC Telephony Distribution Processor 1+1MEMT Memory of the Telephony Processor 1+1MPCC Administrative Processor 1+1PWRS Power Supply 1+1PLLH Clock Unit 1+1STLP Line Interface 3+1PPXL Peripheral Processor LAPD/SS7 1+1

Modules Max. Quantity

STLP Line Interface 7+1PPXU Peripheral Packet Control Unit 12

16 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

6 System ResponseThis procedure consists of a visual check for the physical presence of all the BSC1 com-ponents; therefore, no response messages are generated by the system.

END

A50016-G5100-A250-01-7630

17

ITMN:BSC Procedures

Id:0900d805800b2a30

3.3 Check of Modules and Relevant CodesThe BSC1 modules and other removable units are identified with a standard label that includes both an alphanumeric code and a bar code. Both codes carry the same infor-mation, i.e. the Module Code, the Issue Number and the Serial Number, that are printed on the same label.PrerequisitesA document must be available describing the correct codes of the BSC1 modules (S.V.R. Stocklist or other).

1 Stocklist checkCheck that the alphanumeric module code matches the values on the list.

2 ResultsThis procedure makes sure that the correct component versions are installed.

END

18 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.4 Power SupplyIn order to avoid any power fault, it is necessary to check for the presence of the fuses on the alarm panel and to verify the power supply.PrerequisitesBefore switching on the two main magnetothermic 48 V DC circuit breakers check the power supply conductors polarity and grounding cables as explained in the IMN:BSC manual.

1 BSC1 Power onFor S30861-C20-X rack:On each power supply card press the black button and shifting the OFF REQ switch lever to the upper position.For S30861-C36/C40-X rack:Put the release levers of the breakers in the DC-Panel to the upper position.

2 Voltage check Locate the PWRS test points and by using an high impedance voltmeter verify for each power module: +12.3 V for M1; +5.3 V for M2; primary 48 volt for M3.

3 SpecificationsUse the following specifications to check for the actual correspondence:

- VOLTAGE -48 VDC (range: 38.4-57.6 V)- POWER SUPPLY

REQUIREMENTS (max):BSCB + BSCE MODULE 475 W for BSC1 regular capacity

490 W for BSC1 72 channels594 W for the BC120-HC rack (657 W fully equipped)

- BFAP (only for -C20-X rack) four 10A and one 1A FUSESDCP (only for -C36/C40-X rack) two 16 A breakers for the Base (lower) rack

two 10 A breakers for the Expansion (upper) racktwo 2 A breakers for the Fan unitsone 2 A breaker for Alarm Panel

- UPSTREAM PROTECTION 20A (curve C) DC unipolar magnetotermic circuit breaker with auxiliary contact.

A50016-G5100-A250-01-7630

19

ITMN:BSC Procedures

Id:0900d805800b2a30

4 System responseThis procedure tests the power distribution and makes sure that the voltages required for a correct use of the equipment are met and therefore no response messages are generated by the system.

END

20 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.5 Check of the Jumper SettingsThis procedure makes sure that the jumpers setting of all modules installed have been executed correctly.g Refer to the chapter Jumpers setting in the MMN:BSC manual.

1 BSC/72 (C20-X rack) Check the Jumper Settings of the following modules:

DK40 IXLT MEMT MPCC PLLH PPXL PPXU QTLP SNAP TDPC UBEX

2 BSC/120 HC (C36/C40-X rack) Check the Jumper Settings of the following modules:

IXLT MEMT MPCC PLLH PPXL PPXU STLP SNAP TDPC UBEX

END

A50016-G5100-A250-01-7630

21

ITMN:BSC Procedures

Id:0900d805800b2a30

3.6 BSC1 "Bring-Up"IntroductionThe "Bring-Up" process performs system initialization. The system is set to the proper initial state, to correctly run under the Operating System. During this phase, all the system processors are loaded with the required Software Version.The procedure is fully automatic at power up and, once activated, it can only be inter-rupted by another Bring-up request.The firmware, implemented in the configuration EPROM, loads the executable software from the disk placed on the MPCC board.If the disk is empty, the MPCC load can be done from an LMT Evolution by entering the LOAD MPCC command available on the LMT Evolution menu during Bring-Up (phase 1) (see "3.7 MPCC Loading").The Bring Up procedure tries to continue its execution even if any of the mentioned steps failed; it is because the system tries to return in a suitable state, in which the User is allowed to perform the appropriate action to restore the correct behavior. Obviously some of the mentioned steps can only be executed if other related actions are success-fully completed. For example the peripheral processors can only be loaded if the TDPC processor was successfully loaded and started (the peripheral processors are subordi-nated to the TDPC in the BSC1 hierarchy); or the TDPC Data Base can only be loaded after the MPCC Data Base has been successfully loaded.

Load sequence for BSC/72 and BSC/120 HC

1. Load of MPCC software by MPCC firmware;*** INFORMATION ***Loading From Disk:name = UNKNOWNdiskCopy = COPY1sourceDirectory = "SYS_BACKUP"fileSoftwareVersion = "02-06-01-01-16-01_01-05-25"neSoftwareVersion = "02-06-01-01-00-29_01-05-25"

*** INFORMATION ***Successful Load From Disk:name = UNKNOWNfwNckCause = NO_ERROR

2. The MPCC software starts; it initializes all devices and then the BSC1 load controller obtains control and begins to load base processors.*** INFORMATION ***Set Notification BSCOSUSW:name = BSCOSUSW:0phase = LOAD_BACKUP_ESU_SW

3. Permanent MPCC patch loading, if present, otherwise pass to next step; note that patches whose attribute PERMANENT wasnt set as true are not loaded.*** INFORMATION ***Load Patch In Progress Information RSUPCH:

22 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

name = RSUSWLH:4/RSUEXE:0/RSUPCH:0processorType = MPCCuserLabel = "PATCH0 MPCC LOAD 16"

*** INFORMATION ***Successful Load Patch RSUPCH:name = RSUSWLH:4/RSUEXE:0/RSUPCH:0processorType = MPCC

4. The following three steps are executed in parallel: MPCC Data Base load (if the involved BSCESUDB object is ENABLED) IXLT software load on both processor copies TDPC software load on the active processor copy*** INFORMATION ***SystemInfoReport:name = BSC:0informationIdentifier = MPCC Database Load Startoriginator = 2002neSoftwareVersion = "02-06-01-01-00-29_01-05-25"

*** INFORMATION ***Load in progress RSUEXE:name = RSUSWLH:4/RSUEXE:4processorType = IXLTsetOfProcessors = 0 & 1neSoftwareVersion = "02-06-01-01-00-29_01-05-25"fileSoftwareVersion = "02-06-01-01-16-00_01-05-21"

*** INFORMATION ***Load in progress RSUEXE:name = RSUSWLH:4/RSUEXE:1processorType = TDPCsetOfProcessors = 1neSoftwareVersion = "02-06-01-01-00-29_01-05-25"fileSoftwareVersion = "02-06-01-01-16-00_01-05-21"

*** INFORMATION ***SystemInfoReport:name = BSC:0informationIdentifier = MPCC Database Load Endoriginator = 2002neSoftwareVersion = "02-06-01-01-00-29_01-05-25"

*** INFORMATION ***Successful load RSUEXE:name = RSUSWLH:4/RSUEXE:4processorType = IXLTsetOfProcessors = 0 & 1

*** INFORMATION ***Successful Load RSUEXE:

A50016-G5100-A250-01-7630

23

ITMN:BSC Procedures

Id:0900d805800b2a30

name = RSUSWLH:4/RSUEXE:1processorType = TDPCsetOfProcessors = 1

Permanent TDPC patch load (if present, otherwise pass to next step); note that patches whose attribute PERMANENT wasnt set as true are not loaded.

*** INFORMATION ***Load Patch In Progress Information RSUPCH:name = RSUSWLH:4/RSUEXE:1/RSUPCH:0processorType = TDPCuserLabel = "PATCH 0 TDPC LOAD 16"

*** INFORMATION ***Successful Load Patch RSUPCH:name = RSUSWLH:4/RSUEXE:1/RSUPCH:0processorType = TDPC

5. TDPC Data Base Load.*** INFORMATION ***SystemInfoReport:name = BSC:0informationIdentifier = TDPC Database Alignment Startoriginator = 2002neSoftwareVersion = "02-06-01-01-00-29_01-05-25"

*** INFORMATION ***SystemInfoReport:name = BSC:0informationIdentifier = TDPC Database Alignment Endoriginator = 2002neSoftwareVersion = "02-06-01-01-00-29_01-05-25"

6. The initialization of FULL level is automatically executed in order to start the software and the Data base loaded in the processors.

7. MPCC and TDPC in service processors execute software crosscopy on the other copies.

8. The peripheral processors PPXL and PPXU are loaded in parallel.*** INFORMATION ***Load in progress RSUEXE:name = RSUSWLH:6/RSUEXE:6processorType = PPXLsetOfProcessors = 0 & 1neSoftwareVersion = "02-06-02-01-00-B2_01-12-04"fileSoftwareVersion = "02-06-02-01-08-01_01-PP-XL"

*** INFORMATION ***Load in progress RSUEXE:name = RSUSWLH:6/RSUEXE:7processorType = PPXUsetOfProcessors = 0 & 1 & 3

24 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

neSoftwareVersion = "02-06-02-01-00-B2_01-12-04"fileSoftwareVersion = "02-06-02-01-00-06_01-12-03"

*** INFORMATION ***Successful load RSUEXE:name = RSUSWLH:6/RSUEXE:6processorType = PPXLsetOfProcessors = 0 & 1

*** INFORMATION ***Successful load RSUEXE:name = RSUSWLH:6/RSUEXE:7processorType = PPXUsetOfProcessors = 0 & 1

9. The application software waits for the notification of the result of the start actions from the local processor controllers and notifies the conclusion of the Bring Up pro-cedure to the Users terminal. When the attribute phase of the object BSCOSUSW is set to IDLE, the procedure can be considered as terminated.

*** INFORMATION ***Set Notification BSCOSUDB:name = BSCOSUDB:0runningESU = BSCESUDB:0

*** INFORMATION ***Set Notification BSCOSUSW:name = BSCOSUSW:0runningESU = BSCESUSW:4

*** INFORMATION ***Set Notification BSCOSUSW:name = BSCOSUSW:0phase = IDLE

PrerequisitesThe BSC "Bring-Up" process takes place in dedicated mode and the system cannot do any other function except for loading.

1 Automatic Bring-Up procedureThe user should not perform any procedures until the "Bring-Up" is ended.

END

A50016-G5100-A250-01-7630

25

ITMN:BSC Procedures

Id:0900d805800b2a30

3.7 MPCC LoadingIntroductionThe MPCC executable loading is automatically performed during the first installation and during "Bring-Up" initialization. This is the initial operation at "power up". The suc-cessful execution of this phase is a basic condition for the execution of the following phases.At "power up" a logic configuration, implemented in the configuration EPROM, will deter-mine which MPCC copy is active; the other one will be in hot-standby mode. When the active processor is powered up, it is reset and, since it has not been loaded, the load check fails and the processor goes into a loading state. In this state, the MPCC firmware looks for a valid load in the system disk and, if the system cannot load , the "Bring-Up" stops and displays an UNSUCCESSFUL LOAD message:

In this case, since the MPCC firmware isnt able to load MPCC software, it is necessary to reload the MPCC software from the LMT Evolution by entering the LOAD MPCC command from the LMT Evolution. The command is available on the LMT Evolution menu only during the "Bring-Up" (phase 1).

g From BR 8.0 only the latest version of MPCC (MPCCv9) is supported.PrerequisitesThe user must have the visibility level number set to "3" (Super User).

1 Loading MPCC during the "Bring-Up"Enter the following command:b MANAGED-ELEMENTSOFTWARE MANAGEMENTLOADMPCC SOFTWARE-MANAGEMENTLOADMPCC:SRCDIR=c:\.....,HEADER=HBxxyyzz.SWL,SOURCE=LMT;The "Bring-Up" process restarts automatically after this command. It is displayed on LMT Evolution menu, only during the "Bring-Up".

2 System ResponseThe procedure takes about 50 minutes to complete.The BSC1 goes over to Phase 2 and the user needs to insert the following:

g For login and password please contact your local service organization.The LMT Evolution shows the containment tree.

*** INFORMATION ***

UNSUCCESSFUL LOAD FROM DISK:

Load not Found Anywhere

Login: login Password: password

26 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

END

For detailed information refer to the same chapter in the OMN:BSC- MPCC Loading.

A50016-G5100-A250-01-7630

27

ITMN:BSC Procedures

Id:0900d805800b2a30

3.8 BSC1 ReloadIntroductionIt could be necessary to reload the BSC1 because of faults or software upgrades.There are three ways to cause a reload:1. the first one consists of switching the power supply off and on;2. the second one is MPCC cards hardware reset;3. the third one is performed by a SETRUNBACK command on the BSCOSUSW

object, which allows system reload.

1 Load the systemTo load the whole system the user must enter the SETRUNBACK BSCOSUSW command, following the next sequence of selections:b MANAGED-ELEMENT ---> SOFTWARE-MANAGEMENT ---> BSCOSUSW ---> SETRUNBACK BSCOSUSW Result: The BSC1 is reloaded. The loading process takes approximately five minutes.

END

For more information refer to the same chapter in the OMN:BSC- BSC Reload.

28 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.9 Download of a SW load header file on BSC1 diskIntroductionThis procedure allows the performance of the download of a SW load header file on BSC1 disk.To execute the download, the operator must create an instance of the RSUSWLH object. The attributes that the BSC1 application considers mandatory for executing this command are: userLabel (ULAB): is a user-defined string that identifies the SW load to which the

software load header file is related; SRCPATH: contains the path of the LMT Evolution directory that contains the SW

load header file; the user can use the Browse Dir button to select both the directory and the SW load header file on the LMT Evolution disk;

DNLALLEXE: allows to specify if, besides the SW load header file, all the executable file must be uploaded.

PrerequisitesThe RSUSWLH object to be created can not have the same version of another RSUSWLH object already created.The user must have the visibility level number set to "2".The Network Element must be in phase "2".

1 Download of SW load header file on BSC1 diskThe user must enter the CREATE RSUSWLH command following the next sequence of selections:b MANAGED-ELEMENT ----> SOFTWARE-MANAGEMENT ---> RSUSWLH---> CREATE RSUSWLHResult: the chosen SW load header file will be download to the BSC1 and according to the Network Element type a correspondent ESU instance is generated.For more information refer to the same chapter in the OMN:BSC- Download of a SW load header file on BSC1 disk.

END

!CAUTION - Loss of connectionDuring the download of SWL files the BSC1 software checks every 2 minutes the presence of the file on BSC1 disk. If the file is missing the related RSUEXE object goes in disabled-failed.If during a Software download a link interruption on the LMT-BSC connection happens, the user has to wait until this timeout will be expired inside the BSC1 in order to download again the software.

A50016-G5100-A250-01-7630

29

ITMN:BSC Procedures

Id:0900d805800b2a30

3.10 Check of SW imagesThe BSC1 Software images have to be checked in order to ensure that the download has been completed successfully. The SW load identifiers have to be compared with the ones in the SW Release Notes.

PrerequisitesThe download of EXE (BSC1 software) Files in the SYS_BACKUP Directory must have been executed successfully.The user must have the visibility level number set to "2".The Network Element must be in phase "2".

1 Get SW information about a BSC1To get SW information about a BSC1, the user must enter the GETINFO BSCESUSW command, following the next sequence of selections:b MANAGED-ELEMENT ---> SOTWARE-MANAGEMENT ---> BSCESUSW ---> GETINFO BSCESUSWResult: BSC SW Version is displayedFor more information refer to the same chapter in the OMN:BSC- Get information about SW version.

END

30 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.11 Inventory Data: Preparation to use Remote Inventory FeatureThe Remote Inventory feature requires that the complete, individual Product Identifica-tion Data (PID) of each inventory object, including issue and serial number, are stored in the inventory object itself, electronically and non-volatile. The on-board memory for the PID is called Info-element. Modules that have their inventory data on board are called "On Board Remote Inventory Units" or ob_RIUs.In order to manage the inventory data of objects without an Info-element (e.g. frames, racks, etc.) called "Not On Board Remote Inventory Units" or nob-RIUs the Inventory Editor Evolution tool has been implemented.The Regional Logistic Centre (RLC) provides all the inventory data that the commis-sioner needs to enter into the network element with an inventory data file on a rack basis together with the racks.The task of the commissioner is to create the complete nob_RIU file to be downloaded to the core module of the BSC1.The main BSC1 Remote Inventory files are:1. IDF;2. IDT;3. NOB;4. ZDT.The following table provides an overview of the input and output data of the IDF Editor Evolution:

g C_IDF and C_TXT are only output files (produced by the IDF Editor Evolution, from the .ZDT files). The C_IDF file is used as backup of the structure content to be sent to the main database. The C_TXT file has the same content as the C_IDF but in a more readable format for the user.

The PID are combined with the mounting location and network element data to create the complete Inventory Data Table (IDT). The IDT file is structured into three Records: N: Network Element Record, containing basic information of the NE.

The BSC1 is identified by the "C" letter. S: Structure Record arranges the inventory objects in the functional structure of the

NE. I: Inventory Record lists the inventory objects currently contained in the NE by their

physical identification (mounting location identifier), their functional identification (code numbers, status, ...) their (production) serial number and data on the history of the inventory object.

Input OutputIDT IDF, NOBIDF IDT, NOBZDT C_IDF, C_TXT

Table 1 Input and output data of the IDF Editor

A50016-G5100-A250-01-7630

31

ITMN:BSC Procedures

Id:0900d805800b2a30

After uploading the IDT to the LMT Evolution, the IDT is converted, with the support of the IDF Editor Evolution, to a Inventory Data File (IDF) with the addiction of a header and footer records.The NOB file format is only used for storing the nob_RIUs. It is the IDT format minus N-Record.The ZDT file format is used for the transfer of the Central-IDT located at the BSC1 towards the LMT Evolution or Radio Commander using file compression.This file format can only be decoded within the system.The IDF Editor Evolution is an indipendent off-line tool. It could be installed on the same machine on which it runs also the LMT Evolution.Main IDF Editor Evolution tasks are: Modify uploaded IDT (creation, deletion and edit of nob_RIUs only); Convert uploaded IDTs into IDFs; Attach one NOB file to an IDF; Remove all redundant nob_RIUs; Export NOB file for download to the BSC1.In the next figure it is represent the main panel of IDF Editor Evolution for the nob_RIU Inventory data management.

Figure 1 IDF Editor Evolution - Edit

In the next figure its represented the IDF Editor evolution dialog box for the manual ma-nagement of nob_RIU inventory data.

32 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

Figure 2 Edit nob_RIU dialog box

The IDF Editor Evolution supports the inventory data entry also by means of a 2D-Code-Reader: every input requesting Hardware (HW Item Number, HW Functional Status) data, Firmware (FW Item Number, FW Functional Status) data or Serial Number of an inventory object is possible via the 2D-Code-Reader and by pressing the Scan button. The data are inserted in the relevant fields (for more details see the OGL:IDF Evolution Manual).

In the next figures, the IDF Editor Evolution GUI support for the Export, Attach functions, is represented; and Reminv is a command supported by LMT Evolution.

A50016-G5100-A250-01-7630

33

ITMN:BSC Procedures

Id:0900d805800b2a30

Figure 3 Export IDF File

Figure 4 Reminv command

34 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

Figure 5 File menu: Attach command

The following tables show all the nob_RIUs for the BSC/72, BSC/120 HC (High Capacity BSC1):

Functional Address

Functional Address Type

BSC-FRAME-0 F:BSCLBSC-FRAME-1 F:BSCUBSC-RACK R:BSCEARTHQUAKE-0 MK:EQ4FANB FANB

MKCABMP-0 MK:CABMPMKNEWBSC-0 MK:NEWBSCADC-0/0 M:ADCADC-0/1 M:ADCADC-0/2 M:ADCADC-0/3 M:ADCADC-0/4 M:ADCADC-0/5 M:ADCADC-0/6 M:ADC

Table 2 List of nob_RIUs for BSC/72, BSC/120 HC

A50016-G5100-A250-01-7630

35

ITMN:BSC Procedures

Id:0900d805800b2a30

g If the Siemens Customer Service is requested to maintain inventory informa-tion for the customer, the data transfer must be defined in the service con-tract.

File transfer periods (weekly, monthly, ...) data storage (via disk, tapes, internet) or direct Radio Commander access have to be defined.

ADC-0/7 M:ADCADC-0/8 M:ADCADC-0/9 M:ADCADC-0/10 M:ADCADC-0/11 M:ADCADC-0/12 M:ADCADC-0/13 M:ADCADC-0/14 M:ADCADC-0/15 M:ADCADC-0/16 M:ADCADC-0/17 M:ADCADC-0/18 M:ADCADC-0/19 M:ADCPLADS PLADSETHCAB-0 ETHCABETHCAB-1 ETHCABPWRS-0 M:PWRSPWRS-1 M:PWRS

Functional Address

Functional Address Type

Table 2 List of nob_RIUs for BSC/72, BSC/120 HC

36 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

1 Upload the Inventory Data Table (IDT) from the BSC1The user shall enter the "Upload local idf file" command in order to create a local copy of the file on the LMT Evolution. Before upload it is necessary to lock the REMINV object.b Enter the following command:See ........... Figure 4

b Enter the following command:

2 Start IDF Editor EvolutionStart the IDF Editor Evolution from the user Windows startup file menu by clicking the related icon and open the uploaded IDT file by selecting the button Open into the file menu.

3 Cards checkVerify the attribute SalesUniqueName (11 characters ASCII string) and the content of the file uploaded.The SalesUniqueName is the BSC1 identification code and it is stored on the core module (i.e. Disk) of every BSC1.To check the PID information contained into the BSC1 modules, which have On Board Remote Inventory Unit (ob-RIU objects), its necessary to have these modules and the BSC1 in Enabled state.

LMT tree: MANAGED-ELEMENT--> BSS EQUIPMENT--> REMINVCommand: LOCK REMINVName REMINV=

Submit

UPLLIDF REMINV:NAME=

LMT tree: MANAGED-ELEMENT--> BSS EQUIPMENT--> REMINVCommand: UPLLIDF REMINVName REMINV=

Attributes: DESTDIR = FILE ="bsc.idt"OVERWRITE =

Submit

UPLLIDF REMINV:NAME=DESTDIR=,FILE=bsc.idt,OVERWRITE=YES;

A50016-G5100-A250-01-7630

37

ITMN:BSC Procedures

Id:0900d805800b2a30

4 Attach NOB file to actually loaded IDF or IDTb To attach a NOB file to an IDF or IDT file uploaded from BSC1, the IDF Editor Evo-lution provides the following functionality:

The nob_RIU records are shown in bold style. For more details about graphical panels see the OGL:IDF Evolution manual.See ........... Figure 5

5 Remove all redundant nob_RIUsAfter importing IDFs coming from the RLC or after replacing a card originally a nob_RIU with another card, now having inventory data on board, the same nob_RIU would be reported twice. For removing the redudancy the IDF Editor Evolution provides the fol-lowing functionality:

This action can be applied for IDFs with inventory of only one BSC1.It cannot be used for central IDFs. For more details about graphical panels see the OGL:IDF Evolution manual.See ........... Figure 5

6 Modify NOB fileIf it is necessary to modify the NOB file, select the I-Record and open the Edit dialog box by right clicking the mouse (refer to OGL:IDF Evolution manual) and insert the nob data into corresponding field in the opened window.See ........... Figure 2

7 Save and Export NOB fileb When the user has completed the modification of the nob_RIUs inventory data the NOB file shall be saved as follow:

Button: in the file menuInput: Result: The inventory objects of the are

attached IDF or IDT file. The number of attached objects is displayed after command execution.

Button: in the file menuInput:

Button: in the file menuInput:

(default filename is retained from the "SalesUniqueName" field of the IDF)

38 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

A copy of the NOB file is saved in the C:\LMT_root\..\idf\download directory, where it can be accessed only by the LMT Evolution during execution of the "Download nob_RIU" command.The command is only applicable for IDFs with an inventory of one NE. It cannot be applied to central IDFs. The filename is BSCNRIU for the BSC1.See ........... Figure 3

8 Close the IDF Editor EvolutionClose the IDF Editor Evolution and open the LMT Evolution.

9 Download the NOB fileThis step must be executed to transfer the file stored on the local LMT Evolution to the BSC1.b Enter the following command:

See ........... Figure 4

10 Backup and restore inventory dataSince nob_RIU data is also stored in the NE itself and the core module might become defective, a backup of the inventory data is strongly recommended.The data should be stored on a floppy disk and kept together with the side specific doc-umentation and the backup of configuration data at the site.Especially for the Acceptance Test Documentation, an upload of the inventory data during system handover shall be performed.1. Backup: upload the Inventory Data Table to the LMT Evolution, load it into the IDF

Editor Evolution and export in IDF format. Save the file on a floppy.2. Restore: Load the IDF file from the floppy disk into the IDF Editor Evolution; export

in NOB format and download the NOB file to the NE using the LMT Evolution.When there is no local backup copy available, the Central IDF backup of the BSC1 or RC can be used as well.

END

Result: NOB file is saved for further processing

LMT tree: MANAGED-ELEMENT--> BSS EQUIPMENT--> BSCE --> REMINVCommand: DNLIDFD REMINVName: REMINV=

Attributes: SRCDIR =

Submit

DNLIDFD REMINV:NAME=REMINV:,SRCDIR=;

A50016-G5100-A250-01-7630

39

ITMN:BSC Procedures

Id:0900d805800b2a30

3.12 Module State VerificationThe following procedure is to be executed only for those modules that do not require a fully working connection of the BSC1 with other NEs. The procedure consists of launch-ing the GET STAT command on all the configured objects of the following type inside the BSC1 rack: MEMT; MPCC; NTW; TDPC; IXLT; CPEX or ESAM ( for High Speed Gb Interface feature); PPXL.

PrerequisitesIn order to execute the procedure, the "Bring-Up" must have already been completed successfully.

1 Verify the Objects statesThe admitted values are:

2 System ResponseThe LMT Evolution shows the containment tree.

END

Operational State Administrative StateEnabled Unlocked

40 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.13 Module Quantity Expansion for BSC/72 and BSC/120 HCThe BSC1 in the expansion rack is provided without objects configured.On the base rack 3+1 (spare) LICDs can be configured.If it is necessary to increase the number of LICDs or configure PPXU card, the following BSC1 Database configuration procedure must be executed: create the EPWR if equipped (in the S30861-C36/C40-X rack EPWR is not present); create the other LICDs; create the PCUs.

PrerequisitesThe user must know the numbers for LICD/PPxx.

1 Creation of a EPWR (not for S30861-C36/C40-X rack)This procedure creates an EPWR object.Enter the following command:b MANAGED-ELEMENTBSS-EQUIPMENTBSCEEPWRCREATE EPWRCREATE EPWR:NAME=EPWR:;

2 Creation of the spare LICD on the expansion rackThis procedure creates the spare LICD (LICDS-1 object).Enter the following command:b MANAGED-ELEMENTBSS-EQUIPMENTBSCELICDSCREATE LICDSCREATE LICDS:NAME=LICDS:1,LICDTYP=LICDQTLP;

3 Creation of a LICDThis procedure creates a LICD object.Enter the following command:b MANAGED-ELEMENTBSS-EQUIPMENTBSCE

!CAUTION - EEPROM on board

If you add one or more cards without EEPROM on board, the whole file of nob-RIU objects must be modified, by means of the IDF Editor Tool, and then downloaded again by the LMT Evolution (see MMN:BSC - Update of RI file Procedure).

A50016-G5100-A250-01-7630

41

ITMN:BSC Procedures

Id:0900d805800b2a30

LICDCREATE LICDCREATE LICD:NAME=LICD:,LICDTYP=LICDQTLP, ALARMT1=,ALARMT2=,ALARMT3=, ALA-COUNT=;

4 Creation of a PPXUThis procedure creates a PCU object.Enter the following command:b MANAGED-ELEMENTBSS-FUNCTIONALPCUCREATE PCUCREATE PCU:NAME=PCU:,

5 Creation of other PPXURepeat the Creation for all PCUs.

6 System ResponseThis procedure creates and tests additional EPWR, LICD, PPxx modules.

END

42 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.14 Alarm Panel VerificationPrerequisitesThe Data Base completion must have already been performed, whatever is the adopted procedure.g The alarm panel verification must be executed after the completion of the Data

Base.

1 Check LEDsCheck for LEDs on Fuse and Alarm Panel and Lamp Panel:Only the green EQUIPMENT STATUS - COMMUNICATION LEDs must be illuminated but not flashing. None of the other LEDs must be illuminated.

2 ResultsIf one or more of the green EQUIPMENT STATUS - COMMUNICATION LEDs is flashing or one or more than one of the other LEDs are lit, it is necessary to check the condition of the suspected faulty modules by using the MMN:BSC.

END

A50016-G5100-A250-01-7630

43

ITMN:BSC Procedures

Id:0900d805800b2a30

3.15 Module TestPrerequisitesIn order to execute the procedure, the "Bring-Up" and the object creation must have already been completed successfully.

1 Lock the Module (i.e. MPCC module)b Enter the following command:

2 Start the Testb Enter the following command:

It is possible to perform a test on the single module. The LMT Evolution tree is the fol-lowing:

!CAUTION - Module State

Every module, before launching the Test command, must be in LOCKED state.

LMT tree: MANAGED-ELEMENT--> BSS-EQUIPMENT--> BSCE --> MPCCCommand: LOCK MPCCName: MPCC:Submit

LOCK MPCC:NAME=MPCC:;

LMT tree: MANAGED-ELEMENT--> BSS-EQUIPMENT--> BSCECommand: PERFTEST BSCE Name: BSCE:Attributes: MORT = where pathname=DISK, DK40, EPWR, IXLT,

LICD, LICDS, MEMT, MPCC, NTW, PPXL, PPXU, PWRD, TDPCSubmit

Perftest BSCE:NAME=,MORT=;

LMT tree: MANAGED-ELEMENT--> BSS-EQUIPMENT--> BSCE --> module where module=DISK, DK40, EPWR, IXLT, LICD, LICDS, MEMT, MPCC, NTW, PPXL, PPXU, PWRD, TDPC,

Command: PERFTEST module

44 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

g The System output depends on the fact that the test is activated on a faulty (Response 1) or working (Response 2) module.

For more detailed information see the Diagnostic Procedure of the BSC1 Maintenance Manual.

END

Name: module:Submit

Perftest module:NAME=:;

A50016-G5100-A250-01-7630

45

ITMN:BSC Procedures

Id:0900d805800b2a30

3.16 Module SwitchPrerequisitesIn order to execute the procedure, the "Bring-Up" and the object creation must have already been completed successfully.

1 Duplicate ObjectsThis procedure checks the standby status exchange of the duplicate objects from "Pro-viding Service" to "Hot Standby" and vice versa.The duplicate objects are: MEMT; MPCC; NTW; TDPC.

2 Switching of Duplicate ObjectsThis procedure allows for modules switching.Enter the following command:b MANAGED-ELEMENTBSS-EQUIPNENTBSCE

SWITCH SWITCH :NAME=:;g The must be relevant to the active (providing service) copy.

3 System ResponseThe LMT Evolution shows the containment tree.

END

46 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.17 External Alarm Check for C20-X rackPrerequisitesThe Data Base completion must have already been performed successfully.

1 Check of corresponding alarm activation/deactivationFor every couple of external alarms (see IMN:BSC) alternatively open/close the contact and check on the LMT Evolution the corresponding alarm activation/deactivation.All the five external alarms have to be previously created in the BSC1 Configuration menu.

Enter the following command:b MANAGED-ELEMENTBSS-EQUIPMENTBSCEENVACREATE ENVA

Notconfigured

AlarmName

Int. Threshold State OK

ENVA-0ENVA-1

ENVA-2

ENVA-3ENVA-4

It's possible to define only 5 of 16 alarms:.....ENVA-0:NAME=SMOKE,INT=TRUE, THR=2

Ex: Creation of ENVA (0,...,4)ENVA-0:NAME=SMOKEENVA-1:NAME=FIRE

ENVA-2:NAME=HEAT VENT

ENVA-3:NAME=HUMIDITYENVA-4:NAME=TEMPERATURE

In this configuration the alarms are:

SMOKE (MAJOR)FIRE (CRITICAL)HEAT VENT (MAJOR)

A50016-G5100-A250-01-7630

47

ITMN:BSC Procedures

Id:0900d805800b2a30

END

HUMIDITY (MAJOR)TEMPERATURE (MAJOR)

Correspondence between the connector pins and the ENVA:

ENVA-0 PIN 23

ENVA-1 PIN 24

ENVA-2 PIN 25

ENVA-3 PIN 49

ENVA-4 PIN 50

48 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.18 External Alarm Check for BSC/120 HC C36/C40-X rackPrerequisitesThe Data Base completion must have already been performed successfully.In the C36/C40-x rack configuration the CPEX or ESAM alarm card can check sixteen more external alarms then five the other previous C21-x rack.

1 Check of corresponding alarm activation/deactivationFor every couple of external alarms (see IMN:BSC, Cables connection chapters) alter-natively open/close the contact and check the corresponding alarm activation/deactiva-tion via the LMT Evolution.All of the external alarms have to be previously created in the BSC1 Configuration menu.Enter the following command:b MANAGED-ELEMENTBSS-EQUIPMENTBSCE

Notconfigured

AlarmName

Int. Threshold State OK

ENVA-0ENVA-1

ENVA-2

ENVA-3ENVA-4

ENVA-5

ENVA-6ENVA-7

ENVA-8ENVA-9ENVA-10ENVA-11

ENVA-12

ENVA-13ENVA-14

ENVA-15

ENVA-16ENVA-17

ENVA-18ENVA-19ENVA-20

A50016-G5100-A250-01-7630

49

ITMN:BSC Procedures

Id:0900d805800b2a30

ENVACREATE ENVA

It's possible to define 21 external alarms:Ex: Creation of ENVA (0,...,4)

ENVA-0:NAME=SMOKEENVA-1:NAME=FIRE

ENVA-2:NAME=HEAT VENT

ENVA-3:NAME=HUMIDITYENVA-4:NAME=TEMPERATURE

In this configuration the alarms are:

SMOKE (MAJOR)FIRE (CRITICAL)HEAT VENT (MAJOR)HUMIDITY (MAJOR)TEMPERATURE (MAJOR)

N pin Signal ENVA number1 NB-AMB1 (Note 1) ENVA-52 NB-AMB2 (Note 1) ENVA-63 GND4 NB-AMB3 (Note 1) ENVA-75 NB-AMB4 (Note 1) ENVA-86 GND7 NB-AMB5 (Note 1) ENVA-98 NB-AMB6 (Note 1) ENVA-109 not used10 GND11 Alarm door open ENVA-11 (Note 3)12 GND13 NB-AMB9 (Note 1) ENVA-1314 NB-AMB10 (Note 1) ENVA-1415 NB-AMB8 (Note 1) ENVA-12

50 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

16 NB-AMB11 (Note 1) ENVA-1517 NB-AMB12 (Note 1) ENVA-1618 GND19 not used20 GND21 GND22 GND23 MPC-INP4 (Note 2) ENVA-024 MPC-INP5 (Note 2) ENVA-125 MPC-INP6 (Note 2) ENVA-226 NB-AMB13 (Note 1) ENVA-1727 NB-AMB14 (Note 1) ENVA-1828 GND29 NB-AMB15 (Note 1) ENVA-1930 NB-AMB16 (Note 1) ENVA-2031 GND32 not used33 not used34 GND35 GND36 not used37 GND38 not used39 not used40 GND41 not used42 not used43 GND44 NB-AMB7 (Note 1) ENVA-11 (Note 3)45 GND46 not used47 GND48 not used49 MPC-INP7 (Note 2) ENVA-350 MPC-INP8 (Note 2) ENVA-4

N pin Signal ENVA number

A50016-G5100-A250-01-7630

51

ITMN:BSC Procedures

Id:0900d805800b2a30

g Note 1: handled by CPEX or ESAM board.g Note 2: handled by MPCC board.g Note 3: Alarm door open signal is extended to ENV-11 to display it in environmen-

tal alarms.

END

52 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800b2a30

Procedures

3.19 Power On/Off SequenceThe BSC1 Restart Verification must be executed in order to check the behavior of the system in case of a total power failure.

PrerequisitesThe system must be powered on.

1 Power Off the BSC1For the -C20-X rack: press the Red button on each PWRS.For the -C36/C40-X rack: switch-off the breakers in the DCP panel.

2 WaitWait for about one minute.

3 Power On the BSC1For the -C20-X rack: press the Black button on each PWRS.For the -C36/C40-X rack: switch-on the breakers in the DCP panel.

4 System ResponseThe test is to be considered successful if the BSC1 performs the Bring-Up autono-mously.If the BSC1 is not able to activate the Software, the test is unsuccessful.

END

A50016-G5100-A250-01-7630

53

ITMN:BSC Appendix

Id:0900d805800df1ee

4 Appendix

4.1 EPROM FirmwareThe following table provides the relevant information for the firmware installed on EPROMs for BSC1 modules.

!CAUTION - MNEM-modules

Also the older MNEM-modules eventually not supported in this release are listed.

MNEM-module

Module codeNum-ber

EPROM code-Number

Checksum EPROM Locat.

Notes

M:IXLTV6 S30861-Q444-X1for issue 03, 04

V30113-M50-A1 034C2983 U34 DATA I/O load for factory.(OTPROM)

V30113-M50-A2 034BA4B2 U35M:IXLTV7 S30861-Q467-X

for issue 01, 02, A1, 03

V30113-M50-A1 034C2983 U34 DATA I/O load for factory.(OTPROM)

V30113-M50-A2 034BA4B2 U35M:QTLP S30861-Q372-X1

for issue 02440-111/11 00233922 IC43 DATA I/O load for factory

M:QTLPV2 S30861-Q414-X1for issue 02

448-015/01 0723EE2C IC35 Boot + FWBoot file FW file (FLASH EPROM)

for issue 03 448-015/02 0723EE33 IC35 Boot + FWBoot file FW file

for issues: 04, 05 448-015/06 07226A70 IC35 ICT load - PC load by pgmPC2QTLP.EXE

for issues: 06, 07 V7311-P1-R668 0721E7E6 IC35 ICT load - PC load by pgmPC2QTLP.EXE

for issues: F1, 08 V30113-M30-A26 IC35 ICT load - PC load by pgmPC2QTLP.EXE

M:STLPV1 S30861-Q465-Xfor issue 05

V30113-M30-A30 IC33 ICT load for factory

for issue : E1, 06 V30113-M30-A31 IC33 ICT load for factoryIC33 PC load for field by program

pcl2104.exefor issue : E2, 07, E8 V30113-M30-A47 IC33 ICT load for factory

IC33 PC load for field by program pcl3100.exe

Table 3 BSC1 firmware

54 A50016-G5100-A250-01-7630

ITMN:BSC

Id:0900d805800df1ee

Appendix

M:PLLH S30861-Q370-X1for issues: 01, 02, 03

440-53/002 000A12C4 N067 DATA I/O load for factory

S30861-Q370-X101for issues: 01, 02, 03

440-53/002 000A12C4 N067 DATA I/O load for factory

for issue 04 440-53/007 000A15C3 N067M:PLLHV2 S30861-Q370-X201

for issue 02440-25/141 00128866 N067 DATA I/O load for factory

for issue 03, 04 440-25/142 00129B3E N067M:PPXXV2 S30861-Q486-X

for issue 08V30113-M1-A46 196D5E05 U4 ICT load for factory

M:PPXXV1 S30861-Q462-Xfor issue 15, H6

V30113-M30-A35 U4 ICT load for factory and PCload for field by theprogram px210000.exe

for issue 16, H7, 17 V30113-M30-A41 0A1C588D U4 ICT load for factory and PCload for field by theprogram px210000.exe

M:TDPCV9 S30861-Q495-X1 for issue 01

V30113-M30-A43 1DC915C0 D39 ICT load for factory (FLASHEPROM)PC load for field by pgmPC210100.EXE

M:MPCCV9 S30861-Q494-Xfor issue 01

V7311-P1-R667 002FB9D8 D23 ICT load for factory (FLASHEPROM)

V30113-M30-A42 1D52AB4F D59 ICT load for factory (FLASHEPROM)

M:DK40 S30861-U423-X2for issue B5

V7311-P1-R653 00681A00 M025 Mandatory since BR4.0DATA I/O load for factory

V7311-P1-R654 0066B3E6 M018

M:DK40V3 S30861-U719-Xfor issue 01, 02

V7311-P1-R655 01620D00 IC28 Mandatory since BR6.01 DATA I/O load for factory

V7311-P1-R656 01602CF3 IC27M:ESAMV1 S30861-Q480-X

for issue 10V30113-M30-A68 00D99C96 D100 ICT load for factory

MNEM-module

Module codeNum-ber

EPROM code-Number

Checksum EPROM Locat.

Notes

Table 3 BSC1 firmware

ITMN:BSCTable of ContentsList of FiguresList of TablesReason for Update1Introduction1.1Purpose of the Document1.2Precautions1.2.1Access to Electrical Installations1.2.2Handling Modules with Electrostatically Sensitive Components1.2.3Check List1.2.4Required Instruments

2Tasklist2.1Visual Control of BSC12.2Bring-up: the BSC1 Activation Process2.3Data Base Completion2.4Alarm Verification2.5BSC1 Restart Verification

3Procedures3.1Check of Modules and Auxiliary Equipment for High-Capacity (C20-X rack) configurations3.2Check of Modules and Auxiliary Equipment for BSC/72, BSC/120 HC 2nd Step (S30861-C36/C40-X) configuration3.3Check of Modules and Relevant Codes3.4Power Supply3.5Check of the Jumper Settings3.6BSC1 "Bring-Up"3.7MPCC Loading3.8BSC1 Reload3.9Download of a SW load header file on BSC1 disk3.10Check of SW images3.11Inventory Data: Preparation to use Remote Inventory Feature3.12Module State Verification3.13Module Quantity Expansion for BSC/72 and BSC/120 HC3.14Alarm Panel Verification3.15Module Test3.16Module Switch3.17External Alarm Check for C20-X rack3.18External Alarm Check for BSC/120 HC C36/C40-X rack3.19Power On/Off Sequence

4Appendix4.1EPROM Firmware

Documents

bscit