This action might not be possible to undo. Are you sure you want to continue?
§1.1 DX200 Platform: Nokia¶s proven DX 200 platform supports the switching of traffic channels (speech), user data, signalling, short messages and the functions required for cellular radio administration. In addition to the GSM network, the DX200 also forms the basis for the Nokia NMT, PMR, PSTN and ISDN products.
DX 200 structure in block diagram
§1.2 DX200 Hardware:
1. Racks: 2. Sub-racks: 3. Cartridges: 4. Units:
3 Power Supply: DXSYS 5 .DX200 Platform §1.
DX200 Platform §1.3 Power Supply: DXSYS 6 .
4 Computer Units: DXSYS 7 .DX200 Platform §1.
The other unit is kept in the hot stand-by state or the spare (SP) state. DXSYS 8 . the spare unit is not used by the applications and is not permanently bound to some of the N active units but can take over the load of any one of them in case of an active unit failure or by an operator command.2N: 2n When two units are dedicated to a task to which one is enough at any given time.N+1: n+1 When there is just one or a few spare units for a set of N units of a given type.DX200 Platform §1. .5 Redundancy Principles: . one of the units is always active or in the working state (WO).
adaptation of external 2Mbit/s 2.signalling . SWM in HLR.performs tests in the switching network .6 Functional Unites: 1.controls and supervises GSW .hunts free circuits MCMU/BCSU in BSC.DX200 Platform §1. Control functionality : . ET: Access: .call control .electrical synchronisation . Network interface.internal semipermanent connections 3.connects / releases all connections .dynamic connections(calls and data) . Group Switch. GSW : Switches: . SCU in SXC DXSYS 9 .
link between computer units 6. Message Bus.local mass storage for SW back-ups .interface between the system and the user . CLS : . OMU: .connects I/O-devices . MB : . changes the mode automatically .generates the synchronisation signals 5.the synchronisation signal comes from ETs in hierarchical mode .connections to the OMC in BSC .non-redundant or 2N redundant DXSYS 10 .hierarchical/plesiochronous mode.DX200 Platform 4. Operation and Maintenance Unit. Clock and Synchronisation Unit.monitors : configuration and alarms in the system .
I/O system consists of software and peripheral devices . D 2 D 2 D 2 I/O Devices .2 I/O Devices: 1.1 Introduction : 1.FDU : floppy disk unit .MTU : magnetic tape unit 2. I/O system located in the operation and maintenance unit (OMU). User interface: ..FDU : magneto-optical disk .. D 2 . Mass memories: . DXSYS 11 . 3....WDU: winchester disk unit .LPT : line printer .. 2.VDU: visual display unit .I/O System §2. §2. I/O system provides with all the necessary I/O-services by the MMI system.CTU : cartridge tape unit .
BL-SY: blocked by system .VPP : virtual printer protocol .DIA : dialog §2.WO-ID: working idle .BBU : byte basket unit . Special I/O devices: .WO-BU: working busy .VTP : virtual terminal protocol .I/O System 3.VDS : virtual data storage 4.BL-US: blocked by user DXSYS 12 .WO-CL: working closing BL (blocked): . View I/O devices ( ZISI ): WO (working): . Virtual devices: .3 Working states of I/O Devices: 1.COK : command calendar .
MI-US: missing by user ««state set by user 2. but is OFFLINE or the plug-in unit is faulty . busy or not ready (offline) .MI-SY: when no hardware is equipped .TE-ID : test idle ««no test is running .BL-SY: hardware is faulty. 3.I/O System TE (test): .MI-SY: missing by system ««HW missing .MI-SY: when no hardware is equipped .TE-ID: tape unit is detected to be faulty or prepared to be diagnosed by command DXSYS 13 .MI-SY: when no hardware is equipped or tape unit is not powered . CTU & MTU: .BL-SY: hardware is faulty and the disk drive is not in working condition .WO-ID: tape unit is online and tape is loaded . WDU & FDU: .WO-BU: normal operation state.WO-BU: normal operation.BL-SY: when hardware is equipped.WO-ID: all except user operations to the disk drive are prevented . tape file is opened and data can be stored on tape . VDU & LPT: .TE-AC: test active ««test is running MI (missing): .WO-ID: when the device is ONLINE 4.
DXSYS 14 .5 Logical files: 1. (not DX200 format) . List logical files: Displays all logical files of OMU that are connected to LPT-1: < ZIIL:.changes the data files to another format before storing it from the disks.I/O System §2. 2. §2.4 Units: 1.used in the data transfer of the FTAM protocol.OMU:DEV=LPT-1. VDS.MML programs and menus.back-up copies of files containing permanent or semipermanent data . Virtual Data Storage : .program blocks of different computer units . WDU. Hard disks contain for example: .
I/O System DXSYS 15 .
. LIST LOGICAL FILES CONNECTED TO GIVEN OBJECT C: . REMOVE LOGICAL FILE I: . Permanent logical files: . DISPLAY MENU D: ........5 Logical file type: Logical files are transit files between application programs and I/O devices .deleted immediately after the MML session is over DXSYS 16 . CREATE LOGICAL FILE P: .... Modify/change/delete the connections by a device: < ZII? ? . Semipermanent logical files: . LINK PHYSICAL DISK FILE TO LOGICAL FILE G: .....I/O System 2...... DISPLAY INFORMATION OF GIVEN LOGICAL FILE S: . Temporary logical files: .can change the connections .... 1.created and deleted by the user 3....... ..connections are stored on disk 2.. CHANGE OBJECT TO ANOTHER IN ALL LOGICAL FILES F: ..user cannot delete or change the name . CREATE SPARE LOGICAL FILE R: ....... RETURN TO MAIN LEVEL §2. CHANGE OBJECT CONNECTED TO LOGICAL FILE L: ... CHANGE SIGNALLED PROCESS Z.....
service. System software: . program blocks DXSYS 17 .The operating system (OS) is the software core and interfaced with the CPU.1 DX200 software: 1. .File Administration §3.Divided into three different levels: system.
File Administration 2.real time services .supervision services The processor time is allocated according to the priority of the process.processor time scheduling .message transfer . Operating system: The main services of the operating system (DMXRTE) can be divided into the following function groups: .handling of processes and process families . The main states of a process and possible changes between them. A Y TO I WAIT DXSYS 18 .
They are loaded into the RAM of the OMU during the MML session.2 DX200 file system: 1. .File Administration §3.Work files: are created and updated by the applications.MML program files: are stored on hard disks.Program code files: are used in the memory of the microcomputer units. and the backup copies are also on the hard disks. . An example of a ring file is the alarm history file.Ring files: are files where the new data is written on the top of the old data. . Configuration files are saved and actively used in the memory of the computer units. File types: DX 200 disk files can be divided into two main categories: data files and Software files. which can be modified with MML commands.Configuration files: contain network element specific data. Data files: . and they are used only in the memory of the computer units. DXSYS 19 . Ring files are stored on hard disks (WDUs) Software files: .
ASWDIR).File Administration 2. DXSYS 20 .g. CONVPR. MMDIRE. In the SCMANA subdirectory there is located e. Disk files: The main level on disk directory structure is the root directory. LFILES. SOMAFI file which stores all the information about created SW-packages. Under the package directories are stored all subdirectories which belong to the SW-package (BLCODE.
LFILES.contains the conversion programs which might be needed during a major SW update. when installing a change delivery. The system itself constructs the necessary directory and files for measurements. ASWDIR : .contains the program code files which are loaded to the memories of the microcomputer during the start up phase. the preprocessor code and data files.contains the back up copies of data files.contains the MML program code files. The master file of the system is MAFILE in the BLCODE subdirectory. DXSYS 21 . MML text files and menus. The MAFILE contains information about all the load modules within the SW build.File Administration (BLCODE. CONVPR : . Also. MMDIRE: . MMDIRE. LFILES : . CONVPR. BLCODE : . the CFLIST file is copied into the ASWDIR directory.can be used for storing macros. ASWDIR).
Disk file handling: The commands for disk file handling: ZIWX / ZIWY / ZIBC DXSYS 22 .File Administration 3.
File Administration DXSYS 23 .
File Administration DXSYS 24 .
File Administration DXSYS 25 .
When the unit is restarted. Loading concepts: Initial loading: . The source can be a hard disk or local memory (codes and files already residing in the memory) so the working unit of the same type. DXSYS 26 .3 Loading system and unit restarts: 1. The loading source is determined by the maintenance procedures or by user. Primary copy is needed in the case of configuration files. the load modules contain the program code and configuration files.File Administration §3.
means the updating of work files from the active unit. Warming is needed because of a hot stand-by system.If the target file does not exist when the loading is started. Loading sources: .Own unit DXSYS 27 . Warming: . the file is created with the same structure as the source file.The distribution is a transaction in which the modification of the data of one file is taken into the copies of the data concerned in the other units of the exchange.Primary unite the active unit . Distribution: . The distribution is carried out from the primary copy to the readonly copies. Spare is ³cold´ for units using n+1 redundancy because it is not known in advance which unit to replace. 2.Active unit of the same type .File Administration File loading: . Spare unit is always updated in the case of units which use 2n redundancy because the spare unit knows that there is only one unit which to follow.OMU hard disk (WDU) .
.. ..... ...... OPERATING SYSTEM COMMANDS COMMAND LANQUAGE UTILITIESR . .... TE to SP and TE to WO........ System: Recovery ? A B C D E I DX 200 SERVICE TERMINAL MAIN LEVEL COOMANDS: ...... WS-220 FILE TRANSFER UTILITY INITIAL NAME: 00BE 0000 00 00-MAN> CURRENT NAME: 00BE 0000 00 Session 2 Online Caps Lock Num User: Service terminal User: Reset button User: MML terminal Unit state change causes a restart in the following state change combinations: SE to TE.. MENU / HELP ANALYSER L .... SYSTEM MONITORING COMMANDS EXIT DEBUGGER SESSION T ... . . Restarts: Restarts can be caused by several different reasons.... SET/DISPLAY TERMINAL TYPE GENERAL INFORMATION W .... EXTENSION HANDLING DEFINE ENVIROMENT O ....File Administration 3.. (ZUSC) DXSYS 28 . REMOTE DEBUGGER HANDLING MEMORY AND I/O HANDLING S ............
HOT : Code and files are not loaded at unit restart.The types of unit restart (values for R-parameter): WRM (warm): Code and files are loaded at unit restart (default).File Administration 4. MIN (mini):The restart of the exchange is imperfect as only disk services and some parts of other service blocks are activated. This parameter can be used for example in change note installation. . DXSYS 29 . Restart type: Restart (Hot) with MML commands (ZUSU). Only the file buffers are reset.g. and the applications start from the beginning. DSK (disk): All initially loadable program blocks are loaded from the disk of the OMU. . TOT (total): All initially loadable program blocks and data files are loaded (default value) by using the normal sources. The data files whose checksums have changed or files which do not have a checksum are loaded. such as maintenance and file system.The alternative loading modes : OPT (optimal): Only the code whose checksum has changed is loaded (default). databases are not loaded. The mini restart should not be initiated for non-database units. E.
Files are loaded from the primary unit.File Administration . in the background. that is. IMM (immediately): All files are loaded immediately. Restart (Warm) with the reset button: The code is not loaded unless there is a checksum error.The file loading modes : VIRT (virtual): Files will be loaded virtually. Restart (Cold) by power cut: The code will be loaded from the disk. DXSYS 30 . and the data files are loaded from the primary unit. Cold restart can be initiated either for a unit or for the whole system.
File Administration 5. Unit states: DXSYS 31 .
File Administration 5. Unit states: DXSYS 32 .
File Administration 5. Unit states: DXSYS 33 .
File Administration DXSYS 34 .
File Administration DXSYS 35 .
1 Supervision & Maintenance in the DX 200 solution : DXSYS 36 .Maintenance §4.
line alarms) .Software alarms (=alarms detected by software) DXSYS 37 .Trunk circuit alarms (=ET alarms.Wired alarms (=hardware alarms) .2 Detection and collection of alarm : .Maintenance §4.
Each error ratio counter has two sides: one side for all events and one side for failed events.Alarms: can be cancelled in two ways: automatically by the alarm system or by a user with MML commands.Maintenance §4. (* / ** / ***) .Error ratio counters: are used for observing events that happen repeatedly. . DXSYS 38 .3 Types of alarms : .Disturbances(:are used for informing about temporary disturbance situations.Notices: are additional information about the situation in the exchange. . Notices and disturbances (*) do not require actions from the user.
Maintenance §4. Alarm system can be handled by the user with MML commands: < ZA? DXSYS 39 .4 Alarm system user interface : 1.
Alarms printouts: DXSYS 40 .Maintenance 2.