Ericsson Business Phone 50-250 Maintenance Fault Tracing

Transcript

FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible SEA/EBBMP Stangelberger SEA/EBBS Dokansv/Godkänd - Doc respons/Approved SEA/EBBMP 1(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Kontr/Checked Datum/Date Rev Tillhör/Referens-File/Reference 1999-07-15 F ASB 150 02 Database reference 1545.fm ASB 150 02 FAULT TRACING Contents Page 1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.1 Tools for fault locating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.2 References . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 1.3 Replacement of printed board assemblies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 1.4 Definitions . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 2 Fault locating . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.1 General checks on start and completion of service . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 2.2 Indication of LEDs on board(s) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 10 2.3 Flow chart: No possibility to make calls in PBX . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 2.4 Flow chart: Individual board not working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 2.5 Flow chart: Individual does not work at all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17 2.6 Flow chart: Digital trunk does not work at all . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 2.7 Flow chart: Part of individual function not working . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20 2.8 Flow chart: Individual facility does not work . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21 2.9 Flow chart: Individual facility works intermittently . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.10 Flow chart: Individual does not work for certain facilities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2.11 Flow chart: Transmission faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 23 2.12 Flow chart: PBX is unstable . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 24 2.13 Flow Charts for Cordless . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 25 3 Procedures . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.1 Check on telephone . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.2 Check RASC connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 32 3.3 Check CSM connection . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33 3.4 Check on service display DT 288, DT 360, DT 368 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 34 3.5 Check on configuration data for trunks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 (continued) FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 2(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference 3.6 Voltage measurements . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 3.7 Check on power supply . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37 3.8 System reset. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 3.9 Check on line network . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 3.10 Check on programmable parameters for facilities. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 38 3.11 Check on resources . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 3.12 Fault checks / correction of intermittent faults. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 39 3.13 Fault reporting. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3.14 Update of board positions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 3.15 Translation and verification of revision states . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41 4 Resistance of temperature sensor at different temperatures . . . . . . . . . . . . . . . . . . . . . . . . . 42 FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 3(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference General These fault locating instructions shall serve as a guide for servicing an ASB 150 02 telephone exchange (PBX). This document presupposes that all installation and start-of-operation instructions have been adhered to. This document covers only such faults (errors) as equipment malfunctions or some incorrect programming. When beginning start by classifying the fault type (see page 8). Generally, when servicing a PBX a hardware fault can only be remedied by replacing the faulty hardware on site and the faulty unit(s) are to be returned to the supplier with a claim for compensation. No repairs are to be done in the field. The PBX has operation and maintenance programs installed which can be accessed via the PC-program RASC and Cordless System Manager software (CSM). These programs run on a PC that can be situated either in a remote service centre or locally next to the PBX. The service personnel shall be familiar with the system, in particular regarding RASC and CSM with their possibilities, as RASC and CSM are the best fault locating aids. 1.1 Tools for fault locating Fault locating from an operation and maintenance (O&M) centre requires a PC with RASC and CSM installed and a Hayes-compatible V.32bis modem. Fault locating on site requires a (portable) PC with RASC and a V.24-cable connected to a free V.24port. Additionally required tools are: a voltmeter (DVM), a system telephone, board extractor and a set of screwdrivers. As the boards are sensitive to electrostatic discharges please use a grounding wrist strap correctly connected to ground when handling the boards. The Cordless System Manager software contains functions for Cordless System part regarding initialization, system maintenance and updating, system fault finding and repair. As RASC cannot detect IC-LU boards installed in the system it is advisable to locate these boards to the right of the IC-CU_ board. The Cordless System Statistics is an extension to the Cordless System Manager. It collects and interprets statistical information from the Cordless System. It gives an overview of the traffic load of the total Cordless System, load per Base Station or per portable telephone. Important data of telephone calls are stored, for example the duration of calls, the number of hand over and errors like failed calls or portable telephones that could not be reached. The Cordless System Manager software has a menu driven user interface. Separate text files permit you to translate and obtain the menus in the desired language. 1.2 References 1 B/XU 93:027 Uen. SAR-routine for Fault reporting and fault handling 2 EN/LZB BS 103 1197 RASC 3 LZY NB 201 01 /n Cordless System Manager Software 4 Service advice: Status of R-states FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 4(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.3 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Replacement of printed board assemblies Before handling printed board assemblies (PBAs) service personnel shall always connect themselves to ground to prevent damage caused by static discharges. Boards with Electrostatic Sensitive Devices (ESD) are marked with a sign. In the interest of quality and reliability of the system boards, always handle static sensitive boards with special care. Always use a wrist strap connected to a low resistance ground e.g. provided on the cabinet. Some of the benefits of ESD protection are: -less failures/service calls -lower maintenance costs -higher customer satisfaction Use portable equipment LYA 30101 as a protection against electrostatic discharges. Older system versions of the PBX must be restarted (e.g. switched OFF and ON) after the replacement has taken place. As of BP 50/250 Version 3.1 (ASB15002 R10) boards can be replaced during power on. The board can be exchanged during operation by a board with the same type and number of individuals. Prior to removing the board, it can be disabled for traffic (by RASC) and the new board is put in operation without the need of restarting the exchange. A new board can be inserted in a free slot and put in operation. When replacing boards be careful when inserting the board in the cabinet as not to damage the backplane connector (e.g. bending pins due to misalignment) or to cause a short circuit on the layer side of neighbouring boards e.g. by elevated components such as transformers, capacitors. Note that the PBX will generate warnings to this effect and is therefore advisable to read the relevant warning log. Also bear in mind that restarts normally generate the alarm and if automatic alarm transmission is active, alarms will be generated to the relevant alarm centre. This can be avoided by re-classifying the restart codes or by deactivating the alarm transmission. The changes done to avoid alarms from being issued while servicing shall be reset after final restart has been effected and the system handed over to the customer. The procedure for replacement of boards is described below: 1 Transfer the (if any) warning log to a file in RASC if possible for later evaluation and appropriate measures. Make a printout of the warning log. 2 Deactivate active alarm. 3 Save configuration data on file in RASC if possible when CPU-D is to be replaced or with the aid of the Cordless System Manager if the failure concerns the IC-CU_ or IC-LU. 4 Connect portable equipment LYA 30101 to protect against static electricity. 5 Replace faulty PBA. 6 Restart PBX manually (switch power off and on) or via RASC. If the PBX comprises several cabinets the cabinet containing the CPU-D_ shall be switched ON as last. 7 Empty the warning log. 8 Reset active alarm if this is required. 9 When replacing the CPU-D_ perform a cold-start in the PBX and update it with the saved configuration data from RASC in order to restart all programmable data. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 5(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.4 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Definitions Blocked Printed Board Assembly (PBA) A blocked PBA is normally unable to process traffic. The state of the board is indicated on the board's LEDs (see under section " Indication of LEDs on board(s)" on page 10) and read outs of revision (R)states is made via RASC where the board position is indicated (marked). See user guide for RASC-menu Maintenance-HW/SW-RP. Blocked directory number An individual whose directory number has been blocked cannot generate nor receive traffic. A blocked directory is not indicated on the LEDs of the device board. See RASC-menu CONFIGURATION. Cold start Cold start denotes a restart of the PBX, whereby all programmed data is erased and replaced by default values initially assigned e.g. factory). Cold start is performed by placing a strap in the socket provided for this purpose on the front of CPU-D_ (see under section " Indication of LEDs on board(s)" on page 10) and thereafter switching off and on the DC supply voltage to the cabinet containing CPU-D_. Instead of switching the PBX OFF and ON again two pins are available in connector field 2 on the CPU-D_ which can be short circuited by a plug to invoke restart (refer to section 4.8). CSM The Cordless System Manager is a maintenance and configuration software program for the Integrated Cordless System. A PC with CSM software installed can connect directly to a CPU-D4 on a maintenance port or remotely via internal modem (similar as with RASC) but as in the past it is also possible to connect CSM directly to the IC-CU_ or via an external modem. CPU The central processor unit and its programs. Device The PBX can be considered as an interworking unit of function blocks. Such a function block is sometimes called a "device". Examples of devices are: switch, tone sender, extension, trunk, MFC-register and voice memory. The placing of the devices on PBAs is arbitrary. Facility The functions of a telephone exchange are called facilities. Often a facility consists of several connection cases. A connection case is initiated by means of a certain procedure from a telephone or other unit (equipment) connected to the exchange. Examples of facilities are: internal call, external call, inquiry, transfer, intrusion, conference, sector paging, various types of diversion, programming of function keys and abbreviated numbers. Hot swapping A board of the PBX can be exchanged during operation by a board of the same type and with the same number of individuals. The board can be disabled for traffic (by RASC) prior unplugging it and the new board is put in operation without the need of restarting the exchange. A new board can be inserted in a free slot and put in operation. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 6(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Individual An individual member (unit) of a group. The PBX possesses, among others, groups of extensions where an individual can connect a telephone. On analogue trunks each individual can connect (is connected) to a trunk. On digital trunks several individuals share a single line (cable/interface). Installed PBA A PBA is correctly installed if it is physically mounted in a board position stipulated in the appropriate installation instructions. A correctly installed PBA is a prerequisite for traffic. See the guide text for RASC-menu MAINTENANCE-HW/SP-RP. The LEDs on the board identify different board conditions. An explanation of the conditions is given under FAULT LOCATING. Line network with stubs: Extension line with extra jacks in the form of a star network. See figure below. PBX Note: This configuration must never be used for digital telephone extension lines connected to boards like ELU-D and ELU-C. Although with appropriate termination this is a valid configuration for the ISDN S-interface connected to the BTU-B. Line signalling diagram with line test Several line signalling diagrams for trunks include a line test that is done for both outgoing and incoming calls. These tests are described in RASC, RASC-menu CONFIGURATION-TRUNKS. Link supervision Digital trunks are supervised by the exchange and the state conditions, errors on the digital link to the public exchange are monitored. The monitoring data can be read out via RASC-menu maintenance-system-link supervisor and stored in a file or printed out. Minimum system size A minimum system comprises one cabinet equipped a CPU-D_ and either one ELU-D, ELU-C or ELUA. Power supply Transformers, battery chargers, batteries and appurtenant cables are all included in the concept "Power supply". Programmable parameters The PBX possesses a considerable number of programmable parameters, which help O&M-personnel to adapt the function of the PBX to customer requirements. The majority of facilities and individuals can be programmed. See RASC-menu CONFIGURATION and the Cordless System Manager Software. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 7(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Recommended measure Each warning code is described in RASC and recommended measures are offered. See item Warning below. Remote SW upgrading The system software can be downloaded from a remote maintenance centre. Setting a certain time and date automatically loads the new software into the system non volatile memory and re-starts the exchange. RP (Regional Processor) The control system of the PBX is handled by a central processor and a number of regional processors. A typical task for an RP is to handle the hardware check on the individuals on a PBA. Update board position The database contains, among other things, relevant data for all board (PBA) positions in the PBX. The database contains also details about the type of PBA that should be installed. The update means that the database is adapted to physical reality. An update is required in conjunction with a configuration change of the PBX, e.g. on expansion with new PBAs, on removal of PBAs and when a PBA is replaced by a different type of PBA. See RASC-menu Maintenance-HW/SW-RP. Warm start Restart of a PBX with no cold start strap installed. This is the normal procedure in conjunction with power-up or controlled restart via RASC-menu Maintenance-log-reset. All programmed data is retained. Warning The control system of the PBX is structured so that warnings are generated when abnormal situations occur. The warnings can be read out by O&M-personnel and also personnel who have access to the control system's source code. Warnings that are directed to O&M-personnel are complemented with a recommended measure. Warnings without recommended measures shall be interpreted by persons with access to the control system's source code. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 8(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F 2 Fault locating 2.1 General checks on start and completion of service Tillhör/Referens-File/Reference Start by identifying the type of fault by collecting as much information about the fault as possible, from the relevant customer, then (if possible) connect RASC and check the configuration of the PBX with regard to revision states (see point 4.15, Translation and verification of revision states) as soon as this is possible. The majority of faults can probably be eliminated from the O&M-centre by means of reprogramming or via telephone contact with the respective customer (operational faults). Consider to which one of the following main fault categories best describes your fault: Number TYPE OF FAULT Go to: 2.2 Indication of LEDs on board(s) page 10 2.3 No call procedures possible in the PBX page 15 2.4 Individual board not working page 16 2.5 A single individual does not work at all, e.g. an extension is "dead". The individual is not able to either initiate or receive calls page 17 2.6 Digital trunk (BTU-D) does not work at all page 19 2.7 Individual malfunctions partly, intermittent faults, e.g. one connection case is successful and another fails. The fault can be traced to an individual page 20 2.8 A certain facility never functions. A certain facility is inaccessible, e.g. intrusion is never possible page 21 2.9 A certain facility functions intermittently, that is a certain connection case succeeds on one page 22 occasion, not on another, and where the fault cannot be traced to an individual 2.10 An individual has no access to a certain facility page 22 2.11 Transmission fault (one way speech, line scratching, etc.) page 23 2.12 PBX unstable (repeated restarts) page 24 2.13 Faults related to Cordless page 25 Use the following flow charts describing a methodical path for checks and tests to help locate and eliminate the fault. When the flow charts lead to a possible cause, this is indicated by a statement giving the name of the defective part or the cause of the problem, e.g. a defective BTU-_ board is indicated by the statement `BTU-_ board defect'. When there are more possible items, they are listed in order of decreasing probability. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 9(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Description of flow chart symbols Question 1 4 Question? 2 This symbol contains a question with two or three possible answers being YES (Y), NO (N) or text. Inputs are points 1 or 4 and outputs are points 2,3 or 4. 3 Instruction This symbol contains an instruction for the maintenance engineer. References This symbol is used as: starting point for a procedure (e.g. START), as a reference to another flowchart, to end a procedure (END). This symbol is used as a reference point within a flowchart. This can be to a part of the flowchart on another page (e.g. B or C) or at a part of the flowchart on the same page (e.g.1). Flow Lines indicate the normal flow. The normal flow is always "down" and "to the right" and in exceptional cases "to the left". Arrows are used to indicate flows going "up" or left. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 10(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.2 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Indication of LEDs on board(s) The front edge of all PBAs in the PBX are equipped with LEDs of different colours. Their purpose and signalling cadence is described in the following. On system restart all LEDs are ON and go OFF during start-up sequence. Depending on their function the LEDs are in different positions on the front edge. CPU-D_ LEDs controlled by relevant RP Connection field 2 LEDs controlled by CP Connection field 4 Position for cold start strap on CPU-D Position for cold start strap on CPU-D_ Connection field 6 RPs on BTU-_,ELU-_, IC-CU etc. Red LED lights up during power on sequence Go to: a . Check if PROMS are placed and if no yellow and green LEDs 1st pair (generally RP) flashes. For LED flashing procedures during upgrading refer to MAINTENANCE 2nd pair (e.g. DSPs INSTRUCTION (1541-ASB 150 02). on BTU-D or REG) Yellow and green LEDs indicating start, faults or active ports. During remote upgrading the number of flashes indicate which FLASH program memory is being re-written go to page 11 For LED flashing procedures during upgrading refer to MAINTENANCE INSTRUCTION (1541-ASB 150 02). For LEDs on Integrated Cordless boards go to page 11 Red LED is lit if CP is restarted Go to: c The LED can be ON for up to 2 min. during upgrading or only 1 to 5 seconds during start-up conditions. Yellow Yellow LED LED flashes flashesinindifferent differentcadences caduring sequence and is and off is during dencesstart during start sequence normal operation to page 11. off during normal go operating. Green LED that is directly connected to alarm log e.g.if warnings occur these warning codes are stored in the warning log and this LED is turned on go to page 11. Red LED is ON if cold start strap (located below) is inserted go to page 11. 3rd pair 4th pair Not mounted on all boards FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 11(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.2.1 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference LEDs on the CPU-D LED red Correction LEDs in This can occur if the CP on the CPU is restarted or a board failure is connection detected by the RP. Check if it concerns just one or more board(s). A field 2 watchdog reset on the board could cause a board restart. System supervision will invoke a system restart if major faults occur. If LED is continuously ON check if the yellow and green LEDs flash otherwise the RP is not working yellow This LED indicates This condition is normal for a start-up sequence indicating initialisation or board start-up or if the running self test. If this LED is ON during operation, this indicates blocking board (individual) is of one or more individual(s). The proper action is to check the wiring and if the connected equipment is operational (check it’s alarm indication) blocked. green Port is active This indicates normal system operation and one port is active e.g. RASC LEDs in red CP is reset This occurs during remote upgrading of the SW or if the watchdog detects connection a fault. If LED is continuously on the FLASH PROMS could be re-written field 4 (refer to RP LED conditions) yellow Flashes during start- This LED flashes during start-up of the CP and is OFF during normal up of CP operation green Alarm log indication If this LED is ON, check the logged errors, save them to disk and delete them in the log. Check in which intervals the system logs errors and if possible correct the cause LEDs in red Cold start strap active This LED turns on if the cold start strap below is inserted. This is a warning connection that if this strap is not removed during operation the system will start with field 6 initial values on restart. This occurs even if the mains fails intermittently! All customer data will be lost in this case. 2.2.2 Condition RP disconnects PCM bus and signalling interface from back plane LEDs on the IC-CU, IC-LU LED yellow red ON OFF OFF OFF OFF ON ON ON ON OFF ON OFF ON red red Correction green ON Flash (4 Hz) 0,5s ON/4,5s OFF 0,5s ON/0,5s OFF/ 0,5s ON/3,5s OFF 0,5s ON/0,5s OFF/ 0,5s ON/0,5s OFF/ 0,5s ON/2,5s OFF 1s ON/1s OFF SPU LED on (see Installation Instruction for details) CLU LED on (see Installation Instruction for details) Communication to CPU-D_ terminated. Board failure is detected by the RP. PROM error (invalid checksum) RAM error FPGAs not loaded EPIC initialization fault Initialization fault of process data Invalid FECU connected This LED flashes if the board’s SPU RP detects a fault. To correct the fault check entries in the CSM and follow suitable solution given. Flashing -> CPU fail, ON steady -> warning entries not read. This LED is turned on if the board’s CLU RP detects a fault and/or if a base station is not initialized. Correct the fault, check entries in the CSM and follow suitable solution given. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 12(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.2.3 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference LEDs on other Boards LED red Condition RP disconnects PCM bus and signalling interface from back plane Correction LEDs in This can occur if the CP on the CPU is restarted or a board failure is connection detected by the RP. Check if it concerns just one or more board(s). A field 2 watchdog reset on the board could cause a board restart. System (upper supervision will invoke a system restart if major faults occur. If LED is part) continuously ON check if the yellow and green LEDs flash, otherwise the RP is not working. yellow This LED indicates if This condition is normal for a start-up sequence indicating initialisation the board is in start-up or running self test. If this LED is ON during operation, this indicates blocking of one or more individual(s). The proper action is to check the procedure or if the wiring and if the connected equipment is operational (check it’s alarm board (individual) is indication). blocked. green Individual is active This indicates normal system operation and at least one e.g. extension (individual) is active on the board. LEDs in yellow Register is blocked This indicates that the register function on the board is blocked e.g. on connection BTU-D or VMU-HD. field 2 (lower part) green Register is active This indicates normal system operation. This register function is active on the board e.g. on BTU-D or VMU-HD. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 13(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.2.4 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference LED description during start-up Normal start sequence 1 (power up) Start LEDs sequence Yellow Green aborted ON State Function OFF RESTART Lights up immediately for about 20 seconds FAULT ON ON FAULT ON FAULT R-FL1) R-FL1) PROM-fault Start up is interrupted if a fault is discovered during self test. RAM-fault R-FL1) HD-fault Hard disk is missing/not installed FAULT A-FL3) A-FL3) DSP-fault VMU-HD only: DSP not loaded 2 S-FL2) OFF WAIT Entered after restart following fault-free self test and relevant RP is initiated. Waits for start order from CPU. 3 R-FL1) OFF START Entered in state wait for receipt of start order from CU. RP reports data to CPU, e.g. type of board R-FL1) OFF Data base- Condition in case of database mismatch fault ON OFF BLOCKED Occurs when database does not match with reported data from RP or if at least one individual is blocked4) OFF OFF NORMAL Normal idle state that is entered after PBX has been started. No traffic exists on relevant board/device OFF ON TRAFFIC Traffic on least one individual 4 (operation) 1) 2) 3) 4) Rapid Flash (Frequency=4Hz). Slow Flash (100 ms ON and 900 ms OFF). Alternate Rapid Flash (Frequency=4Hz). Green and yellow LEDs toggle. Applies only for analogue and digital trunks. Individually blocked trunks are indicated in configuration data and not in RASC-menu Maintenance-HW/SW-RP. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 14(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F LEDs on BTU-D LED Prom test OK (1 sec) Prom test ERROR Load DSP MFC Load DSP MFE (20 sec) (20 sec) RP-YELLOW OFF OFF ON ON RP-GREEN OFF ON OFF OFF DSP-YELLOW OFF OFF ON ON DSP-GREEN OFF ON OFF ON AFTER DSP LOAD = “OK” LED RPOFF RPSTARTUP RP-YELLOW FL-OFF FL-STARTUP RP-GREEN OFF DSP-YELLOW FL-OFF DSP-GREEN OFF OFF FL-STARTUP OFF RPNORMAL OFF OFF OFF OFF AFTER DSP LOAD = “ERROR” LED RPOFF RPSTARTUP RP-YELLOW FL-OFF FL-STARTUP RP-GREEN DSP-YELLOW DSP-GREEN OFF OFF FL-OFF FL-OFF FL-OFF FL-OFF RPNORMAL OFF OFF FL-OFF FL-OFF FLASH TIMES: FL-OFF FL-STARTUP = ON 100 msec / OFF 900 msec flash = 4 Hz flash Tillhör/Referens-File/Reference FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 15(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.3 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Flow chart: No possibility to make calls in PBX START Remove front cover on cabinet containing the CPU-D. Y All LEDs extinguished? N Insert cold start strap and remove it immediately. Does the red LED (above cold start strap) light indicating a cold start and extinguishes when strap is removed. Correct? Y N Verify that the exchange is supplied with power. Check 48VDC/36VAC supply, the cabling and if the voltages are present on the backplane. (see point 4.7). Connect to RASC. Verify proper communication parameters Check all revision states (see point 4.15). Connection Y successful? Power ok? Y Valid revision states? N N 1 N Remove board after board in cabinet and measure voltages on the backplane. Replace board causing the wrong voltage(s). If the boards are not the cause replace the back plane. Y Update to latest revision state. Configure mini-PBX comprising one cabinet and CPU-D. Connect RASC. Correct? Fault remains? N Y Check available (free) resources (see point 4.11). Y 1 Resources available? Y 1 N Restart PBX AA AA N Replace CPU-D and restart PBX. Continue by increasing size of PBX with one device board at a time. Replace boards that malfunction. Fault remains? N AA AA = Go to " Completion of service" on page 31 AA AA Y 1 FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 16(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.4 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Flow chart: Individual board not working START Connect RASC and read hardware revision states (see point 4.15). Messages logged from faulty board? N Y Translate message to revision state of board? Remove board and verify that all ICs (EPROMS) are properly mounted on their holders, i.e. no bent legs giving poor contact. Mounted correctly? Y Revision state ok? Y Board blocked? see point 1.4)? N Y Board installed? see point 1.4)? Y N N Swap board and restart PBX. Send the board for swap repair and include fault report Replace board (see point 1.3). AA N Correct mounting fault and reinsert board Restart PBX Y Board starts? (see point 3.1) N Board blocked? (see point 1.4) N AA AA = Go to " Completion of service" on page 31 Y Update board position (see point 4.14). FAULT TRACING DESCRIPTION Uppgjord/Prepared 17(42) Dokumentnr/Documentnr Faktaansvarig - Subject responsible 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.5 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Flow chart: Individual does not work at all START Locate faulty individual and connect RASC Y Extension? N Check MDF and cabling for breaks. (see point 4.9) Cable breaks? Y Telephone functions at another line position? Correct line running Fault remains? Y N N N Check, repair or replace telephone (see point 4.1) AA AA Replace board. 2 Y Intermittent fault? Trunk? Y Y Y N N Analog/digital? Fault remains? N analog Report fault (see point 4.13) digital AE Go to page 14 Warning code in warning log related to fault? Line signalling Y diagram agrees with line test? N N Check with anaolg test equipment in MDF for dial tone from public exchange Y AA Check MDF and cabling (see point 4.9) Correct? 2 Y N Y Fault in public exchange. Report fault to relevant instance. Dial tone? Y Another type? AF N Go to page 13 Fault in public exchange. Report fault to relevant instance. Correct line running Fault remains? AA Y N AA AA = Go to " Completion of service" on page 31 Report fault (see point 4.13) AA FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 18(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved AF Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference From page 12 Proceed in identifying the faulty individual Y V.24 Is there an entry due to the fault? Connect RASC and check warning log. N Y Follow recommended measure. N Y Fault remains? Temperature sensor Y Measurement Y value agrees with table (see point 5)? Disconnect temperature sensor and measure resistance of sensor. N Music source N N Y Check cabling (see point 4.9) Correct? Replace temperature sensor. Y Check cabling (see point 4.9) use data tester. Correct? AA N Y N N Correct cabling AA Other type Y Has the PBX been reY started after programming? If not then restart. Fault remains? N Replace board (see point 1.3). Fault remains? Y N AA Report fault (see point 4.13) AA AA = Go to " Completion of service" on page 31 FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 19(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.6 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Flow chart: Digital trunk does not work at all AE From page 12 Did this board work before? Connect to RASC. 1 Y N Is the hardware setup ok? Correct jumper settings and/or firmware? Y N Correct hardware setups Check in RASC the link supervision if synchronisation is possible. Warnings logged for the card functions? Y N Y Did this board work before? Y Swap board. Does it function correctly? Send to swap repair with fault report N N 1 Is the network/line signalling selection link correct? N Change selection Y Is the ISDN termination selection correct? N Change termination Y Are the services used in the PBX subscribed correctly? N Correct programming Y Are the services used in the PBX subscribed correctly? Y N If possible collect the signalling trace and forward it with the fault report. (see point 4.13) AA AA = Go to " Completion of service" on page 31 FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 20(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.7 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Flow chart: Part of individual function not working START Connect to RASC and read warning log. Warnings logged resulting from the fault? Y Follow recommended measure (see point 4.12). N Verify which individual causes the fault Y Digital extension? Verify proper wiring (twisted pair) with no stubs (extra jack). Correct? Y Correct wiring. Disconnect stubs from old net. N N Y Trunk? Verify Y configuration data for trunks (see point 4.5) Correct? N Replace board (see point 4.13) N Correct programming Other type? Y Check line running (see point 4.9) Fault remains? N Y Correct wiring. Disconnect stubs from old net. Fault eliminated? (see point 4.12) N Report fault (see point 4.13) AA = Go to " Completion of service" on page 31 AA Y FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 21(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.8 Kontr/Checked Datum/Date Rev 1999-07-15 F Flow chart: Individual facility does not work START Connect to RASC. Y Has this facility ever worked before? Warnings logged resulting from the fault? N N Check all parameters that influence the facility (see point 4.10) Y Follow recommended measure. Fault remains? Y N AA Y Correct? N Correct programming. Fault remains? Y Report fault (see point 4.13) N AA AA AA = Go to " Completion of service" on page 31 Tillhör/Referens-File/Reference FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 22(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.9 Kontr/Checked Datum/Date Rev 1999-07-15 F Flow chart: Individual facility works intermittently START Connect to RASC. Warnings logged resulting from the fault? Y N Follow recommended measure. Fault remains? Y N AA Fault is a capacity problem. No. of trunks,VMUboards etc.? Y Expand capacity if possible N Try to reproduce the procedure resulting in the fault and note the conditions when it occurs Report fault (see point 4.13) AA 2.10 Flow chart: Individual does not work for certain facilities START Connect to RASC. Warnings logged resulting from the fault? Y N Check all programmable parameters (see point 4.10) Correct? Follow recommended measure. Fault remains? Y N AA Y N Correct relevant parameters. Fault remains? Y Report fault (see point 4.13) N AA AA = Go to " Completion of service" on page 31 Tillhör/Referens-File/Reference FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 23(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.11 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Flow chart: Transmission faults START Levels too high or low? Acoustic oscillation? (self-sustained) Installed transmission parameters correct? Y N Y N Y Excessive echo on trunk lines? Use RASC to set ATIA to ON for analog trunk. Fault remains? N Is the correct session loaded? Problem solved? Y AA N Y N AA Disturbances? One-way speech? Y N Fault due to an individual e.g. in trunk or extension? Y Replace board, alternatively telephone. Fault remains? N Y N N External disturbances suspected? Y Test using temporary line running Fault remains? Y N Run new line network. No transmission? Y Build mini-PBX comprising one CPU-D and one ELU-D. Is a transmission obtainable? Y Expand PBX in stages. Use exclusion method to replace faulty device (board, back plane, flat ribbon cable, etc.) AA N AA = Go to " Completion of service" on page 31 Report fault (see point 4.13) AA FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 24(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.12 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Flow chart: PBX is unstable START Y Continous restarts? N Restarts once or twice a day or less? Restarts before going into operation (yellow and green LEDs on) ? Y Remove boards Y one by one. PBX goes into operation? N N Y Determine under which conditions restarts occur and select a time when these do not occur to avoid restart during service. Connect to RASC Y N AA N Verify all board revision states (see point 4.15) Valid revision states? Replace faulty board Fault remains? Build mini-PBX comprising one cabinet N and one CPU-D. Connect RASC.Connection successful? Y Y N Update to latest revision state. Fault remains? N Y AA Read Y warning log. Are warnings logged relating to the fault? Y Follow measures recommended in RASC. Fault remains? N AA Report fault (see point 4.13) AA = Go to " Completion of service" on page 31 AA FAULT TRACING DESCRIPTION Uppgjord/Prepared 25(42) Dokumentnr/Documentnr Faktaansvarig - Subject responsible 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 2.13 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Flow Charts for Cordless START Y General Alarm active? N From page 20 General Alarm Y Common user complaint? Common User complaint Go to page 22 Individual User complaint Go to page 23 N Individual user complaint? Y N CSM Problem System managerControl - Service Go to page 26 Y Fault 8 or 37? Check availability of indicated Base Station in System ManagerControl-System N Y Base Station available? Connection between the indicated IC-CU, IC-LU and BS has been broken for a short time N Check supply voltage at Base Station Y Fault 35? Check availability of indicated DTU board in System Manager Control-System Voltage <1/2 x PSU voltage? Y N N BC, L1 and L2 of DTU available? - Check IC-CU, IC-LU connector if voltage present - Check cable to Base Station, MDF Y Restart PBX - Check IC-CU, IC-LU Connection between the indicated DTU part and the PBX has been broken for a short time Base Station powered by an adapter? Y N - Check Base Station - Check BS wiring adapter FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 26(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Common User complaint All portables out of range? Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference From page 25 Y - Check if power is available in the system refer to General checks on start and completion of service on page 8 Y - Poor coverage of an area due to lack of Base Stations or a malfunctioning Base Station. A malfunctioning Base Station can be detected by: N Complaints come from same area? - testing the Base Station with the portable in the Service Display Mode or - checking the load of the Base Stations by System manager Statistics - Display - Station - Station load or - checking the working of the Base Station by System manager Statistics - Settings - View on line N Blocking calls? Y -Lack of resources in BS or SPUs (on IC-CU, IC-LU) When going off-hook with the portable the hook symbol is displayed, if the connection is not stable the portable automatically goes on-hook. N -Time settings lost on IC-CU DIP switch (pos. 119) on IC-CU should be set to ON otherwise the system clock can deviate substantially, which may cause the 24 hour test on the DCT system to run during daytime. Individual User complaint FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 27(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Individual User complaint Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference From page 26 N Portable display remains blank? Y Connect Basic Charger Display turns on ? Y - Portable not within coverage area Portable notinitialized for the system Portable defective System out of order, see "Common user complaint" Battery is low (Battery icon flashes). Leave charger connected until battery is charged (icon is stable) N "Battery Low" displayed ? Y Connect charger to charge battery N Y "PhoneBook empty" displayed ? No names stored in the fixed, nor in the personal phone book. ’CallName’ menue is not active. N "MemoryFull" displayed ? Y Personal phone book memory is full. A name has to be deleted first before adding a new one. N "ConnectBattery" displayed? Y Battery not properly fitted or defect. Message appears only if charger is connected N ".....Error" displayed ? Y NO DIAL TONE DT 310, DT 360, DT 368 N ERRORS - Portable defect N N "No System" displayed ? Y Go to page 28 To page 29 FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 28(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference 1) For all faults corrective action is given. If after correction a fault re-appears, the portable should be sent for repair. From page 27 ERRORS 1) N System List Error Y Initialization data missing or corrupted. Reinitialize portable Y Ringing cadence data missing or corrupted. Reinitialize portable Y Fixed phone book data missing or corrupted. If phone book was loaded, all data is lost, Re-download phone book N Buzzer Data Error N Fixed Phone book Error N Y User Data Error User data corrupted. All data (preferences) will be replaced with defaults, short numbers will be cleared. This fault occurs only once: after cycling the power the fault disappears, because defaults are set. N Initialization Error Y Error occurred during initialization process. Restart initialization N AA AA = Go to " Completion of service" on page 31 FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 29(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked NO DIAL TONE DT 288, DT 310, DT 360,DT368 Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference From page 27 Go off - hook Call icon visible? (flashing or stable) N Reset portable by removing and reconnecting its battery Switch on and go off - hook Call icon visible now ? Y Portable okay now dial tone will be heard N Y Portable defect AA Turns off after some flashes Call icon ? No speech channels available in IC-CU, IC-LU or Base Stations. Try again later or in another location. If problem persists portable is defect. Stable Portable programmed for an IC-CU? N N Program portable General Alarm? Y BC Y General Alarm Go to page 31 AA = Go to " Completion of service" on page 31 Check that associated extension number is registered in PABX and not blocked. Otherwise portable is defect. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 30(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Rev 1999-07-15 F Y Check PC cabling: from COM1 via connection board to IC-CU N Cabling correct ? N ’No connection with portable in desk charger message? Tillhör/Referens-File/Reference From page 25 CSM Problem message ’No connection with DCT1800’ on PC screen? Datum/Date Correct cabling Y - COM1 port of PC - IC- CU board - Serial PC cable N Y Check desk charger/ programmer cable ’Init’ on portable displayed ? N N Replace cable Cable correct? Y Replace desk charger/ programmer ’No connection with portable in desk charger message? N Replace adapter or connect properly Y Y COM2 port of PC Portable makes proper contact with charger pins? Y N END N Y Portable defect Y Adapter correct and properly connected? ’Init’ is displayed when programming another portable? Portable defect N Try to correct contacts or replace desk charger Desk Charger/ Programmer defect FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 31(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference From page 29 BC N Dial tone present? - Error in PBX - extension number blocked or not registered Y Delete old portable from system and initialize new portable with same PUN Press the hook key on the new portable N Dial tone present? - replace relevant IC-CU, IC-LU board - re-initialize old portable with original PUN. Y Old portable defect replace it AA AA AA = Go to Completion of service below Completion of service On completion of service disconnect RASC and check the warning log for entries. If this is the case adopt the recommended measure(s). If no further measures can be taken note the logs (or printout if possible) and contact your local support facility. Remaining faults are to be reported (see point 4.9, “Fault reporting”.) If you cannot fix the problem at the moment start up the exchange again and give the customer instructions how to cope with malfunctions, conclude by making a printout of the warning log and resetting it. Disconnect RASC and place the cover on the exchange. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 32(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked 3 Procedures 3.1 Check on telephone Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference The digital system telephones have a built-in self test facility that can be initiated by pressing three keys simultaneously for three seconds. Self test can only be initiated in idle state. Initiate self test and verify that the telephone functions properly. If not replace the telephone. Telephone type Keys for initiation of self test Result of self test ok DBC 199 R-button, * and 4 LED glows steadily DBC 201 C,*,4 for one second All LEDs light up DBC 202 C,*,4 for one second ’Self test ok’ on display DBC 203 C,*,4 for one second ’Self test ok’ on display DBC 211 C,*,4 for one second All LEDs light up DBC 212 C,*,4 for one second ’Self test ok’ on display DBC 213 C,*,4 for one second ’Self test ok’ on display DBC 214 C,*,4 for one second ’Self test ok’ on display DBC 601 Transfer, * and 4 No LEDs shall flash DBC 632 Transfer, * and 4 ’Self test ok’ on display DBC 662 Transfer, * and 4 ’Self test ok’ on display DBC 663 Bypass, * and 4 ’Self test ok’ on display If there is a voice communication problem also check the connection of the telephone handset to the telephone and test using another handset if the original handset is suspected to be faulty. 3.2 Check RASC connection When encountering communication failures to RASC verify proper settings for the V.24-port and the programmable parameters for the built-in modem and corresponding parameters for RASC on the PC. For more information consult document EN/LZB BS 103 1197 RASC Uen, "RASC". FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 33(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 3.3 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Check CSM connection The Cordless System Manager software installed on a PC requires a connection to the maintenance port on the Cordless System Central Unit (IC-CU_) or to the CPU-D4, either to the maintenance port or via modem. Off-line menus include functions that do not require this connection. Go to the directory in which the Cordless System software has been installed. In most cases, you can start the Cordless System software by just typing DCT . Typing DCT /B. Example: DCT /B9600. This option allows you to change the bit rate with the Desk Charger/Programmer. This may be useful when you want to down-load software to portables with a higher (non-default) bit rate. Valid bit rates are: 4800 (default), 9600, 19200 and 38400. Consult your PC documentation to check which bit rates are supported for the COM2 port. When the program has correctly started-up the welcome menu is displayed. If there is no communication with the Cordless System the message ’No connection with DCT1800. Start Off-line program? Y (Yes/No)’ is displayed. By pressing the key the Off-line program is started. If you want the connection with the Cordless System you must now check the connection between the PC and the Cordless System and then select N(o). If communication has not been established yet, the following message ’Waiting for DCT1800 response...’ is displayed. If there is still no communication with the DCT1800 system the message ’No connection with DCT1800. Do you wish to continue? (Yes/No)’ is displayed. When the communication is established the message ’Loading data from DCT1800, please wait...’ is displayed. If the Cordless System has been initialized before with a version of the Cordless System Manager older than revision R6, the message ’WARNING: SPU-S parameters not initialized yet. ’ is displayed. If so, do not forget to execute the ’Restore country data’ command. FAULT TRACING DESCRIPTION Uppgjord/Prepared 34(42) Dokumentnr/Documentnr Faktaansvarig - Subject responsible 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 3.4 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Check on service display DT 288, DT 360, DT 368 The portable can be switched to service display mode (type DT 310 does not support this function) displaying information regarding the radio interface like BS number, carrier, time slot number, RSSI etc. When the service display is active, calls cannot be made and incoming calls will terminate the service display mode. To make this display visible while calling, first setup the call and then, via the `R(inquiry)' menu, access the service display menu. Note: Activating the service display reduces the normal functioning of the portable. It is therefore recommended only to use this facility in exceptional cases, e.g. when service requires such. 3.4.1 Activating Service Display Mode DT 360 (A-protocol) 1 Switch off portable 2 Switch on portable with special code: ON /MUTE (Press the 3 keys simultaneously for more than 1 second). 8 + 2 + A `DCA-Service' menu will appear in the Preference menu. This menu can be removed by switching-off the portable followed by a normal switch-on. 3 Access Preferences menu 2 x down, yes. 4 Access DCA-Service menu 1 x up, yes. 5 Access wanted service display option. The DCA-Service menu has six options available to display different types of information. Explanation of Service Displays Data is always displayed in hexadecimal numbers. The Base Station number relates to the physical connection in the central Unit. Note: A portable is always blind for the two adjacent time slots. For example, a portable is locked on a Base Station on TS 5. If it approaches a Base Station that has only one active channel (traffic or beacon) on TS 4 or TS 6, the portable will not see that Base Station. The display remains unchanged until the current channel or the channel of the second Base Station changes. Consider this when using the menu's below. Link Info CS Fp SsQuLi H9 09 2A20-4 C S Fp Ss Qu Li : Carrier (A..J) : Time Slot number (0..9,A, B) : Base Station number (Fixed Part) : Signal strength (RSSI) : Quality of the signal (RQI) : Link type (0 = beacon, 4 = traffic) The Link Info option can be used for site surveys and commissioning of the system. All information regarding the traffic/beacon channel to which the portable is locked, is visible. The signal strength theoretically varies between /00 and /3F. In practice, values will lie between /07 and /37, of which /07 means noise, /37 means optimum quality. Typical values are /20 .. /29. All - FP + RSSI FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 35(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved FpSsFpSsFpSs 092A1518XX-- Kontr/Checked Fp Ss XX -- Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference : Base Station number : Signal strength of its best channel : No more Base Station number detected : No channel detected This menu can be used to check the traffic that is offered on a certain location. It shows the number of Base Stations within reach of the portable in order of their respective signal strength. The portable displays a list of up to 7 different Base Stations, the maximum a portable can see. FP - Info N Fp Ss CB D 0 09 2A 11 0 N Fp Ss C B D : Number of Base Stations in list (0..6), see previous display : Base Station number : Signal strength of its best channel : Number of channels in use on Base Station : Number of channels in use on portable with current Base Station : 0 = no channels, portable locked on other Base Station : 1 = beacon or traffic : 2 = handover occurring : Number of time slots disabled on Base Station (max. 10 seconds) This menu allows scrolling through the Base Stations (/00../FF) list. The default Base Station is the first Base Station mentioned in the All-FP+RSSI display; the one with the highest signal strength. By pressing `down/up', you can display other Base Stations. When a Base Station is not in the portable list, the display remains blank. If it is, the display shows the data as specified in the lines above. `N' may change during the display if another Base Station from the portable list is getting a higher/lower signal strength than the one currently displayed. Channel Info Not applicable to maintenance Time Slots Not applicable to maintenance Select PUN A : Automatic selection Select PUN 01234567 A This menu is useful for testing purposes when more systems cover the same area. It allows a forced selection of one system on a portable that is programmed for both systems. By selecting a different PUN an engineer can test Base Stations of different systems on the same spot without having to re-initialize his portable. When `A' is selected, the portable will automatically select systems for which it has access rights. After switching on, the portable is always set to automatic selection. FAULT TRACING DESCRIPTION Uppgjord/Prepared 36(42) Dokumentnr/Documentnr Faktaansvarig - Subject responsible 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 3.4.2 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Activating Service Display Mode DT 368 (GAP-protocol) 1 Switch off portable 2 Switch on portable with special code: ON /MUTE (Press the 3 keys simultaneously for more than 1 second). 8 + 2 + A ‘LinkInfo’ menu can then be accessed via the Info - DCA Service menu. This menu cannot be accessed after a normal switch-on. Access Info - DCA Service menu. Access Linkinfo menu. Note: It is also possible to access the DCA Service menu when the phone is ‘off-hook’ ie during a call. The DCA-Service menu has two options available to display different types of information. Link Info The link info menu has two display options which can be selected by pressing either up or down. The following display is entered by pressing up: PARK 10002140140 Upper line : PARK (Portable Access Rights Key) is displayed Lower line : The PARK number without the first two digits and the checksum : PARK 3110002140140-4 is represented as 10002140140 : Signal strength (RSSI) The following display is entered by pressing down: CS Rp SsQu T H9 09 2A20 4 C S Rp Ss Qu T : Carrier (A..J) : Time Slot number (0..9,A, B) : Base Station number (Fixed Part) : Signal strength (RSSI) : Quality of the signal (RQI) : Link type (0 = beacon, 4 = traffic) The Link Info option can be used for site surveys and commissioning of the system. All information regarding the traffic/beacon channel to which the portable is locked, is visible. The signal strength theoretically varies between /00 and /3F. In practice, values will lie between /07 and /37, of which /07 means noise, /37 means optimum quality. Typical values are /20 .. /29. 3.4.3 Activating Service Display Mode DT 288 (GAP-protocol) 1 Switch portable: 2 Press: 3 Press: ON down until Information appears then press YES down until Total calls appears then press YES one after the other until you reach DevServices. Here you will find the Link Info, the FP Info, the Display Tests, Hardware conditions. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 37(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 3.5 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Check on configuration data for trunks When checking configuration data for trunks verify the following: 3.6 • That the selected line signalling diagram agrees with the public network for the relevant trunk and the country specific session is loaded. • That the country specific RASC session is loaded. • This can vary depending on the type of public exchange which type of trunk is connected. • Signalling to public exchange; decadic, DTMF, MFC/MFE or ISDN. • Supervision times. Voltage measurements System voltages can be measured either using the RASC tool (menu systems- ad-converters) or directly on the backplane. As it is possible to cause a short on the lines during measurement all boards in the cabinet should be removed. Test points on the backplane are accessible only if the CPU-D_ in position 0 is removed (refer to 1531-BDV11308 for details). 3.7 Check on power supply Check the secondary voltage of the transformer(~36VAC), generally power supply (48VDC) and battery charger regarding connection to mains and functioning fuses. Check (if installed) the battery condition of the power back-up. Replace (if any) faulty units. The voltages (see drawing below) can be verified on the backplane. As there is always the risk of short circuits these measurements should be done when all boards have been removed. View of left most connector mounted on backplane -12V +12V Test points GND +5V -48V A02 C02 0V (B02, B04, C02, C04) -48V (A08, B08, C08) -12V (C14) +12V (A16) exchange power cable TRE 990 113/850 0V (A30, A32) +5V A32 (C30,32) C32 48V DC or 36V AC FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 38(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 3.8 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference System reset There are several conditions needing a restart of the PBX. In this case there are two ways of restarting the system: • Switch off the power supply either by disconnecting from mains (unplug, switch off the supply lines) or switch off the exchange using the switch at the bottom of the cabinet. • Make a short between the two pins (A32 and C32) on the connector at the front of the CPU-D. Be careful when shorting these two pins by using a plug with a wired connection or a jumper. A C 26 28 30 32 reset pins CPU-D_ 3.9 Check on line network Checks on the line network can vary in scope depending on the configuration of the line network and type of connection. See the following schematic diagram and use the exclusion method by testing in the order stated. PBX MDF MDF Jack 3.10 1. The first MDF to which the PBX is connected. Disconnect the network below this point and test by connecting a telephone or other unit here. 3. Interim MDF (none, one or more). Disconnect the network below this point and test by connecting a telephone or other unit. 2. Test with telephone or other unit here. Check on programmable parameters for facilities For facilities and various connection cases there exist a number of programmable parameters that need to be programmed correctly for the facility to function. See "Facilities" in RASC. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 39(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference In addition there is a traffic group matrix that states the authorisation for different connection cases. The traffic group matrix can be used to verify connection paths, e.g. A may call B but B may not call A. 3.11 Check on resources Free and utilised resources are specified in the RASC-menu Maintenance-system-resources. Here are stated the number of free PCM-channels, number of free references on VMU, etc. Only the number of free PCM-channels and free references on the VMU-board are of interest. Other information is used only during system testing in conjunction with new development. With the help of the stated information it is possible to determine whether the PBX possesses sufficient capacity. 3.12 Fault checks / correction of intermittent faults Intermittent faults constitute a considerable problem as it is difficult to verify whether remedial measures eliminated the fault. It is essential therefore to make great efforts to identify in which circumstances the fault occurs. If one is fully or partly successful then one has acquired a possibility of verifying whether the fault really has been eliminated by attempting to repeat the circumstances which gave rise to the fault. If this is not possible the PBX should be checked at suitable time intervals. This is often a matter of judgement and varies from case to case. The following part of the fault checking relates to the Cordless system with a table describing the class, most probable reason and service class number. • Column 1 - Fault numbers in sequence • Column 2 - Service class: • Class 1 Faults in this class mean that communication with a board or peripheral is lost. In most cases there is a physical reason. Check on proper connection. Execute a Replace Board by the System manager-Control menu and check that the fault disappears. If not successful, proceed to class 3. • Class 2 Faults in this class can be minor faults that can be cleared by a board reset. Execute a Replace Board by the System manager-Control menu and check that the fault disappears. If not successful, proceed to class 3. • Class 3 Faults in this class are in most cases fatal errors that require board replacement. It is convenient to ensure that the fault is a hard fault by executing a Replace Board and checking if the fault disappears. If not successful, execute the Replace Board command from the System manager-Control menu and replace the board by a spare board. The new board is automatically tested and taken into service. If the fault persists, call your local supplier for service. • Column 3 - Fault threshold This column indicates the number of times a fault may occur intermittently. This means that after detection of the fault, the fault does not reappear when tested, see paragraph 2.2. If this intermittent occurrence exceeds its threshold number within 24 hours, a status code S (service) will be written in the Fault Table, a fault report is written in the Service Table and the General Alarm is activated. The counter values are halved every 24 hours. Threshold value 99 is equivalent to infinite. • Column 4 - Fault description This column gives a brief description of the fault that has occurred. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 40(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Fault Service Fault Code class Threshold Tillhör/Referens-File/Reference Description 1 2 2 Unexpected message/primitive Message received but not within specified time 2 1 99 Board/CPU communication error or time out. Message corrupted or not received 3 2 99 Threshold Fault counter exceeded 4 3 1 Board controller ROM error 5 3 1 Board controller RAM error 6 3 2 Internal loop back error 7 2 5 Peripheral state error- state of periph. differs from state listed in CPU data base 8 1 6 Base Station not present - wiring fault or power lost 9 3 2 Peripheral ROM error 10 3 2 Peripheral RAM error 11 2 99 Peripheral status unknown. Two simultaneous faults: status can not be obtained 12/13 2 99 Board status unknown. No communication with board: status can not be obtained 14 2 5 Peripheral communication error or time out. Message corrupted or not received 15 2 2 Board signalling link was cut. When a board is not polled, it resets itself and after communication has recovered it sends this message to CPU 16 1 10 Board controller poll response error 17 3 99 CPU main processor RAM error 18 3 99 CPU main processor ROM error 19 3 99 CPU EEPROM error 20 2 1 CPU real time clock failure 21 3 2 CPU-poll processor (8031) RAM error 22 3 2 CPU-poll processor (8031) ROM error 23 1 2 CPU-poll processor communication error 26 2 5 Internal buffer overflow 27 2 99 Board controller watchdog reset 28 1 2 HSCX error. Serial communication controller on CPU of signalling high way 29 3 99 Signalling high way down. No communication between CPU and all other boards 33 1 1 Initialization procedure not successful. Due to e.g.: no communication with board 34 1 99 Portable related circuit not present. DTU-channel. 39 PC communication error. When statistics run, logging is stopped. Statistics must be set ON again 50 1 Minimum configuration error 51 2 Subject unreliable. Fault not continuously present 52 Subject could not be tested after maintenance action due to a coincidence-Subject must be verified if operational. It may be ’AVE’ but not working. Reset subject FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 41(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Comment to Fault Codes • Fault 17 ... 26, 28, 29 CPU faults. Replacement of the CPU requires up loading of its data to PC first. If not possible any more, down load the new CPU with the most recent up load file on disk. • Fault 35, 36, 37 These faults may disappear automatically. The DTU sends a message to T&M and T&M clears the fault status: L1 = AVE and L2 = AVE. However, the Service Error message remains and the General Alarm as well. They must be cleared by 'Clear Service'. • Fault 52 Maintenance personnel must verify if the subject is operational or not. It may occur that a subject is given `AVE', but not working any more. If not working, reset the subject and wait for new fault. 3.13 Fault reporting Fault reporting, in accordance with current SAR-routines, shall be made to the support instance and the warning log shall be enclosed either as printout or on diskette. To enable suitable action it is essential that the correct information is provided describing in the best possible way how the fault was initiated (sequences), under which circumstances (state) it occurred (traffic situation and time), how the fault revealed itself and whether it was repeatable. Also state the PBX configuration, which can be obtained by reading out the revision states (see point 4.15, "Translation and verification of revision states"). 3.14 Update of board positions Read the revision states of the hardware positions, RASC-menu Maintenance-HW/SW-RP. Highlight the relevant row with the cursor and update the board. All programmable data is assigned default values. For extensions and trunks it is also necessary to assign all individuals a telephone number. Normally it should be possible to load configuration data from RASC provided back-up exists. 3.15 Translation and verification of revision states Ericsson identifies all products by means of a product number and revision state. An ASB 150 02 exchange is built-up from several sub-products, each with its product number and revision state. Via RASC-menu Maintenance-HW/SW-CPU it is possible to read the product number and revision state of the central program's PROM-set (LZY), PROM (RYS) and linkage unit (CXC). Via RASC-menu Maintenance-HW/SW-RP it is possible to read the product number and revision state of three different regional control programs per printed circuit board position. The same RASC-menu also permits the device board's product number to be read, however the revision state cannot be read directly although it can be determined with the help of the information in columns PCB and PS. • PCB contains a digit that indicates the R-state of the PBA's printed circuit board. • PS code contains a digit that can be related to a modification of the PBA that took place subsequent to the manufacture of the PBA. In the service advice is stated, for each board's (product number) revision state, the applicable PROMset (RYS), PS-code and PCB-code. Note: that there also exist prerequisites stipulating which revision states for which products may be combined. FAULT TRACING DESCRIPTION Uppgjord/Prepared Faktaansvarig - Subject responsible 42(42) Dokumentnr/Documentnr 1545-ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 4 Kontr/Checked Datum/Date Rev 1999-07-15 F Tillhör/Referens-File/Reference Resistance of temperature sensor at different temperatures Temperature in deg. Celsius kΩ - 40 - 35 - 30 - 25 - 20 - 15 - 10 -5 328.0 237.7 173.9 128.5 95.89 72.2 54.9 42.0 Temperature in deg. Celsius 0 +5 +10 +15 +20 +25 +30 +35 kΩ Temperature in deg. Celsius kΩ 32.5 25.3 19.9 15.7 12.5 10.0 8.06 6.53 +40 +45 +50 +55 +60 +65 +70 +75 5.33 4.37 3.6 2.99 2.49 2.08 1.75 1.48 Temperature in deg. Celsius kΩ +80 +85 +90 +95 +100 1.25 1.07 .915 .786 .677 MAINTENANCE INSTRUCTION 1(23) Uppgjord/Prepared Faktaansvarig - Subject responsible SEA/EBBM Stangelberger SEA/EBBS Dokansv/Godkänd - Doc respons/Approved 1541 - ASB 150 02 Uen Kontr/Checked SEA/EBBM Dokumentnr/Documentnr Datum/Date Rev Tillhör/Referens-File/Reference 1999-07-15 E ASB 150 02 Database reference 1541.fm MAINTENANCE INSTRUCTION ASB 150 02 Table of contents page 1 2 2 3 3 4 4 8 1.1 1.2 1.3 1.4 1.5 1.6 REMOTE UPGRADING OF THE CENTRAL SOFTWARE . . . . . . . . . . . . General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Requirements of the CPU-D4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Upgrading Program . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Creating the Output File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Terminal Application to load the file into the CPU-D4 . . . . . . . . . . . . . . . . 2.1 TROUBLE SHOOTING . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 14 Upgrading using a modem with the terminal program . . . . . . . . . . . . . . . 14 2 3 LEDs ON THE CPU-D4 . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 15 4 4.1 4.2 4.3 HOT-SWAPPING OF BOARDS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Prerequisites . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Procedure. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 16 16 16 16 5.1 5.2 5.3 5.4 DETAILED INFORMATION ON BOARDS. . . . . . . . . . . . . . . . . . . . . . . . Considerations for ELU-* and IC-CU boards . . . . . . . . . . . . . . . . . . . . . . Considerations for BTU boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Considerations for VMU-* boards . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Final Check . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 19 19 20 21 21 5 6 HARDWARE ADMINISTRATION . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 7 REPLACEMENT OF BATTERIES . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22 2(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference 1 REMOTE UPGRADING OF THE CENTRAL SOFTWARE 1.1 General The BusinessPhone remote upgrading system is used to upgrade the current software running in an ASB 150 02 exchange to a different or enhanced software version without the need of exchanging the PROMs on the CPU-D4. The software that should be upgraded to, must be based on the identical language version that is already installed in the system. If the language shall be changed, the system must be upgraded with the complete software in the new language. Remote upgrading has the following prerequisites on the PBX side: CPU-D4 equipped with FLASHPROMS and a FECU (KDU BS 130 06/_ or KDU BS 130 07/_) has to be installed. For details on FLASHPROMS refer to Requirements of the CPU-D4 on page 3. On the maintenance side a PC is necessary with hardware requirements as mentioned in chapter 1.2. This PC can be connected to the CPU-D4 directly (V.24) or remotely. The PC requires an operating system such as MS Win95 or MS WinNT 4.0. The terminal application program, provided by the operating system, such as HyperTerminal, Telix etc. manages the communication between PC and the CPU-D4. The terminal program is used to load the new ASB 150 02 software upgrade file created by the "UPGRADE PROGRAM" into the CPU-D4. In order to keep the transmission time as short as possible the "UPGRADE PROGRAM" creates only a file comprising the differences between the existing software in the exchange and the new software to which it should be upgraded to. Optionally a full software upgrade version can be created too. The basic principle of upgrading is that the CPU-D4, equipped with two separate program memory areas receives an upgrade software and stores the changes in a temporary storage area, called the upgrade FLASH that is controlled by the RP. This upgrade software, called output file, is created by the "UPGRADE PROGRAM" chkdiff.exe, then transferred and stored directly into the upgrade FLASH. This file has to be sent as a text file. The PBX continues operating while the program is loaded remotely or locally into the CPU-D4 upgrade FLASH as the CP operates on the program stored in the program memory area called active FLASH. The time to upgrade to the new software can be selected in a menu. As soon as the upgrade time is reached the CPU-D4 is automatically restarted. ASB 15002 Remote O&M Centre CPU-D4 MODEM HyperTerm Telix Communication to CPU-D4 Data transfer control V.24 Upgrade FLASH FLASH 1 3 System reset data is copied to active Flash Active FLASH PROM 1 2 3 Data is stored in the upgrade FLASH 3(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference During the restart several actions are performed. The content of the upgrade FLASH is verified. The base data of the active FLASH is merged with the data stored in the upgrade FLASH. After final verification the data of the upgrade FLASH is copied into the active FLASH if ordered. This process results in a delay of the start-up but is indicated by flashing LEDs (see page 16). Optionally no upgrade can be ordered and the upgrade information is just stored in the upgrade FLASH. This is useful if an upgrade is required at a later date. In all cases it is necessary to create the output file based on the current system software version and the in comparison to system software version that is to be upgraded to. 1.2 Requirements HW: (main requirements) 486DX2 66MHz at least 16 MB system memory 15MB free hard disk space free COM port capable of up to 9,6 kBaud communication speed SW: The PC operating system can be either Microsoft Win95 and WinNT 4.0. The terminal application is used to build up the connection to the exchange. As an example for HyperTerminal the settings below are required. Settings: 1.3 select data rate: parity check data bits stop bit flow control COM 1 or COM2 9600 Baud OFF 8 1 XON/XOFF ASCII sending - do not select echo typed characters locally - do not select send line ends with line feeds Requirements of the CPU-D4 The firmware on the CPU-D4 must be at least RYS 102 533 Version R2A or higher. Verify that the FLASH PROMs are mounted on the CPU-D4. RASC displays this information in the RP menu such as: 4(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved POS TYPE 00 01 02 03 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference ARTICLE REV HW CPUD4 ROF 157 5118/4 RYS 102 533/1 FECU ATMEL AT 49F040 ELUD ROF 157 5118/2 RYS 102 516/1 ELUA ROF 157 5114/1 RYS 102 514/1 BTUB ROF 157 5121/1 R4 R2C R1A 0 V=0 4 R3 R1A R2 R1J R1 1 FECU FLASHPROM *) V=0 I=1 4 V=0 I=1 0 V=0 I=1 *) This line could also show: MACRONIX MX 29F040 NOTES I=3 FLASHPROM 5(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked 1.4 Upgrading Program 1.4.1 Installation Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Before starting refer to the hardware requirements mentioned before. The binary software files and the upgrading program chkdiff.exe are available on the support server at SEA. Note: Chkdiff.exe requires a 32-bit operating system such as MS-Win95 and MS-WinNT4.0. All registered users can download these files. Download the ASB15002 SW file for the required release from the server. Copy the upgrade program and the ASB 150 02 software files into a dedicated directory. These files are compressed and after extraction the following binary ASB15002 files are available e.g. as listed below: • readme.txt This file contains information on the software version • 101RA21.me These files are necessary for the upgrading program • A11R1AA.bin • A21R1A.bin and These files are extracted from the current ASB15002 SW • A31R1A.bin. zip files: They are available on the FTP site. .... Check in the read me file the version of the available program and compare it with the program version installed in the PBX to be updated. All three binary files are needed to install a complete SW upgrade. 1.5 Creating the Output File The first step is to create an output file that shall be loaded into the exchange. Refer to the read me file giving details of the version of the software to be upgraded to and compare it with the program version installed in the PBX to be updated. It is important to know your market version to perform the upgrade for details refer to the ORDERING INFORMATION (131 62-1x/ASB150 02) or the index of the software e.g. LZY 203 2230/x. The x states the market version needed to create the upload file. Execute the 32 bit console application program chkdiff.exe in a DOS prompt. The program chkdiff.exe generates the file which is used for uploading the new SW-version. This application verifies which parts of the SW has been changed, determines the differences between the two SW-versions and creates an output file (*.txt). The file is a specially coded (containing line number, checksum, ...) but must not be opened by any tool (e.g. editor) as in this case the data may be corrupted. 6(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference The file denominations used for remote upgrading are explained in the following: Output-file name explanation: r10 1 A_r10 1 B.txt link version market version release version link version market version release version existing version - to upgrade version PROM-file name explanation: A 1 1 R1A.bin PROM revision market version PROM number release number me-file name 10 1 A.me explanation: link version market version release number For this procedure it is very important to have the correct link version. This could present a problem in existing (running) SW-versions in a PBX. To find this value enter RASC. Menu maintenance -> HW/SW -> CPU. Here the LZY 203 223x/x R1A the highest link version number is the valid number to be used and entered in the field of the software version currently in the PXB. The link version can be read out using RASC. Check the LZY information with link version of the PROMS. The highest value is the correct link version or by reading the information in the PROM me-file. After executing chkdiff.exe and select whether a standard or full upgrade is needed and enter the data accordingly. 7(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.5.1 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Standard upgrade This standard upgrade is the common upgrade for the ASB 150 02 exchange. Choosing this option keeps the transmission time as short as possible. The chkdiff.exe creates a file comprising only the differences between the existing software in the exchange and the new software to which it should be upgraded to. E:\>chkdiff AA A A A A A A AAAAAA A A A A A A A A SSSS S S S S SSSS S S S S SSSS BBBB B B B B B B BBBB B B B B B B BBBB 1 11 11 1 1 1 1 1 1 1 1 5555 5 5 5 5 555 5 5 5 5 555 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 00 22 2 2 2 2 2 2 2 2 2 2 2222 Welcome to the remote update file generation menu: Please insert the release, upgrading shall be based on: 10 Please insert the market, upgrading shall be based on: 1 Please insert the SW version,upgrading shall be based on: A Base information were checked successfully Please insert the wanted upgrading release: Please insert the wanted market version: Please insert the upgrading version: Upgrade information checked successfully Binary file names verified successfully Checking maps: map number: 0 number of records different 0004 10 1 B (e.g. if R10 is selected) (e.g. if STANDARD is selected) (select version) (e.g. if R10 is selected) (e.g. if STANDARD is selected) (select version) After entering the data this information is sent back to verify operation. If an error is encoutered retry with correct data. Enter the requested values in the fields above. The operation is terminated stating that the output file e.g. r10 1 A—r10 1 B.txt was generated. As an alternative it is possible to execute the chkdiff.exe and add the upgrading parameters in the command line such as: e.g. chkdiff∩r10∩1∩A∩r10∩1∩B for standard upgrade or chkdiff∩r10∩1∩B for full upgrade. OLD NEW The symbol ∩ denotes an empty space in the command line. NEW 8(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.5.2 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Full upgrade If the remote PBX has a software that requires a full upgrade then enter the letter "b". In this case the chkdiff.exe program executes a full software upgrade file. This results in the largest file size and therefore takes the longest time to transmit. E:\>chkdiff AA A A A A A A AAAAAA A A A A A A A A SSSS S S S S SSSS S S S S SSSS BBBB B B B B B B BBBB B B B B B B BBBB 1 11 11 1 1 1 1 1 1 1 1 5555 5 5 5 5 555 5 5 5 5 555 00 0 0 0 0 0 0 0 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 00 0 0 0 0 0 0 0 00 Welcome to the remote update file generation menu: Please insert the release, upgrading shall be based on: 22 2 2 2 2 2 2 2 2 2 2 2222 b (full release version is selected) 1 B (e.g. if STANDARD is selected) (select version) You wanted to base the output on a blank PROM set! Please insert the wanted market: Please insert the upgrading version: Upgrade information checked successfully Binary file names verified successfully Checking maps: map number: 0 number of records different 0004 This statement confirms that a full upgrade not based on initial SW is chosen. After entering the data this information is sent back to assure correct operation Enter the requested values in the fields above. The operation is terminated stating that the output file e.g. Blank_r101B.txt was generated. 9(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.6 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Terminal Application to load the file into the CPU-D4 Before starting the upgrading verify if the system time and date is correct otherwise correct it with RASC. Verify that the physical connection to the exchange has been established between the COM port of the PC (optionally via modem) and the V.24 interface/modem on the CPU-D4. The upgrade program chkdiff.exe creates an output file called (____.txt). This is a binary file and must be sent as a text file. The terminal application has to be set for this type of transmission. Depending on which type of upgrade is requested, the file is composed of either a complete new ASB 150 02 software version or of only the differences in code between the existing software on the CPU-D4 and the new software, to reduce transmission time. In the latter case data is omitted that is already available in the active FLASH on the CPU-D4. This shows that it is very important to know the actual software in the active FLASH running on the CPUD4 and not depend on revision information stated on the PROMS mounted on the CPU-D4. Note that the software version stated on the PROMS is obsolete after loading the new software. The output file (____.txt) must not be accessed by any editor as this action may destroy the content. Start the terminal program as available on your operating system e.g. Hyperterminal. The terminal application starts the communication with the CPU-D4 and a selection menu is displayed prompting the next actions. The CPU-D4 supervises the communication and if no input occurs for more than 15 minutes the terminal is logged off and the connection is shut down. This is to prevent unnecessary connection fees. The CPU-D4 verifies all entered requests and the menu screen offers a selection of commands that are executed by typing in a letter. Set up the connection to the ASB 150 02 system by using the terminal program on your PC and after having configured the settings mentioned before. To start the communication quickly press the "S" key 3 times. There is a timer surveillance monitoring the time between two key strokes and if it is greater than 1 second the process is terminated. If the connection was built up successfully a welcome screen (see below) greets the user and requests a password entry. 1.6.1 Communication Start WELCOME TO BUSINESSPHONE REMOTE UPGRADING SYSTEM ENTER PASSWORD: ***** Enter the system password: "33333" If the correct password is entered the main menu will be displayed otherwise the session will be automatically closed. 10(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.6.2 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Main Menu The main menu prompts the following functions: ASB 150 02 REMOTE UPGRADING MAIN MENU S T U D C E view information about active FLASH and upgrade FLASH view system and upgrade time load new SW into upgrade FLASH define upgrade time cancel an ordered upgrade exit remote upgrading Please choose your MENU function: Select a function in the menu above by typing the related letter. 1.6.3 Menu item "S" - view information about active FLASH and upgrade FLASH ACTIVE PROGRAM: LZY2032230/1 R1B Prom 0: RYS102204/1 R1B CheckSum: Prom 1: RYS102205/1 R1B CheckSum: Prom 2: RYS102206/1 R1B CheckSum: 57AF hex 3B78 hex 120E hex UPGRADE PROGRAM: LZY2032230/1 R2A Prom 0: RYS102204/1 R2A CheckSum: Prom 1: RYS102205/1 R2A CheckSum: Prom 2: RYS102206/1 R2A CheckSum: D6D0 hex A164 hex A100 hex UPGRADE TIME: DATE: 00-00-00 TIME: 00:00 SYSTEM TIME: DATE: 98-02-22 TIME: 17:55 UPGRADE FLASH STATE: OK Press ENTER to continue: ACTIVE PROGRAM This information applies to the actually running ASB 150 02 software program in the active FLASH. UPGRADE PROGRAM This information applies to the ASB 150 02 software program, which is stored in the upgrade FLASH. The contents is re-written by uploading the new SW. During every system restart the contents in the upgrade FLASH is checked. If an error is encountered (e.g. wrong checksum or last uploading of new SW was not finished) the content of the active FLASH will be copied into the upgrade FLASH. 11(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference UPGRADE TIME DATE: YY-MM-DD TIME: HH:MM shows the upgrade time. SYSTEM TIME DATE: YY-MM-DD TIME: HH:MM shows the current system time. UPGRADE FLASH STATE The upgrade FLASH state is indicated by the following messages displayed on the screen: • • • • • NOT OK OK ERROR DURING LAST UPLOAD UPGRADE WAS ORDERED UNKNOWN connection was broken? OK indicates no backup has been ordered repeat upload connection was broken? Press ENTER to continue: To return to the main menu press ENTER. 1.6.4 Menu item "T" - view system, backup and upgrade time SYSTEM TIME: DATE: 98-02-22 TIME: 12:55 UPGRADE TIME: DATE: 00-00-00 TIME: 00:00 Press ENTER to continue: This menu just displays the system and upgrade times. No change of time settings are permitted on this screen. 12(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.6.5 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Menu item "U" - load new SW into upgrade FLASH START SENDING A FILE OR PRESS E TO EXIT This screen requests to start the file transfer in the terminal application or press "E" to abort the procedure To send the file execute send e.g. press the send icon on the terminal application. Verify that the file is sent as a text file. The next screen shows the process of file uploading. 1.6.6 Uploading the file PROM number: 0 map number 0 XXXXXXX number of the MAP number of the PROM After the file transfer is started this screen shows the progress of uploading. Each PROM is numbered (1 to 3) and the number shows which PROM and which MAP is currently re-written. A "X" is displayed as a progress indicator as data is stored. If an error occurs during transmission a short error message describing the error cause is displayed. If the file was transferred without any error „UPLOADING SUCCESSFULLY COMPLETED !“ is displayed. 13(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.6.7 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Menu item "D" - define upgrade time Press E to exit without changing the upgrade time Press ENTER after you have changed the upgrade time to activate the upgrade The TAB key moves the cursor to the next field The upgrade time entered must be later than the system time SYSTEM TIME: DATE: 98-02-22 TIME: 17:55 UPGRADE TIME: DATE: 00-00-00 TIME: 00:00 The time to upgrade to the new software can be selected in this menu. The TAB key moves the cursor between the fields. Press ENTER after you have changed the upgrade time to activate the upgrade NOTE: The entered upgrade time has to be a time later than the system time and the year of the upgrade time has to be the same as the year of the system time. If changes in any field are entered a validation check is done. (e.g. 61 is not valid for the minutes) The time is verified every 5 minutes thus after waiting up to 5 minutes upgrading is activated. If the program in the upgrade FLASH is valid and the system time reaches the upgrade time the system will automatically perform a re-start. The upgrade is also initiated if the system is restarted locally. During the restart the SW from the upgrade FLASH will be copied into the active FLASH and then the system restarts with the new software. 1.6.8 Menu item "C" - cancel ordered upgrade time Press E to exit without cancelling an ordered upgrade Press C to cancel an ordered upgrade After entering the letter "C" the system cancels the task and returns to the main menu. 14(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 1.6.9 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Menu item "E" - exit remote upgrading SESSION IS CLOSED BYE If no input occurs for more than 15 minutes then the system logs out and automatically shuts down the connection. 15(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked 2 TROUBLE SHOOTING 2.0.1 Upgrade program related faults Error condition Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference correction refer to: Base information incorrect Verify that you have the link information correct for the software currently running on the CPU-D4. page 6 Error input parameters are not within directory information file Verify that all parameters were correct. Check that the market version is correct. Check that the upgrade version is correct. page 7 2.0.2 Terminal application related faults Error condition Check sum error correction refer to: If the CPU-D4 detects a checksum error e.g. the connection page 10 caused data to be corrupted or missing, re-transmit the output file. In case of problems verify that the modem speed is the same data page 15 rate settings of the terminal application. Terminal application does not start If a timeout is engaged it takes some 15 minutes before a terminal page 9 can reconnect. Reasons: the session before was aborted or a wrong file was sent to the CPU-D4 or the modem connection caused data corruption or the CPU-D4 is performing an upgrade/ backup etc. Upgrade Flash errors: ERROR DURING LAST UPLOAD NOT OK UNKNOWN NOTE: 2.1 The CPU-D4 monitors and verifies the data transfer. Corrupted data is detected and the upload has to be repeated. page 10 If the data is corrupted re-transmit the output file. Possible causes page 10 e.g. broken link, PBX is restarted during upload etc. Cause of error not known and the upload has to be repeated. page 10 If upgrade is ordered, a system restart causes traffic interruption. Select a time that causes the least customer disturbance. Upgrading using a modem with the terminal program If the maintenance centre is remotely located to the exchange the use of a modem is required to cover the distance. In this case the application displays the same prompts and screens. The data rate between CPU-D4 and maintenance PC is up to 9.600 Baud. In case of problems verify that the modem speed is the same data rate settings of the terminal application. 16(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 3 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference LEDs ON THE CPU-D4 The data uploaded into the upgrade FLASH memory has to be copied into the active FLASH memory. This data move is invoked by entering the upgrade time. When the defined time is reached a restart is invoked. The contents of the upgrade FLASH is copied into the active FLASH and the system starts up. The same procedure is started if the exchange is restarted either by power switching or reset on the CPUD4 board. This copying process is indicated by the upper LEDs on the CPU-D4. The CPU displays this process by lighting the LEDs on the front in a specific manner. LED Red red yellow green Yellow The communication to the backplane is interrupted as soon as the red LED is on on fast flashing CPU-D4 Description of condition Green Erasing of the upgrade FLASH. This takes some 30 seconds. on one flash Writing into PROM 1. After completing, the green LED repeated flashes several times to recalculate the checksum flashes on two flashes Writing into PROM 2. After completing, the green LED repeated flashes several times to recalculate the checksum flashes on three flashes Writing into PROM 3. After completing, the green LED repeated flashes several times to recalculate the checkless flashes on The green LED flashes during checksum recalcularepeated tion of the programming data. Then the system restart flashes is invoked. 17(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 E 4 HOT-SWAPPING OF BOARDS 4.1 General Tillhör/Referens-File/Reference This chapter explains the procedure of exchanging, adding or replacing a board in the ASB150 02 without switching off the power. This procedure can be used for all system boards except the CPU, IC-LU, VMU-D and AUX boards. Changing boards without switching off the power should mainly be used to replace faulty boards or for expanding an existing hardware configuration. 4.2 Prerequisites Boards can only be replaced by boards of the same type, with the same number of individuals. This limitation applies also for changing the number of individuals on an IC-CU-board. Just changing the FECU may cause serious memory allocation problems which may lead to a warmstart of the whole system. New boards shall be inserted in a vacant position only. If the RASC-PC is connected to the system via an AUX-board, this board must not be removed. If RASC is connected via a modem it is not possible to perform any hot swapping action. 4.3 Procedure This action can be invoked either by pressing the appropiate function keys (see Function keys overview on page 18) or by executing the system command called ‘Shutdown’ in the pull down menu located in the RASC menu ‘System data’: System data/shut down/reroute position/cmd: 2095 To exchange (a) board(s) in a running system please follow the five steps below: 1 One or more boards need to be shutdown (see Shutdown of board(s) on page 18) 2 Change or insert new board(s) (see Adding (a) new board(s) to the system on page 19) 3 Search for and activate (a) new board(s) (see Search for new boards on page 19) 4 Re-programming of boards (if needed) 5 Check and erase warnings in the warning-log, which may have occurred because the board has not been available during hot swapping. 18(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 4.3.1 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Function keys overview If all boards are registered in the system the keys below are only activated in the menu: Admin/Maintenance/HW/SW/RP. F1 HELP F2 F3 4.3.2 LOCA F4 PRINT F7 F5 SEEK F8 F6 SHTDWN F9 FILE F10 EXIT F11 UPDATE (board) F12 Shutdown of board(s) The shutdown command is not needed if a new board is plugged into a formerly vacant slot. In RASC this new command is located in the maintenance menu. The shutdown command must be issued before removing one or more board(s) from the system. If a board is removed from the system that was not shut down will cause a system restart. Move in the list to the boards (arrow keys) and press the space bar to select them. Press the function key (F6) to shut down the board(s) or click the field in the pull-down menu. This function key is only available in on-line condition (not available during remote access from e.g. the help desk). Enter the additional input parameter time to shut down if needed. The system waits during this selected time (0 to 11 minutes) and then forces all traffic to disconnect on the selected board(s). RASC displays in a window the remaining time until shutdown is invoked. After this time has elapsed all active processes on the board(s) are terminated and RASC issues a prompt that the board is now ready to be removed. The user can neither exit this window nor use any other RASC function during this time. Note: It is not possible to shut down CPU boards. The selected board(s) must be registered in the E2 memory on the CPU, so it is neither possible to shutdown MISPLACED or MISSING boards nor boards of a wrong type. Additionally a detailed help text is accessible via the F1 key. If the PC crashes or a PC restart occurs during this waiting time, it is not possible to reconnect from RASC to the system until the shutdown process has finished. In this case it is prohibited to enter system programming from a system instrument while a shutdown is in progress. This may cause serious configuration faults (mismatches) which could lead to a non-restartable system (in this case only a cold-start could get the system running again). Transferring configuration data retrieved from a system with a different running/shutdown board configuration (but everything else totally equal) causes serious configuration mismatches. This may lead to a system restart or, even worse, to a non restartable system. Therefore it is necessary to be very careful with retrieving and storing of system configurations. 19(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 4.3.3 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Adding (a) new board(s) to the system One or more boards can be added to the system. These boards can be new ones or updated ones which are still in shutdown state. There are two ways of adding a new board to an operating system: a Replacing a board of the same type (& version) After a board in shutdown state has been updated or replaced by a new one, it can be added to the system using the update command (F9) located in the RP menu in RASC. After the process is complete, RASC receives an acknowledge and this result is shown in the RP menu, now containing all the data of the operational board (PROM version, revision, etc.). b 4.3.4 A new board in a formerly vacant position (refer to next chapter 4.3.4). Search for new boards The search key (F5) in the RASC RP menu is available for finding new boards in formerly vacant positions. RASC checks all board positions marked empty or new for boards. If a new board in an empty slot is found, it is marked as new. The new boards will be reported to RASC and will be shown in the RP menu. By pressing the update function key (F9) the boards are accepted by the system. After all boards have been accepted by the running system, the RP menu is built up new, now displaying all the data of the operational board (PROM version, revision, etc.). Because the new board(s) is/are initialized with some default data only, (re)programming of the board(s) may be necessary. After the initialization (and re-programming, if needed) is finished the board(s) and all individuals are ready for traffic. Note: When the search function is activated all new AUX-T boards are re-started (regardless whether newly inserted or already existing in the system). RASC does not show them. When a board is inserted in a ‘SHUTDOWN’ position and does not exactly match (type & version) the board inserted there before will cause the new board not to be accepted. In this case the slot remains in ‘SHUTDOWN’ state. 4.3.5 Deletion of a board Not available, restart the exchange to delete a board. 20(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved Kontr/Checked Datum/Date Rev 1999-07-15 E 5 DETAILED INFORMATION ON BOARDS 5.1 Considerations for ELU-* and IC-CU boards Tillhör/Referens-File/Reference The central software block which handles ELU-A, ELU-C, ELU-D and IC-CU boards is EX. Note: 5.1.1 It is NOT possible to change the number of individuals of an IC-CU board by performing a shutdown of the board, replacing the FECU by another one (which may offer more/less individuals than the old one) and restarting the board. Insertion of an ELU/IC-CU board There are two possibilities when a new board is inserted at a certain position: There could have been a board of the same type and with the same number of individuals on it or the slot could have been unused. When adding an IC-LU board, this is handled only by IC-CU and does not involve the ASB 150 02 central software. Thus neither further actions are required, nor is it possible to add nor to delete an IC-LU by the central software of the ASB 150 02. Note: Before removing an IC-CU board, save the data by using the Cordless System Manager (CSM), and after replacing the IC-CU board transfer the configuration data from the previously installed board, otherwise all cordless telephone sets need to be re-programmed. The main difference between insertion of a new board in a previously vacant slot and in a slot where another board of the same type was inserted before, is that in the first case no directory numbers are assigned to the individuals after the board has been started. This directory number assignment has to be done from RASC and Cordless System Manager (CSM) afterwards. 5.1.2 Shut down of an ELU/IC-CU board 5.1.2.1 Operator Instrument On an operator instrument calls can be parked with the loop keys, the OP-hold key and the monitor key. If only one call is parked on the loop key and this is an incoming external call, it is rerouted back to the operator queue. If it is any other type of call the call is terminated. For the OP-hold and the monitor key the same applies as for the call on a loop key. If there are no more active operator instruments available for the OP-queue, all calls within the queue are re-routed to the shut down reroute position. The new new command is: • 2095 shut down reroute position (default = 0FFFFh). 21(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 5.1.2.2 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Tandem Configuration If a master is shut down, no calls can be made to the slave extension. But calls to a master/slave extension with a shutdown slave extension are presented on the master extension. 5.1.3 Insertion of an ELU/IC-CU board 5.1.3.1 Considerations for Diversion of an Extension If an extension has activated any kind of diversion (e.g. follow-me) to a directory number that is not available in the system, the call is not diverted but instead starts ringing at the diverting extension. So it is not necessary to check activated diversion during deletion of a board. If diversion of an extension is deactivated, it is not possible to reactivate it again until a valid diversion address is programmed. 5.2 Considerations for BTU boards All registers on the board are marked as busy. So these registers cannot be seized any longer. The system tests the registers on the board to be shut down on their function (only for traffic or only for voice or both). If one or both register types (traffic or voice) are no longer available within the system because the board is going to be shut down and was the only one or last one with this register type on then the system responds with blocked function and lack of resources. These actions do not affect an active call but background music or music-on-hold may be changed to silence. After a call is finished the individual(s) are blocked automatically. Check that the S/T switch settings are the same on the new BTU-B board as on the BTU-B board that was removed from the system. If a BTU-B is shut down, all data-calls (via the S-interface) are terminated too. This applies especially for automated calls. Calls to a directory number belonging to an extension (also operator) located on a board which is in shut down state are rejected or diverted. While a board is removed from the system (the connectors from the board front are removed) the Power Failure Circuit (PFC) is disabled. 5.2.0.1 Changing music channels If a BTU-* board is hot swapped with one or more connected music sources, all extensions and operators currently connected to one of these music sources (background music or music-on-hold) are switched to silence channels. 5.2.1 Insertion of a BTU board When inserting a new board in a previously vacant slot there are no directory numbers assigned to the individuals after the board has been started. Directory number are to be assigned by RASC later on. 22(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 5.3 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference Considerations for VMU-* boards VMU-D: This board must not be hot swaped! VMU-HD:After hot swapping a VMU-HD board all references to announcements are deleted. After reinsertion of a board of the same type and version it is possible to re-program the announcements. Otherwise this could lead to wrong announcements. 5.3.1 Shutdown of a VMU-HD board On a shutdown request all individuals on this board as well as all VMU-channels are blocked, so no new requests to seize VMU-channels are possible and all queued VMU-channel requests are cancelled. All registers on the board are marked as busy. So these registers cannot be seized any longer. This is exactly the same as for a shutdown of a BTU-D board. As soon as a call and process is finished, all individual(s) affected will be blocked automatically. Not all calls with queued voice channel requests receive a channel, so these calls have to continue after the voice playing part or be re-routed. After the selected shut down time out elapses, all channels still playing announcements will be terminated. 5.3.2 Insertion of a VMU-HD board There are two possibilities if a new board is inserted in a slot: There may have been a board of the same type and version in this slot before or the slot may have been vacant. Before a new VMU-HD board can be initialized, note that the references to the anouncements and messages of the old board are deleted. This is necessary because there is no way for the system to check whether the voice stored on the new VMU-HD board is the same as it was on the old one. Set the command 4603 to YES to allow recording of announcments. Announcements stored on the board can be retrieved after an update command by a system programming command via a system telephone (command No. 4450).This does not apply for a new board in a previously vacant position. 5.4 Final Check Generally a shutdown and restart of a board should generate no warnings. If some warnings are logged due to this action, open the log, evaluate the warnings and forward them if necessary to the support centre and, if they are obsolete, erase them. 23(23) Uppgjord/Prepared Faktaansvarig - Subject responsible Dokumentnr/Documentnr 1541 - ASB 150 02 Uen Dokansv/Godkänd - Doc respons/Approved 6 Kontr/Checked Datum/Date Rev 1999-07-15 E Tillhör/Referens-File/Reference HARDWARE ADMINISTRATION On re-start of the exchange the administration data is updated in the system hardware administration area indicating the service technician where to re-insert the different shut down boards after a program upgrade. Using the information in the RP menu of RASC, reduces the risk of misplacing boards after the hot swapping. The most recent and valid configuration is stored on the CPU-D4 containing information such as ROF number, RYS number and revision states, also during the shutdown state of these boards. The battery back-up RAM stores the complete administration information for up to a maximum of 64 boards. To read out the configuration enter RASC, go to the item configuration or look under the maintenance menu HW/SW the configuration list. 7 REPLACEMENT OF BATTERIES The only components in the PBX requiring maintenance are the batteries used as power backup for the entire system and the battery on the VMU-boards. To ensure sufficient battery capacity in the event of power failure, the batteries must be replaced periodically. The replacement period for the power supply battery backup of the PBX, and for the battery on the VMU-board (ROF 157 5117/1) are five years. For more information of the power supply battery backup of the PBX, see document INSTALLATION INSTRUCTION 1531-BML BS 101 01, INSTALLATION INSTRUCTION 1531-BDV 113 08, INSTALLATION INSTRUCTION 1531-BML 351 048 and INSTALLATION INSTRUCTION 1531-BML 351 013. To ensure proper function the batteries should be replaced by new ones every five years. The replacement of the battery on the VMU-board is done easily: 1 be sure that the main supply is ON 2 then replace the battery package on the front of the VMU-board The product No. for the battery on the VMU-board is RNV 991 942/001. MAINTENANCE INSTRUCTIONS Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) EBC/FMD/TL Thomas Åsberg Dokansv/Godkänd - Doc respons/Approved EBC/FMD/TL (Sture Winther) 1(5) Nr - No. 1541-DBC 211 01 Uen Kontr - Checked Datum - Date Rev 1996-10-31 A File Created by: EBCINSV Telephone sets (DBC 211 01, DBC 212 01, DBC 213 01 and DBY 409 01) 1 General . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2 Selftests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 2 2.1 Automatic selftest (when connecting the telephone to ASB 501) . . . . . . . . . . . 2 2.2 Local test mode (initiated with 'C','*','4') . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 MAINTENANCE INSTRUCTIONS Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) 2(5) Nr - No. 1541-DBC 211 01 Uen Dokansv/Godkänd - Doc respons/Approved 1 Kontr - Checked Datum - Date Rev 1996-10-31 A File General This document is to be used by service personnel when maintaining digital telephones DBC 211 01, DBC 212 01 and DBC 213 01 with key panel DBY 409 01, designed for use with defined releases of Ericsson's digital exchanges ASB 501 and ASB 150 02 or equivalent. None of the units (DBC 211 01,DBC 212 01, DBC 213 01 and DBY 409 01) should be repaired, except for replacement of parts listed in the spare parts list Instead, the purpose of this instruction is to decide whether the faults are located in the telephone set, in the exchange or line network. For spare parts, see 154 11-DBC 202+ Uen 2 Selftests There are two types of selftest: (1) automatic testing when the telephone is connected to a local power supply (48 V) or to an exchange. (2) testing initiated by the user pressing a special key combination. The latter test can also be carried out with the telephone connected to the exchange or to a local power supply. The testing refers primarily to the DBC 211 01, DBC 212 01 and DBC 213 01 telephones, whereas the test items applicable to DBY 409 01 are specially indicated in the text. DBY 409 01 can only be tested together with the DBC 203 or DBC 213 telephone. 2.1 Automatic selftest (when connecting the telephone to ASB 501) The automatic selftest is always carried out when connecting the telephone and comprises the following functions/units: watchdog, RAM, D-channel, registers in the line communication circuit (DASL), registers in the speech transmission circuit (COMBO) and the display. If no fault is detected, the LED in the INQUIRY key is lit, and for DBC 212 and DBC 213 the message "SELFTEST OK" is shown on the display for one second. If a fault is detected, this is reported to the exchange when the telephone is activated, but no fault indication is given on the telephone. If no fault is detected in DBY 409 01, the bottom LED is lit for 1 second. If a fault is detected, no LED is lit. MAINTENANCE INSTRUCTIONS Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) 3(5) Nr - No. 1541-DBC 211 01 Uen Dokansv/Godkänd - Doc respons/Approved 2.2 Kontr - Checked Datum - Date Rev 1996-10-31 A File Local test mode (initiated with 'C','*','4') This test is initiated by pressing the keys 'C', '*' and '4' at the same time for one second. The telephone abandons local test mode automatically after 30 seconds, or directly when the ’#’ key is pressed. The following objects are tested automatically: RAM, D-channel, registers in the line communication circuit (DASL), registers in the speech transmission circuit (COMBO) and the display. In addition, the user may test the following objects keys, hook, LEDs, tone ringer, display and speech transmission. 2.2.1 Local selftest This selftest is carried out automatically when local test mode is activated. All LEDs are lit. If no faults are found, the display shows "SELFTEST OK" and the product number of the ROM contents of the telephone's microprocessor, for instance, "CAA1122856 R1A". If a fault is found, the LEDs in Table 1 below will start flashing, and fault messages will be shown on the display. After 5 seconds, the display is filled with characters in descending ASCII order. ERROR MESSAGE (DBC 212 01, DBC 213 01) written on the display ERROR MESSAGE indicated by flashing LEDs ERROR: LCD (if possible) ERROR: RAM ERROR: DASL ERROR: WDOG ERROR: COMBO Programmable key 0 Programmable key 1 Programmable key 2 Programmable key 3 Programmable key 4 Table 1 Error messages presented on the display. MAINTENANCE INSTRUCTIONS Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) 4(5) Nr - No. 1541-DBC 211 01 Uen Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev 1996-10-31 A File Keys for identification of error messages on DBC 211 01, DBC 212 01 and DBC 213 01 On DBY 409 01, the top LED flashes if a fault is found in the RAM test. 2.2.2 Local key and tone ringer test The keys are tested by pressing them one at a time. Each keystroke should result in the generation of a tone signal; this applies to DBY 409 01 as well. “Off hook” and “On hook” will also result in the generation of a tone signal. The volume of the tone ringer can be changed by pressing the volume keys marked ’+' and '-'. The levels will be the same after exit from the Local test mode. 2.2.3 Local speech and transmission test Handset function: Off hook activates handset mode. The microphone signal in the handset is sent via COMBO and is looped back in DASL to the handset receiver. The transmission is tested by blowing into the handset microphone and listening through the handset receiver. The "blow" sound shall now be heard in the receiver. Loudspeaker function: The test is activated by pressing the key marked with a loudspeaker symbol. Then its function is tested by blowing into the handset microphone and listening in the loudspeaker. The "blow" sound shall now be heard in the receiver. Handsfree microphone: After the loudspeaker has been tested, the microphone for the loudspeaking function can be tested by keeping the hook pressed. Sound from the microphone should then be heard in the handset receiver. MAINTENANCE INSTRUCTIONS Uppgjord (även faktaansvarig om annan) - Prepared (also subject responsible if other) 5(5) Nr - No. 1541-DBC 211 01 Uen Dokansv/Godkänd - Doc respons/Approved Kontr - Checked Datum - Date Rev 1996-10-31 A File Volume control: The volume of each transmission mode can be changed by pressing the volume keys marked '+' and '-'. The levels will be the same after exit from the Local test mode. Mute function The mute function is tested by pressing the "Mute" key while blowing in the microphone and checking if the sound in the handset receiver or loudspeaker ceases.