9130 MFS Evolution IMT User Guide

Alcatel-Lucent GSM

9130 MFS Evolution IMT

User Guide

MFS Document

User Guide

Release B11

3BK 21673 AAAA PCZZA Ed.14a

Status RELEASED

Short title MX MFS IMT UG

All rights reserved. Passing on and copying of this document, useand communication of its contents not permitted without writtenauthorization from Alcatel-Lucent.

BLANK PAGE BREAK

2 / 100 3BK 21673 AAAA PCZZA Ed.14a

Contents

Contents

Preface . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

1 Introduction . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 111.1 What Is the IMT? . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 121.2 Starting the IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13

1.2.1 Configure the Network Board . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.2 Install IMT Environment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 131.2.3 Connect IMT to MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2.4 Configure Web Browser . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141.2.5 Install the TightVNC Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 151.2.6 Start IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 17

1.3 Upgrade MFS IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.4 Basic IMT Concepts . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 20

1.4.1 MFS Access . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 201.4.2 MFS Maintenance . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

1.5 Using the GPRS Terminal Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.5.1 Alarm Summary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221.5.2 Menu Bar . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 22

1.6 Context Menus . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 281.7 Using the IMT Online Help . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1.7.1 Online Help Structure . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.7.2 Online Help Entry . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 301.7.3 Online Help for IMT Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 30

1.8 IMT Color Customization . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.8.1 Colors Available for IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 311.8.2 Customize the Appearance of the IMT . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 33

2 IMT Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 35

2.1 MFS Alarm Handling . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.1.1 View Alarm and Access Alarm Dictionary . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 362.1.2 Set Alarm Beeper . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 372.1.3 View Alarm History . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 37

2.2 Identify and Manage Faulty MFS Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 382.2.1 View Site Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.2.2 View Physical Equipment . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 392.2.3 View Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.2.4 Set Telecom Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.2.5 View Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 402.2.6 Set MFS Gateway . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.2.7 Set VLAN Configuration in MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 412.2.8 Ping Status . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.2.9 View GPUs IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 422.2.10 Set MFS GPU Telecom IP Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 432.2.11 View GPU Link to BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.2.12 View MFS Equipment Global Parameters . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.2.13 Set MFS Profile . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.2.14 Send BUI Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.2.15 View BUI Responses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 452.2.16 View BUI Requests . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.2.17 View GPRS Mib Usage . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 462.2.18 GPU Map . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 472.2.19 Switch Over Control Stations . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.2.20 Reset MFS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.2.21 Reset GPUs Linked to a BSS . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482.2.22 Display PCM-TTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49

3BK 21673 AAAA PCZZA Ed.14a 3 / 100

Contents

2.2.23 Check MIB Inconsistencies . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 492.2.24 Set Reachability IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 502.2.25 View Reachability IP Addresses . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 52

2.3 Managing Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.3.1 Types of Backup File . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 532.3.2 Back Up MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 542.3.3 Restore MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.3.4 List Backups of MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.3.5 Delete Backup of MFS Data . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 552.3.6 Reset Data for all GPUs . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56

2.4 Software Management . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.4.1 View Current Versions of MFS Software . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.4.2 Access the Software Component Version List . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 572.4.3 Install a New Software Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 582.4.4 Set Protected Version . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 58

2.5 Synchronize PCM-TTP . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.6 Extend to Two Shelves . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 592.7 Switch from 10 to 12 E1 Extension . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602.8 Gb Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2.8.1 Export Gb Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 602.8.2 Import Gb Configuration . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 60

2.9 Cold Restart . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.10 Administrative Tasks . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 62

2.10.1 View User Activity Log . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 622.10.2 Manage a User Account . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 64

2.11 Remote Inventory Information . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.11.1 Read Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 662.11.2 Write Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 672.11.3 Get No Remote Inventory . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 682.11.4 Update Remote Inventory Files . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 68

3 IMT Windows . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 693.1 Alarm History Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 703.2 Attributes of GPU Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 713.3 Attributes of MFS Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 733.4 Attributes of PCM-TTP Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 763.5 GPRS Terminal Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 783.6 GPRS Mib Usage View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 793.7 List of Alarms Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 803.8 MFS Alarm Detailed View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 813.9 MFS Set Attributes Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 823.10 MFS Subrack View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 843.11 Site View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 863.12 Telecom Parameters Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 873.13 Gateway View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 883.14 Gateway Set Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 893.15 Gateway Pinger Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 903.16 GPU View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 913.17 GPU Set Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 923.18 Reachability View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 933.19 Reachability Set Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 943.20 Vlan Config View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 953.21 Vlan Config Set Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 963.22 Condition Status View . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 973.23 View All Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 983.24 Sub-BSS View Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.25 Remote Inventory Data Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 993.26 No Remote Inventory Window . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 100


Tables

TablesTable 1: IMT Profile - FAD Correspondence . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 18

Table 2: Alarm Severities . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 21

Table 3: IMT Menu Options Availability . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 26

Table 4: GPRS Terminal Window Menu Items . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 27

Table 5: Context Menu Options . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 29

Table 6: Object Class . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 47

Table 7: Create User Dialog Box Description . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 65

Table 8: Attributes of MFS Window Characteristics . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 75


Tables


Preface

Preface

Purpose This guide describes how to use the IMT to maintain the MFS. It enables theIMT PC user to display alarms from the MFS and then identify particular MFSequipment related to the alarms. OMC-R users cannot access the alarmhandling functions. It also contains procedures for managing MFS data andsoftware. The guide also contains a description of all the IMT windows. Therecan be a maximum of eight IMT connected to the same MFS.

There are two GP board variants, JBXGPU (3BK 26857 AAAA) and JBXGP2(3BK 26857 ABAA) which are similar and which are referred as GP boardsinside the document.

Document Pertinence This document applies to release B11 of the BSS.

This document contains IP transport in the BSS related information. Thisfeature is available commercially from Release B11 MR2.

What’s New In Edition 14The following sections were removed from method:

3.24 Boards Firmware Upgrade Window

2.12 Firmware Upgrade

2.13 Check Firmware Status.Description improvement performed in section:

Ping Status (Section 2.2.8)

View GPUs IP Configuration (Section 2.2.9)

In Edition 13Improvement done in:


MFS Set Attributes Window (Section 3.9)

In Edition 12Improvement done in:

Vlan Config Set Window (Section 3.21)


Preface

Vlan Config View Window (Section 3.20)


2.13 Check Firmware Status.

In Edition 11The following sections were added:




In Edition 10The following sections were removed from method:




In Edition 09New section Set VLAN Configuration in MFS (Section 2.2.7) was created.

In Edition 08Improvement done in Set MFS GPU Telecom IP Configuration (Section 2.2.10)The following sections were added:




In Edition 07Description improvement in Synchronize PCM-TTP (Section 2.5) and ExportGb Configuration (Section 2.8.1).

In Edition 06Improuvement done in :Set Reachability IP Addresses (Section 2.2.24)

In Edition 05Improuvement done in :GPU View Window (Section 3.16)

In Edition 04Improvements done in:

Gateway View Window (Section 3.13)

Gateway Set Window (Section 3.14)

Gateway Pinger Window (Section 3.15)

GPU View Window (Section 3.16)

GPU Set Window (Section 3.17)


Preface

Reachability View Window (Section 3.18)

Reachability Set Window (Section 3.19)

GPRS Terminal Menus/Options Availability (Section 1.5.2.2)

Set Reachability IP Addresses (Section 2.2.24)

View Reachability IP Addresses (Section 2.2.25)

Ping Status (Section 2.2.8)

View GPUs IP Configuration (Section 2.2.9)

In Edition 03Improvement done in Menu Bar (Section 1.5.2)

In Edition 02This document contains information about the following new features:

Menu Tree (Section 1.5.2.1)

Sub-BSS View Window (Section 3.24)

Support of Windows Vista for PC LMTUpgrade MFS IMT (Section 1.3)

IP Transport in the BSSIdentify and Manage Faulty MFS Equipment (Section 2.2)

In Edition 01First official release of document for B11.


Preface

Audience This guide is intended for:

System support engineers

Operating personnel

Training department.

Assumed Knowledge The reader must be familiar with:

Alcatel-Lucent MFS O&M concepts

MFS functions and equipment

IBM-compatible PCs

Microsoft Windows XP/Vista operating system software.

10 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

1 Introduction

This section introduces you to the IMT and describes how to start the IMTand the basic concepts of its use.

3BK 21673 AAAA PCZZA Ed.14a 11 / 100

1 Introduction

1.1 What Is the IMT?The Installation and Maintenance Terminal (IMT) is the local or remote terminalof the MFS. The MFS is the Alcatel-Lucent platform for GPRS. The Installationand Maintenance Terminal (IMT) maintains the MFS by displaying alarms fromthe MFS, then identifying particular MFS equipment related to the alarms.There can be a maximum of two IMT connected to the same MFS

You use the IMT to maintain the MFS by:

Displaying and managing MFS alarms, then identifying particular MFS

equipment related to the alarms

Maintaining MFS equipment (reset boards, etc.)

Viewing and reconfiguring hardware

Software management

Modifying telecom parameters.

MFS equipment includes telecommunications, processing, and internal andexternal communications subracks.

12 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

1.2 Starting the IMTThis section describes how to install the IMT software, connect the IMT tothe MFS, and start the IMT.

1.2.1 Configure the Network Board

This procedure describes how to configure the network board of the IMT onthe internal network. The IMT’s internal IP address must be chosen between172.17.y.201 and 172.17.y.253,

Where y is:

3 if ATCA Shelf is in lower position

4 if ATCA Shelf is in upper position

The IMT’s IP address can be external too. But the network board can only beconfigured with the internal or external IP address at a time

On the IMT:

1. Connect as local Administrator.

2. From the Windows desktop select the following menu path:

Start -> Run

3. Enter the following command:control.exe netconnections

The "Network Connections" window opens.

4. Select ’Local Area Connection’ .

5. Right-click on ’Local Area Connection’ to display the context pop-up menuand select [ Properties ].

6. The "Local Area Connection Properties" window opens.

7. Select ’Internet Protocol (TCP/IP)’ or ’Internet Protocol Version 4 (TCP/IPv4)’from the list, depending of the operating system used.

8. Click on [ Properties ] .

The "Internet Protocol (TCP/IP) Properties" or "Internet Protocol Version 4(TCP/IPv4) Properties" depending of the operating system used, windowopens.

9. Select ’Use the following IP address’ frame.

10. Enter the IMT’s IP address in the ’IP address’ field.

11. Enter 255.255.255.0 in the ’Subnetmask’ field.

12. Click on [ OK ].

13. Click on [ OK ] in the"Local Area Connection Properties" window.

1.2.2 Install IMT Environment

Mozilla version 1.6 or higher must be installed on your computer.

To install the IMT environment:

1. Open Mozilla and enter the following URL in the ’location’ field:

3BK 21673 AAAA PCZZA Ed.14a 13 / 100

1 Introduction

For a remote connection to the MFS: http://x.x.x.x/configurationwhere x.x.x.x is the IP address of the MFS, for example:

http://139.54.74.200/configuration

For a direct connection to the MFS: http://172.17.y.x/configurationwhere x can be 3 or 4 depending on the active station and y can be 3 or

4 depending on the shelf where the MFS is installed. This represents theactive connection to the MFS.

The MFS Terminal Configuration files page opens.

2. In the MFS Terminal Configuration files page click on Java RuntimeEnvironment 1.6 to download this file, if it is not already installed on yourPC.

Save the file to disk and when the file is downloaded, double-click on itto launch the installation

During the installation accept the license agreement

Click on [ Finish ] to finish the installation.

Note: If Java Runtime Environment 1.6 is downloaded on the IMT, there isno need for any Java Plug-in to be installed.

1.2.3 Connect IMT to MFS

For a remote connection to the MFS, connect the network cable from the PCto the Hub/Switch of an existing network which is connected to the MFS.

For a direct connection to the MFS, connect the network cable from the PC tothe JAXSSW1 (position 7 on main ATCA, 3rd /4th shelf rear side), port ETH8

Verify the LED corresponding to the connection port is lit.

1.2.4 Configure Web Browser

For any web browser used, the following settings must be performed:

The disk space used for cache must be set to 0 MB

The web browser must be configured so that each time you access a page,

it will check for newer versions of the page, if such option is available

The web browser must be configured with no proxy for both type of

connection: local or remote.We describe two examples in the following sections.

14 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

1.2.4.1 Configure Mozilla Browser on PCTo configure Mozilla browser:

1. Open Mozilla and follow the menu path Edit -> Preferences

The “Preferences” window opens.

2. If the ’Advanced’ subcategories are not visible in the ’Category’ frame,double-click on the ’Advanced’ category to expand the list.

Configure cache 3. Click on Cache in the expanded list.

The Cache preferences panel allows to adjust the Mozilla disk cache.

4. In the "Set Cache Options" frame, for ’Compare the page in the cache tothe page on the network:’

Select Every time I view the page.

Configure proxy 5. Click on Proxies in the expanded list.

The “Proxies” panel opens.

6. Select the ’Direct connection to the Internet’ radio button.

7. Click on [ OK ].

1.2.4.2 Configure Mozilla Firefox Browser on OMC-RTo configure Mozilla Firefox browser:

1. Open browser and follow the menu path Edit -> Preferences

The “Preferences” window opens.

2. Select the Advanced tab.

Configure cache 3. Select the Network tab.

In the ’Cache’ area you can set the disk space used for the cache.

4. Set the value to ’Use up to: 0 KB of disk space for the cache’.

Configure proxy 5. Click on [ Settings... ] in ’Connection’ area.

The “Connection Settings” window opens.

6. Select the ’Direct connection to the Internet’ radio button.

7. Click on [ OK ].

8. Click on [ Close ].

1.2.5 Install the TightVNC Software

To install the TightVNC software:

1. Power ON the PC and log on.

2. Insert the CD-ROM containing the TightVNC software in the CD-ROM drive

3. Copy the TightVNC software on the local PC

4. Double click on windows-tightvnc-1.2.9-setup.exe to launch the installation

5. Click on [ Next ], then on [ Next ]

6. Select the folder where the VNC will be installed, then click on [ Next ]

7. If not already done, select the components to be installed:

TightVNC Server

TightVNC Viewer

3BK 21673 AAAA PCZZA Ed.14a 15 / 100

1 Introduction

Web pages and documentation.

8. Click on [ Next ]

9. Select the Start Menu folder where the shortcuts will be created


11. Select the additional tasks:

Associate .vnc files with TightVNC Viewer

Register TightVNC Server as a system service

Start or restart TightVNC service


13. Click on [ Install ]. Wait for the installation wizard to finish.

14. Click on [ OK ] to confirm the warning message

The "WinVNC: Default Local System Properties" window opens.

15. In the "WinVNC: Default Local System Properties" window

In the "Incoming Connections" area enter the password in the two

’Password’ fields:alcatel

Click on [ Apply ] then on [ OK ]

16. Click on [ Finish ].

16 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

1.2.6 Start IMT

If a remote connection on IMT PC must be established using TightVNC softwareand a Firewall is activated on the IMT PC the Firewall blocks the remote access.To allow remote connections you have to add the TightVNC Server in theFirewall exceptions list.

1.2.6.1 Start IMT on PCTo start the IMT:

1. Open Mozilla and enter the following URL in the ’location’ field:

For a remote connection to the MFS: http://x.x.x.x where x.x.x.x is the

IP address of the MFS, for example: http://139.54.74.200

For a direct connection to the MFS: http://172.17.y.x

Where :

x can be 3 or 4 , depending on which OMCP board is active

y can be:

3 if ATCA Shelf is in lower position

4 if ATCA Shelf is in upper position

When the IMT is opened for the first time on a PC, click on [ Start ] in theSecurity Warning window to start the application.

A new window asking "What should Mozilla do with this file?" is opened.

2. Select [ Open it with default application (JNLPFile) ] then, clik on[ OK ] .

3. The following default warning message is displayed:

Unauthorized access to this machine is strictly forbidden and

may be liable to legal proceedings.

The warning message can be modified at installation time so it can bedifferent from the one given above.

4. Click [ Ok ] to acknowledge the message.

The IMT software is started and the Terminal Login window opens.

5. Enter the appropriate user name and password in the ’Name’ and ’Password’fields. Depending on your login, the following profiles are provided:

Administrator

Operational

GPU

Basic.

The GPRS Terminal window opens.

1.2.6.2 Start IMT on OMC-ROMC-R users open the IMT without any password. The IMT is openedaccording to the OMC-R user FAD.

When the IMT is opened for the first time on a OMC-R:

3BK 21673 AAAA PCZZA Ed.14a 17 / 100

1 Introduction

Select ’None’ in the Proxy Configuration window and click on [ Ok ]

Click on [ Start ] in the Security Warning window to start the application.

IMT Profile FAD

GPU IMT CONF GPU FAD

Craft IMT CONF MFS FAD

Operational IMT ADMIN FAD

Admin IMT PLATFORM FAD

Table 1: IMT Profile - FAD Correspondence

The number of concurrent users supported by the IMT can be described as:

8 basic users

k basic users and (8-k) GPU users (k ranges from 0 to 8)

1 oper/admin/root user and 7 basic users.

Notice that oper/admin/root users are identical from the craft server’sperspective and no more than one user of these types is allowed at any time.

1.2.6.3 Concurrent usersThe number of concurrent users supported by the IMT can be described as:

8 basic users

k basic users and (8-k) GPU users (k ranges from 0 to 8)

2 admin sessions maximum possible within 8 (any user) at most

If there is an administrative connection attempt, no free slot available (and nomore than one administrative session is already connected), the less recentlyconnected GPU session, (or if there is no such session, the less recentlyconnected basic user) will be forced disconnected to free the needed slot.

A GPU or a basic user can get connected if one of the following conditions aremet:

There is more than one free slot available (within 8 possible users) and noadministrative user is connected

There is one free slot left available (within 8 possible users) and one

administrative user is already connected occupying one of those slots.

1.2.6.4 Exclusion managementThe CRAFT SERVER manages the exclusion feature, which is appliedexclusively to the administrative accounts. The exclusion is granted to oneuser connected and refused to the second one if already granted and notyet released.

The cases to manage (exclusion set of operations) are:

Reset MFS

18 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

Control platform switchover

Software change

Mib backup or restore

System patch installation

User account management.

If the CRAFT SERVER grants the exclusion, there is absolutely no warningto the operator.

If the CRAFT SERVER refuses the exclusion a popup message is displayedcentered, with the following:

Title: "Administrative rights exclusion management"

Message: Another IMT administrative session is performing an

operation with an exclusive execution right. The operation

you have requested is refused because It needs the exclusive

execution right to be released first.

When the [ OK ] button is clicked, the requested operation is given up.

3BK 21673 AAAA PCZZA Ed.14a 19 / 100

1 Introduction

1.3 Upgrade MFS IMT

The IMT software is installed on the MFS stations.The IMT software is updated on the MFS stations during installation/migration.

To open the IMT on the PC after migration from release B10 to B11, ensurethat the necessary prerequisites are met regarding the web browser version orJava environment..

1.4 Basic IMT ConceptsThis section describes various basic concepts of the IMT.

1.4.1 MFS Access

The IMT software can be accessed from either the IMT or the OMC-R. Thethree different user login profiles with the following rights:

Administrator: All possibilities offered to non-Alcatel-Lucent personnel.

Operational: The same rights as the administrator except for the usermanagement facilities.

GPU: For GPU boards management

Basic: For MFS consultation purposes only.

The functions and menu options available to the user depend on the accessand login. See Menu Bar (Section 1.5.2) for more information.

The MFS platform operates in two modes:

Site Mode

Configuration Mode.

When you start the IMT a login window appears. Enter your user ID andpassword. The GPRS Terminal window appears.

When you log in to the IMT you access the MFS platform in Site Mode. You canthen use the IMT to maintain the MFS by displaying MFS alarm informationand accessing facilities for handling the alarms.

Configuration Mode is reserved for Alcatel-Lucent personnel.

20 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

1.4.2 MFS Maintenance

When faults occur in the MFS equipment, alarms are generated and displayedin the GPRS Terminal window. You can then use the IMT facilities to identify theparts of the MFS equipment that are responsible for the faults.

1.4.2.1 Alarm SeverityAlarms are grouped into five severity levels according to the seriousness ofthe related faults. The table below describes the colors and the severity ofeach grouping.

Color Severity Description

Red Critical Immediate maintenance is required because animportant function has been lost.

Orange Major Prompt maintenance is required.

Yellow Minor Maintenance is required but can wait until later.

Blue Warning Maintenance information is available but no actionis required.

White Indeterminate An event has occurred and an alarm report isgenerated but no action is required.

Table 2: Alarm Severities

1.4.2.2 IMT DisplayThe IMT displays the alarms grouped according to the severity levels, so thatyou can prioritize the handling of alarms.

1.4.2.3 Hot Swapping EquipmentWhen the faulty equipment responsible for an individual alarm is identified, it canbe ’hot swapped’ without affecting the operation of the rest of the equipment.

For additional information, refer to 9130 MFS Evolution Maintenance Handbook.

3BK 21673 AAAA PCZZA Ed.14a 21 / 100

1 Introduction

1.5 Using the GPRS Terminal WindowThe GPRS Terminal window contains a menu bar for accessing IMT functionsand an area for viewing a summary of MFS alarms.

1.5.1 Alarm Summary

The MFS uses the GPRS Terminal window to display alarms summarizedin six lists. The first, the Main Alarm list, contains all the alarms that havebeen flagged.

The next five lists contain all the flagged alarms, broken down by severity:

Critical

Major

Minor

Warning

Indeterminate.

You can display all the alarms in the List of Alarms window (see View Alarmand Access Alarm Dictionary (Section 2.1.1) ), and you can display the detailsof a particular alarm in the MFS Alarm Detailed View Window (Section 3.8) .

When a new alarm is raised, an alarm icon is displayed next to the appropriatesublist. The icon is removed when you view the sublist window.

1.5.2 Menu Bar

In addition to the alarm display, the GPRS Terminal window contains a menubar. This provides access to menus for configuring MFS equipment andmonitoring its state, and viewing the equipment in relation to alarms.

1.5.2.1 Menu TreeFigure 1 shows the full GPRS Terminal menu tree. The menu path to a task isin bold. For example, to access the shelf 3 front Physical View item, followthe menu path:

View -> Physical View -> shelf_3 -> Front View

22 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

Menu Bar

Alarm

View

Tools

Backup/Restore

Software

Help

BUI Reception ViewSending ViewRequestQuit

Sound (only on PC)History (only on PC)

Site ViewPhysical View

Sub−BSSProfile

Switch OverReset MFSReset data of all GPU

SCMI TraceBoard Trace

User Management (only on OMC−R)Mib inconsistenciesGb Config

Telecom Parameters (only on PC)

GPRS Mib usage view

GPU Map

Update RI File

Set Protected Version

Data Backup/Restore

Software Management

Online HelpGPRS Terminal WindowAbout Installed SoftwareAbout

shelf_3shelf_4

Gateway

GPUReachability

ViewSet

BackupRestoreListDelete

MFS VersionSw component version list Software change

front viewback view

ViewSetPinger

Check Mib

ViewSet

ViewSet

Switch from 10 to 12 E1 extension

ExportImport

IP View

ViewSet

VLAN config

ViewSet

Conditions Status

View

Figure 1: GPRS Terminal Menu Tree

3BK 21673 AAAA PCZZA Ed.14a 23 / 100

1 Introduction

1.5.2.2 GPRS Terminal Menus/Options AvailabilityThe menus and options available depend on whether the user is assignedadministrator, operational or basic access rights, and whether the IMT isopened from a Windows PC or OMC-R. See the table below for a list of theoptions that are available.

Basic access rights allow the user to access the same menus as the operator,but are for consultation purposes only.

User rightsMenu Option

Admin Oper GPU Basic

Reception View X X X X

Sending View X X X X

Request X X - -

BUI

Quit X X X X

Sound X* X* X X*

History X* X* X X*

External Alarms -> Management X* X* - -

Alarm

External Alarms -> Configuration X* X* - -

24 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction



Site View X X X X

Physical View -> Shelf_3-> front view X X X X

Physical View -> Shelf_3-> back view X X X X

Physical View -> Shelf_4 -> front view X X X X

Physical View -> Shelf_4 -> back view X X X X

Telecom Parameters -> View X X X X

Telecom Parameters -> Set X X X X

IP view -> Gateway -> View X X - -

IP view -> Gateway -> Set X X - -

IP view -> Gateway ->Pinger X X - -

IP view -> Gateway->Reachability->View

X X - -

IP view -> Gateway->Reachability->Set

X X - -

IP view -> GPU -> View X X X X

IP view -> GPU -> Set X X X X

Sub BSS X X X X

Profile -> View X X X X

Profile -> Set X - - -

View

GPRS Mib Usage View

3BK 21673 AAAA PCZZA Ed.14a 25 / 100

1 Introduction



GPU Map X X - -

Switch over X X - -

Reset MFS X X - -

Reset Data of All GPU X X - -

Update RI File X X - -

SCIM Traces - only used underAlcatel-Lucent personnel supervision

X X - -

Board Traces - only used underAlcatel-Lucent personnel supervision

X X - -

Set Protected Version X X - -

User Management X** - - -

Extend to two shelves X X - -

Switch from 10 to 12 E1 Extension X X - -

Tools

Mib inconsistencies -> Check Mib X X - -

Gb Config -> Export X X - -

Gb Config -> Import X X - -

Backup/Restore

Data Backup/Restore X X - -

Software management -> MFSVersion

X X - -

Software Management -> SWcomponent version list

X X - -

Software

Software Management -> SoftwareChange

X X - -

Online Help X X X X

GPRS Terminal window X X X X

About Installed Softwares X X X X

Help

About X X X X

* : Only available on PC IMT. Not available on OMC-R IMT.

** : Only available on OMC-R IMT. Not available on PC IMT.

Table 3: IMT Menu Options Availability

26 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

1.5.2.3 GPRS Terminal Menu ItemsThe following table provides a brief summary of the menu items.

Use this menu item.. To...

BUI Access the gateway to Nectar to seelogs of requests and responses senteither by the execution of BUL files orvia this menu

Alarm Perform miscellaneous alarmmaintenance functions. Refer toMFS Alarm Handling (Section 2.1)for details.

View View MFS equipment and associatedalarm status.

Tools Manage the Control Stations andMFS database.

Backup/Restore Manage the backup and restore ofMFS data.

Software Management Manage the MFS software. Refer toSoftware Management (Section 2.4)

Help Access the online help.

Table 4: GPRS Terminal Window Menu Items

3BK 21673 AAAA PCZZA Ed.14a 27 / 100

1 Introduction

1.6 Context MenusContext pop-up menus are available by right-clicking in View windows. Thecontent of the menu varies according to the different View windows, theselected object, and the user login. It consists of a subset of options describedin the table below.

Option Description

Help Accesses the online help.

Physical view Displays a physical view of the selected resource.

View Displays attributes of selected object.

View all Displays a list of objects of the same type as selected object.

Alarm view Displays the alarm list associated with the selected object.

Subtree alarm view Displays all the alarms associated to the subtree built, taking the selectedobject as the root.

Alarm view for a given class Displays all the alarms associated to a class.

Lock Locks the selected component and allow its maintenance

Unlock Release a locked component to operational state

Reset Re-initializes a BoardUnit, CoolingUnit, MUX board or Power Supply Unit(reloads the software)

Reset data Resets the GPRS traffic stored on the selected GPU without affectingtelecom traffic - speech data is not affected.

Reset all Resets all the data, both GPRS and speech data, of the selected GPU. Thisresults in the loss of telecoms traffic.

Cold restart Performs a cold restart of the control station.

Clear Alarm Clears all alarm of a selected station

Read Remote Inventory Displays the remote inventory for the selected subrack.

Write Remote Inventory Writes the remote inventory for the selected subrack.

Get NO Remote Inventory Displays the no remote inventory and allows you to save the file to local disk.

Update Remote Inventory Updates the no remote inventory file on the local disk.

PMD activate Activates a Post-Mortem Dump (PMD) of all data when a GPU boardcrashes. When the IMT reboots, the GPU sends this data to the IMT.

PMD deactivate Deactivates a Post-Mortem Dump (PMD) of data for a selected GPU.

Switch over Switches over an active board to a standby board (redundancy).

Set attributes Enables modification of the attributes of the PCM-TTP boards.

28 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

Option Description

Display PCM_TTPconfiguration

Displays the PCM TTP configuration.

Update protected version Updates the GPU protected version.

Table 5: Context Menu Options

3BK 21673 AAAA PCZZA Ed.14a 29 / 100

1 Introduction

1.7 Using the IMT Online HelpThis section describes the structure of the IMT online help and how to navigatewithin it. The format of the information displayed for each of the IMT windows isalso described.

1.7.1 Online Help Structure

Online help for the IMT contains three parts, as shown in the table below.

This part... Describes...

Introduction The IMT and describes the basic conceptsof its use.

IMT Tasks The tasks you can perform with the IMT.

IMT Windows The windows displayed by the IMT.

1.7.2 Online Help Entry

Online help is provided for every window displayed by the IMT.

If a window has a menu bar, follow the menu path:

Help -> Online Help

1.7.3 Online Help for IMT Windows

The help information for each IMT window is presented in a standard format.

The first paragraph defines the purpose of the window in terms of theinformation and fields displayed, and lists the task procedures which use thewindow. You can click on a hypertext link to display each task procedure.

Next, a detailed description of every parameter and field displayed in thewindow is provided in table format.

30 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

1.8 IMT Color CustomizationThis section describes the color customization feature of the IMT. This featurecan be accessed only from the OMC-R.

1.8.1 Colors Available for IMT

The IMT has a limited color set in order to avoid interference with otherapplications. The number of colors available to the IMT can be divided intotwo groups:

Logical colors

Physical colors

The physical colors are sub-divided into:

Metal Theme ColorsThese colors define the ’Look and Feel’ of the IMT. They affect itemssuch as the active and inactive window borders plus the active andinactive title bars.

Extended Colors.These colors are defined as User colors. These colors are default valuesthat are associated with alarms and equipment depending on the state ofthe alarm and the equipment.

1.8.1.1 Physical Colors DescriptionThe table below describes the 16 colors defined as Physical Colors.

Metal Theme Colors Extended Colors

Name RGB Value Name RGB DefaultValue

Primary 1 102-102-153 Light coral 240-128-128

Primary 2 153-153-204 Orange 255-165-000

Primary 3 204-204-255 Yellow 255-255-000

Secondary 1 102-102-102 Cyan 000-255-255

Secondary 2 153-153-153 Wheat 245-222-179

Secondary 3 204-204-204 Mistyrose 255-288-225

Black 000-000-000 Red 128-000-000

White 255-255-255 Green 000-128-000

3BK 21673 AAAA PCZZA Ed.14a 31 / 100

1 Introduction

1.8.1.2 Logical Colors DescriptionThe Logical colors are used in association with the physical colors to representalarm and equipment states. The table below provides a description of theLogical Colors.

Name Default Value Description

FGCriticalColor Black Foreground Color.Critical Alarm.

BKCriticalColor Light coral Background Color.Critical Alarm.

FGMajorColor Black Foreground Color.Major Alarm.

BKMajorColor Orange Background Color.Major Alarm.

FGMinorColor Black Foreground Color.Minor Alarm.

BKMinorColor Yellow Background Color.Minor Alarm.

FGWarningColor Black Foreground Color.Warning Alarm.

BKWarningColor Cyan Background Color.Warning Alarm.

FGIndeterminateColor Black Foreground Color.Indeterminate Alarm.

BKIndeterminateColor White Background Color.Indeterminate Alarm.

FGNormalColor Black Foreground Color.Normal, no alarm.

BKNormalColor Wheat Background Color.Normal, no alarm.

FGNackColor Black Foreground Color.Nack counter area.

BKNackColor Mistyrose Background Color.Nack counter area.

FGLeftDetailedColor Black Foreground Color.Status Area.

BKLeftDetailedColor Mistyrose Background Color.

FGCleared Green Text Color.Cleared Alarm.

FGAlert Red Text Color.Alarm alert.

32 / 100 3BK 21673 AAAA PCZZA Ed.14a

1 Introduction

1.8.2 Customize the Appearance of the IMT

This feature is available only for the IMT on the OMC-R.

To edit or modify the appearance of the IMT, it is necessary to edit the textfile Customizelt.ini. This file exists on the OMC-R for one user only afterthe IMT is opened for the first time for this user. The file contains the defaultvalues for the Physical and Logical Colors described in Colors Available forIMT (Section 1.8.1) .

This file is located on the OMC-R in the directory: ~/alcatel/cfg where "~" isthe home directory of the OMC-R user.

Example: for the axadmin OMC-R user, the path is:/alcatel/var/home/axadmin/alcatel/cfg

You have two methods for customizing the appearance of the IMT.

1. Method 1 is to redefine the Metal Theme Colors.

To do this, change the RGB default value of the theme color.

For example, change the RGB value from 102-102-153 (Primary 1) to204-204-255 (Primary 3) to modify the color of the active window border.

2. Method 2 is to change the association between the logical color and thephysical color.

For example, set the BKNormalColor = wheat to BKNormalColor = green tochange the background color of an alarm in a normal state to green.

3BK 21673 AAAA PCZZA Ed.14a 33 / 100

1 Introduction

34 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2 IMT Tasks

IMT Tasks describes the tasks you can perform with the IMT.

3BK 21673 AAAA PCZZA Ed.14a 35 / 100

2 IMT Tasks

2.1 MFS Alarm Handling

OMC-R users cannot access the alarm handling functions.

The different ways alarm can be handled are described below.

Alarm Indication When the MFS generates an alarm the GPRS Terminal window is updated. Thenumber of alarms in the appropriate alarm sublist on the display is incrementedby one. Also, if it is not already displayed, an alarm icon appears next to thesublist.

Optionally, you can set a beeper to be sounded every time a new alarm is raised.

View Alarms You can view the details of the alarm. When you view the alarm it is automaticallyacknowledged to indicate that the alarm has been viewed.

Direct Access to theAlarm Dictionary

From the GPRS Alarm Detailed View window you can directly access theappropriate alarm description in the alarm dictionary.

This alarm description provides you with a structured method to handle thealarm and enables you to successfully complete a fault repair action.

See View Alarm and Access Alarm Dictionary (Section 2.1.1) for how to accessthe alarm dictionary.

Acknowledge Alarms When an alarm is acknowledged a flag is set in the IMT. Nothing is changed inthe MFS until the cause of the alarm is removed. This can be later when, forinstance, a repair action is completed.

The acknowledgment is local to the IMT. If a second IMT is connected to theMFS, its acknowledgment status for the alarm is unchanged.

Alarm History You can view a list of all the alarms generated by the MFS since the IMT terminalwas started in the Alarm History file.

2.1.1 View Alarm and Access Alarm Dictionary

To view an alarm and access its description in the alarm dictionary:

1. From the GPRS Terminal window double-click on the required alarm sublist.

The List of Alarms window opens.

2. Double-click on the required alarm entry.

The alarm is automatically acknowledged and the GPRS Alarm DetailedView window opens.

36 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.1.2 Set Alarm Beeper

To set a beeper to sound every time a new alarm is raised, from the GPRSTerminal window follow the menu path:

Alarm -> Sound

A check mark is placed next to the Sound item in the Alarm drop-down menu toindicate that the beeper has been set.

To disable the alarm beeper, repeat the previous operation. The check marknext to the Sound item in the Alarm drop-down menu is removed.

2.1.3 View Alarm History

To view the alarm history, from the GPRS Terminal window follow the menupath:

Alarm -> Alarms History

The Alarm History window opens, showing:

The number of the alarm

The date and time when the alarm was generated

The date and time when the alarm ended

The source object for the alarm

The identifier of the alarm

The type of alarm

The alarm severity.

3BK 21673 AAAA PCZZA Ed.14a 37 / 100

2 IMT Tasks

2.2 Identify and Manage Faulty MFS EquipmentYou can view the MFS equipment from a number of different perspectives.Each view indicates whether specific equipment is causing an alarm. Formore information about managing and viewing the MFS equipment, see thetable below.

To... Use...

Display racks, shelves, and slots View -> Site View

Display shelf slot allocations View -> Physical View

Display CM, NS, and TRANSPORTresources

View -> Telecom Parameters-> View

Modify CM, NS, and TRANSPORTresources

View -> Telecom Parameters-> Set

Display information related to the gateway(in case of Gb over IP)

View -> IP view -> Gateway ->View

Configure the gateway of the GPUs (in caseof Gb over IP)

View -> IP view -> Gateway ->Set

Display the IP configuration of the GPUsrelated to Gb over IP

View -> IP view -> GPU Config

Display global parameters View -> Profile -> View

Set MFS attributes View -> Profile ->Set

View the GPU boards that are linked to aBSS

View -> Sub-BSS

View the log of BUI responses BUI -> Reception View

View the log of BUI requests BUI -> Sending View

Switch over the control stations. The activeone will become standby and vice versa

Tools -> Switch over

Allows the administrator to restart the stationon the current mode

Tools -> Reset MFS

Check Mib inconsistencies Tools -> Mib incosistencies ->Check Mib

38 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.2.1 View Site Equipment

Purpose is to view the resources managed by Tomas agent "GHM" in a treeway. To view the MFS equipment in terms of racks, shelves/subracks, and slotsand their associated alarm indications:

1. From the GPRS Terminal window, follow the menu path:

View -> Site viewThe Site View window opens.

2. Expand the tree of the rack with an alarm to display its shelves/subracks.

3. Expand the tree of the shelf/subrack with an alarm to display its slots.

4. Expand the tree of the slot with an alarm to display its objects.

5. Select the required object, and right-click to display a context pop-up menu.

6. Select View or View All , as required, from the context pop-up menu:

To display the attributes of... Select...

LSN (SSW board) View

A, B (STATION A or B) View

PCM-TTP View

GPU View

MUX View

All objects in the same class View All

2.2.2 View Physical Equipment

To view the MFS equipment in terms of shelf/subrack slot allocations andtheir associated alarm indications:


View -> Physical view -> Shelf_3/Shelf_4 ->Front/Back ViewThe MFS Subrack View window opens.

2. Select the required object, and right-click to display a context pop-up menu.

3. Select the required alarm view option from the pop-up menu:

To view a list of all the alarmsassociated with the...

Select...

Object Alarms view

Subtree containing the object Subtree alarms view

Object type Alarms view for given class

3BK 21673 AAAA PCZZA Ed.14a 39 / 100

2 IMT Tasks

4. To view the details of one of the alarms in the list, double-click on therequired alarm entry.

The alarm is automatically acknowledged, and the MFS Alarm DetailedView window opens.

2.2.3 View Telecom Parameters

To view the CM, TRANSPORT, and NS resources managed by the NECTARGOM agent:


View -> Telecom Parameters -> View

The Telecom Parameters window appears.

2. Alternatively, click on the left and right arrows to navigate through the classes.

2.2.4 Set Telecom Parameters

The user must have Administrator rights.

To modify the CM, TRANSPORT, and NS resources managed by the NECTARGOM agent:


View -> Telecom Parameters -> SetThe Telecom Parameters window appears.

2. To set the information for a particular resource, select the appropriate classfrom the Class Selection menu. Alternatively, click on the left and rightarrows to navigate through the classes and modify them.

3. To validate the modifications, click on [ Apply ] .

2.2.5 View Gateway

To view the gateways configured on the GPUs:

From the GPRS Terminal window, follow the menu path:

View -> IP view -> Gateway -> View

The Gateway View window appears, displaying the following:

Gateway

Subnet mask

Subnet value

Host name -> the SGSN name.

Click on:

[ Help ] the on-line help is accessed

[ Close ] the window is closed.

40 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.2.6 Set MFS Gateway

To modify the gateway configured on the GPUs:


View -> IP view -> Gateway -> Set

The Gateway View window appears.

2. In the Gateway View window, enter:

Gateway, where the gateway is:

SGSN IP ENDPOINT address, if the GPU_Gb_Base_IP address andSGSN IP Address are in the same subnetwork

IP addresss of the router interface used for telecom traffic (must

belong to the subnetwork defined by the GPU_Gb_Base_IP), if theGPU_Gb_Base_IP address and SGSN IP Address are in different

subnetworks.

Subnet mask, the subnet mask of the SGSN IP EndPoint

Subnet value, the subnet value of the SGSN IP EndPoint.

3. To enable the gateway, select the check box from the left side of the window.

Several subnets can be defined, but make sure that only one gateway isenabled.

Note: By clicking on the [ RESET ] button, the view is refreshed withthe initial values.

4. To validate the modifications, press [ Tab ] key to exit from the editingfield, then click on [ Apply ].

Wait until the [ Apply ] button is active again.

5. Reset all the GPUs using the IP transport mode.

2.2.7 Set VLAN Configuration in MFS


View -> IP view -> VLAN config -> SetThe "MFS: <IP address> - VLAN CONFIG - SET" window opens.

2. In the "VLAN CONFIG - SET" window, select the required VLANconfiguration from the drop down list in the ’VLAN CONF INDEX’ field.

3. [ Apply ] the values are taken into account.

The following warning will appear:

The VLAN_CONF_INDEX modification will lead to a reset

of all GP’s. The port on the switch shall be correctly

configuration. Click Ok to proceed or Cancel.

4. Click on [ OK ].

5. Close the "MFS: <IP address> - VLAN CONFIG - SET" window.

3BK 21673 AAAA PCZZA Ed.14a 41 / 100

2 IMT Tasks

2.2.8 Ping Status

To check the accessibility to the gateway addresses, of a specific GPU:

1. From the GPRS Terminal window, follow the menu path: View -> IP view-> Gateway -> Pinger.The “GATEWAY PINGER VIEW” window appears,displaying the following:

GPU Logical Position: the GPU logical address

BSS name: the name of the BSS mapped on the GPU

Align Status: alignment status

2. In the “GPU Logical Position’ column, select the GPU.

An additional view appears, displaying the result of the ping command tothe gateway addresses.

2.2.9 View GPUs IP Configuration

To view the IP configuration on the GPUs:


View -> IP view -> GPU -> View

The "IP VIEW / GPU / VIEW" window appears, displaying the following:

BSS name: the name of the BSS mapped on the GPU

Gb Transport Mode: the Gb transport mode (FR or IP)

Bss Transport Mode: the Bss transport mode (TDM or IP)

GPU Logical Position: the GPU logical address

GB Addresses: the IP addresses of the GPU for GboIP

GSL Addresses: the IP addresses of the IPGSL link on MFS side.

Gch Addresses: the IP addresses of the IPGCH link used by a GPU

on the MFS side.

By clicking on:

[ Help ] the on-line help is accessed

[ Close ] the window is closed.

42 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.2.10 Set MFS GPU Telecom IP Configuration

When setting the configuration, take into account that:

The MFS will reserve a maximum of 30 GP address for

IPGSL_Base_Address_MFS

The MFS will reserve a maximum of 30 GP address forIPGCH_Base_Address_MFS

The MFS will reserve a maximum of 1000 TCP port for ipGchcBaseTcpPort

The IP addresses for IPGSL_Base_Address_MFS,IPGCH_Base_Address_MFS, GPU_Gb_Base_IP can be the same,but theremust not be any overlapping between the port ranges. Set ports as following:

GPU_Gb_Base_UDP: [63488..64512]

ipGslBaseTcpPort: [52624..52624]

ipGchcBaseTcpPort: [53248..54240]

ipGchuBaseUdpPort: [53248..53502]

To set the IP configuration on the GPUs, from the GPRS Terminal window,follow the menu path:

View -> IP view -> GPU -> Set

The "IP VIEW / GPU / SET" window appears, displaying the following:

Group Name Parameter name Description

GPU_Gb_Base_IP the base address ofthe local IP addressused to define theGb_IP_Address of eachGPU

GPU_Gb_Base_UDP the UDP port number ofthe GPU board for Gbover IP interface

GBoIP parameters

IPGB_SUBNET_MASK_MFS

the mask of the subnetwhere is allocatedthe range of MFSaddresses used for Gbtelecom protocols

3BK 21673 AAAA PCZZA Ed.14a 43 / 100

2 IMT Tasks

Group Name Parameter name Description

IPGSL_Base_Address_MFS

base address of thelocal IP address usedby the MFS to definethe IP address used bythe IPGSL on each GPboard

IPGSL_BASE_TCP_MFS

TCP port number usedto configure the TCPport number of each GPboard of the MFS forIPGSL interface

IPGCH_Base_Address_MFS

base address of thelocal IP address usedby the MFS to definethe IP address used bythe IPGCH protocol oneach GP board

IPGCHC_Base_TCP_MFS

base for the TCP portnumber used by eachGP board of the MFS forIPGCHC protocol. Thisbase is used to definethe TCP ports for eachPTU access

IPGCHU_Base_UDP_MFS

base for the UDP portnumber used by eachGP board of the MFSfor IPGCHU protocol

BSSoIP parameters

IPBSS_SUBNET_MASK_MFS

mask of the subnetwhere is allocated therange of MFS addressesused for IPGCH / IPGSLprotocol

Click on:

[ Apply ] the values are taken into account

[ Reset ] the view ie refreshed with the initial values.

Note: If the task was performed to change the existing GPU IP settings, forthe GPUs supporting the IP transport mode, a Reset_data must beperformed to take into account the new settings.If the task was performed to prepare the change of the transport modefrom FR to IP, the Reset_data is not mandatory at this step, the newsettings are taken into account when the IP transport mode is activated.

44 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.2.11 View GPU Link to BSS

This view shows the GPU boards linked to each BSS.

View -> Sub-BSS

From Sub-BSS view, users can reset all GPUs linked with a BSS (right clickon the BSS).

2.2.12 View MFS Equipment Global Parameters

To view the global parameters of the MFS equipment, from the GPRS Terminalwindow follow the menu path:

View -> Profile -> View

The attributes of the MFS are displayed in the Attributes of MFS window, asdescribed in Table 8 .

2.2.13 Set MFS Profile

To set the MFS profile (attributes):


View -> Profile -> SetThe Set Attributes of MFS window opens.

2. Complete the fields as required.

3. Click on [ Set ] to confirm the new attributes and close the window.

2.2.14 Send BUI Requests

To execute a BUL file:


BUI -> Request

The Request window opens.

2. In the ’Request’ area, enter the BUL file name.

3. Click on [ Send ] .

The BUL file is executed.

Click on [ Switch View ] to view BUI responses. Click again on [ Switch View ] toview BUI requests.

2.2.15 View BUI Responses

To view a log of all responses to requests sent when executing BUL files or viathe BUI menu, from the GPRS Terminal window, follow the menu path:

BUI -> Reception View

A log of the BUI responses opens.

3BK 21673 AAAA PCZZA Ed.14a 45 / 100

2 IMT Tasks

2.2.16 View BUI Requests

To view a log of all requests sent when executing BUL files or via the BUI menu,from the GPRS Terminal window, follow the menu path:

BUI -> Sending View

A log of the BUI requests opens.

2.2.17 View GPRS Mib Usage

To view the total number of object entries in the Mib and the number of alreadycreated objects, follow the menu path:

View ->GPRS Mib Usage

The GPRS Mib Usage window is displayed.

The defined object classes are presented in the following table.

Object Class Description

ADJCELLFORRESELECTION This class focusses on the cellreselection adjacencies related toGPRS functionality.

An object is created for each adjacentcell to the containing cell. It is usedto broadcast on the Air interface theajacent cells that may support theGPRS functionality.

BSS Represents a BSS network element.

BTSSITEMANAGER Represents the O&M functionalityrelated to aspecific BTS equipment.Its purpose is containment.

CELL Represents the O&M functionalityrelated to a specific cell within a BTSequipment

FRBEARER This class focusses on the bearerchannels parameters related toGPRS functionality.

GICGROUP This object defines the characteristicsof the GIC group.

46 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

Object Class Description

LAPDLINK This object defines the characteristicsof the LapdLink which representsthe logical connectivity betweenthe manager functionality for thepurposes of sending managementinformation and responses. TheLapdLink object maps the logicalconnectivity on to some physicalconnection. Different instances ofthe attribute in various objects mayall point to the same or separatephysical connections.

MASTERCHANNEL This object class defines thecharacteristics of the cell that arerequired when there is a masterchannel.

NSE This class focusses on the NSEparameters related to GPRSfunctionality.

NS-VC This class focusses on the NSVCparameters related to GPRSfunctionality.

POWERCONTROL This class focusses on the cell powercontrol parameter relateed to GPRSfunctionality.

PVC This class focusses on the PVCparameters related to GPRSfunctionality.

SGSNIPENDPOIN This class focusses on the SGSNIP endpoints parameters related toGPRS functionality.

Table 6: Object Class

2.2.18 GPU Map

Gives a BSS configuration overwiew.


Tools->GPU Map

The GPU Map window opens.The navigation from GPU logical configuration to GPU hardwareconfiguration is displayed.

Click on [ Close ] to close the window.

3BK 21673 AAAA PCZZA Ed.14a 47 / 100

2 IMT Tasks

2.2.19 Switch Over Control Stations

When you use this procedure the IMT connection is lost for approximately15 minutes.

To switch the platform over from the active Control Station to the standbyControl Station:


Tools -> Switch over

A confirmation dialog box opens.

2. Click on [ Yes ] .

The dialog box closes. The active Control Station automatically becomesthe standby, and the standby Control Station automatically becomes active.

2.2.20 Reset MFS

All ongoing GPRS calls are lost.

To reset the MFS:


Tools -> Reset MFSA confirmation dialog box opens.


The dialog box closes. The MFS automatically reboots.

2.2.21 Reset GPUs Linked to a BSS

This procedure can interrupt traffic if the BSS is unlocked. See the 9153Configuration Handbook for information on how to lock the BSS.This action is reserved for personnel who have Administrator rights.

This procedure lets you reset all GPU boards which are linked to a particularBSS.

When a reset GPU is performed and all of the following conditions are fulfilled:

LCS function is activated on the BSS

At least one GSL to the BSS is operational.Then the warning: LCS - if currently running on the BSS connected

to this GPU - could be interrupted for this BSS . is displayed.

To reset all data on the GPU boards linked to a BSS:

1. From the GPRS terminal window, follow the menu path:

View -> Sub-BSSThe Sub-BSS View window appears.

2. Select the BSS on which the GPU boards are to be reset.

48 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

3. Right-click to display a context menu.

4. Click on [ Reset_data ]

The GPU boards linked to the BSS are reset if all GPUs are in the correctstate.

5. Confirm the dialog box Do you really want to perform a reset_data

of all attached GPU? by clicking on [ YES ] .

The following warning will appear:

You will reset_data all GPU. WARNING: LCS - if currently

running on the BSS connected to this GPU - could be

interrupted for this BSS. Do you proceed anyway?

6. Click on [ YES ] to reset the GPU boards.

2.2.22 Display PCM-TTP

To display the PCM TTP configuration:


View -> Physical view -> Shelf_x ->front viewwhere x can be 3 or 4 depending on MFS configuration.

The Physical View window opens.

2. Select the required GP, and right-click to display a context pop-up menu.

3. Select Display PCM_TTP configuration to open the PCM_TTPconfiguration.

The attributes of the PCM_TTP configuration are listed in Attributes ofPCM-TTP Window (Section 3.4) .

2.2.23 Check MIB Inconsistencies

To check the MIB inconsistencies:


Tools -> Mib inconsistencies -> Check MibA confirmation window appears, warning that the check is in progress.

2. Wait for the check to finish.

A confirmation window opens giving the result of the check.

If errors are found, restore the last correct MIB.

3BK 21673 AAAA PCZZA Ed.14a 49 / 100

2 IMT Tasks

2.2.24 Set Reachability IP Addresses

Use the GPU Map (Section 2.2.18) to view the relation between logical GPUand hardaware GPU configuration, if needed.

To set reachability IP addresses configuration:


View -> IP View -> Reachability -> SetReachability IP parameters:

Parameter name Used by Where

REACHABILITY_TEST_ADDR_ O&M

Control station ’Reachability fromControl Platform’ area

REACHABILITY_TEST_ADDR_ TEL

Control station ’Reachability fromControl Platform’ area

REACHABILITY_TEST_ADDR_ TEL_GB

GP ’Reachability from GPU’- GBoIP area (columns2 and 3)

REACHABILITY_TEST_ADDR_TEL_BSS

GP ’Reachability from GPU’- BSSoIP area (columns4 and 5)

Depending on the topology:

All addresses are in the same subnet. There is only one cable between

MFS and the router:REACHABILITY_TEST_ADDR_O&M,REACHABILITY_TEST_ADDR_TEL,REACHABILITY_TEST_ADDR_TEL_BSS,REACHABILITY_TEST_ADDR_TEL_GB = The IP address of the routerinterface to which the MFS is connected

O&M and Telecom are in two different subnets. There are two cables

between MFS and the router:

REACHABILITY_TEST_ADDR_O&M = The IP address of the

router O&M interface

REACHABILITY_TEST_ADDR_TEL = The IP address of the router

Telecom interface

REACHABILITY_TEST_ADDR_TEL_BSS = The IP address of therouter in the Telecom interface

REACHABILITY_TEST_ADDR_TEL_GB = The IP address of therouter in the Telecom interface

No router is used. L2 network case:

REACHABILITY_TEST_ADDR_O&M = The IP address of the OMC

50 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

REACHABILITY_TEST_ADDR_TEL = The IP address of one SGSNor BSC

REACHABILITY_TEST_ADDR_TEL_BSS = The IP address of

the BSC

REACHABILITY_TEST_ADDR_TEL_GB = The IP address of the

SGSN.

2. In the ’Reachability from Control Platform’ area, set the following:

’REACHABILITY_TEST_ADDR_O&M’ - IP address to be used by theMFS for testing the access to the external network for O&M needs

’REACHABILITY_TEST_LABEL_O&M’ - Friendly name of the IP

address to be used by the MFS for testing the access to the externalnetwork for O&M needs

’REACHABILITY_TEST_ADDR_TEL’ - IP address to be used by the

MFS for testing the access to the external network for telecom needs.This reachability test is performed by the MFS control station on its

two ethernet links

’REACHABILITY_TEST_LABEL_TEL’ - Friendly name of the IP address

to be used by the MFS for testing the access to the external network

for telecom needs

’REACHABILITY_PERIODICITY’ - The periodicity (in seconds) of the

reachability tests done by the control station. The periodicity range valueis (20 - 3600). The default value is 60.

3. In the ’Reachability from GPU’ - GBoIP area (columns 2 and 3), set thefollowing:

’IP Address’ - IP address to be used by the GPU for testing the access

to the external network for Gb telecom needs. This reachability test isperformed by the GPU on their active Ethernet link.

’Friendly name’ - Friendly name of the IP address to be used by the GPUfor testing the access to the external network for Gb telecom needs.

4. In the ’Reachability from GPU’ - BSSoIP area (columns 4 and 5), set thefollowing:

’IP Address’ - IP address to be used by the GPU for testing the access to

the external network for IP BSS telecom needs. This reachability test isperformed by the GPU on their active Ethernet link.

’Friendly name’ - Friendly name of the IP address to be used by the GPUfor testing the access to the external network for IP BSS telecom needs

5. For renewing the data displayed from MIB, click on [ Reset ]

6. For give up all changed not applied and close the window, click on [ Close ]

7. Click on [ Apply ] then update window is still displayed until the checkis successful

3BK 21673 AAAA PCZZA Ed.14a 51 / 100

2 IMT Tasks

Upon successful checks, the NEP_PROFILE configuration is updatedand the window is closed.

If the check is not successful:

The window is still displayed, with a popup error message.

In the reception view, the TOMIX error package must give the field name,specific error and value entered in the output string.

When [ OK ] is clicked, the popup disappear and the faulty value is shownblinking in its box (the other entered or not changed values are still displayedas usual ); the blinking stops as soon as the cursor enters or updatesthe box (if possible).

Note: If the GPU reachability IP address is modified, the GPU board must bereset in order the new reachability IP address to be taken into accountby the GPU.

2.2.25 View Reachability IP Addresses

To view reachability configuration and statuses follow the menu path View -> IPView -> Reachability -> View from the GPRS terminal window.

The values are simply read from the NEP_PROFILE MIB.

The Description field is 15 characters long, to display the remaining charactersif needed, the cursor need to be put in the field or a moving bar can be usedto operate with the mouse.

There are two tables displayed:

Reachability from Control Platform

Reachability from GPU

There is only one operational button [ CLOSE ] which closes simply the window.

Note: A description of the parameters can be found in Set Reachability IPAddresses (Section 2.2.24)

52 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.3 Managing DataThis section describes the different tasks that enable you to back up, restoreand reset MFS data for all GPUs.

2.3.1 Types of Backup File

There are two types of backup files:

Manual backup file

Automatic backup file.

2.3.1.1 Manual Backup FileYou create the Manual backup file. Manual backup file names have thefollowing format:MFS[Num].MFSBackup_[SW Version].[name]:[date]:[time].gz

The following table describes the different parameters of a manually backed-upfile name.

Parameter Purpose

MFS[Num] MFS number on which the backup was performed.

[SW Version] MFS software version MFSXAZ[xxx]

[name] Name the user assigned to the file.

[date] Date of backup. Format equals: dd mm yyyy

[time] Time of backup. Format equals: 00 where 00 equals hours.

.gz File extension of backup file. This extension indicates thatthe file is archived.

You can perform the following tasks with manually backed-up files:

To... Use...

Create a new backup of MFSdata

Backup/Restore -> Data Backup/Restore-> Backup

Restore MFS data from abackup

Backup/Restore -> Data Backup/Restore-> Restore

Display a list of backups of MFSdata

Backup/Restore -> Data Backup/Restore-> List

Delete a backup of MFS data Backup/Restore -> Data Backup/Restore-> Delete

Reset all data on the GPUs Tools -> Reset data of all GPU

3BK 21673 AAAA PCZZA Ed.14a 53 / 100

2 IMT Tasks

2.3.1.2 Automatic Backup FilesThe automatic backup file is created by the IMT. Automatic backup file nameshave the following format:

MFS[Num].MFSBackup_[SWVersion].autobackup_[day]:[date]:[time].gz

The following table describes the different parameters of an automaticallybacked-up file name.

Parameter Purpose

MFS[Num] MFS number on which the backup was performed.

[SW Version] MFS software version MFSXAZ[xxx]

autobackup Indicates it is an automatic backup file.

[day] Day of backup. The first three letters of the day of thebackup are displayed. For example: mon if backup occurredon Monday.

[date] Date of backup. Format equals: dd mm yyyy.

[time] Time of backup. Format equals: 00 where 00 equals hours.

.gz File extension of backup file. This extension indicates thatthe file is archived.

Automatic backup files are stored on the IMT. The IMT automatically createsone backup file each day. The oldest automatic backup file is deleted uponthe creation of a new backup file.

Users can carry out the following tasks with automatically backed-up files:

Restore MFS Data. See Restore MFS Data (Section 2.3.3)

List Backups of MFS Data. See List Backups of MFS Data (Section 2.3.4)

Delete Backups of MFS Data. See Delete Backup of MFS Data (Section2.3.5) .

2.3.2 Back Up MFS Data

To make a new backup of MFS data:


Backup/Restore -> Data Backup/Restore -> BackupThe Backup dialog box opens.

2. Enter the backup file name.

3. Click on [ OK ] .

When the backup is complete, the Backup Done window opens. It showsthe backup file name, together with the date and hour of the backup. Theidentity of the MFS is included at the start of all backup file names.

54 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.3.3 Restore MFS Data

To restore MFS data from a backup:


Backup/Restore -> Data Backup/Restore -> Restore

The Restore window opens.

2. Select the file name of the backup you require.

3. Click on [ Restore ] .

The MFS data is restored.

All ongoing GPRS calls are lost.All ongoing CS calls are lost.LCS, if currently running, will be interuppted.

2.3.4 List Backups of MFS Data

To display a list of backups:


Backup/Restore -> Data Backup/Restore -> List

The Backup List Result window opens. Files are listed chronologically andaccording to the type of backup file, manual or automatic. See Types ofBackup File (Section 2.3.1) for a description of the types of backup files.

2. Click on [ OK ] to close the window.

2.3.5 Delete Backup of MFS Data

To delete a backup:


Backup/Restore -> Data Backup/Restore -> Delete

The Delete window opens.

2. Select the file name of the backup you want to delete.

3. Click on [ Delete ] .

3BK 21673 AAAA PCZZA Ed.14a 55 / 100

2 IMT Tasks

2.3.6 Reset Data for all GPUs

The GPU processor automatically reloads new data without interrupting any ofthe telecom processes. It is primarily used when migrating software.

To reset data for all GPUs:


Tools -> Reset data of all GPUA confirmation dialog box opens.


The dialog box closes and the GPU reloads.

56 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.4 Software ManagementThe table below describes the tasks for managing MFS software:

To... Use...

View current versions of MFSSoftware.

Software -> Software management-> MFS Version

Display the MFS software componentversion list.

Software -> Software management-> Software component version list.

Install a new software version. Software -> Software management-> Software change.

Restart an interrupted softwareinstallation.

Software -> Software management-> Software change.

2.4.1 View Current Versions of MFS Software

To view the current versions of MFS Software:


Software -> Software management -> MFS Version

The MFS Versions dialog box opens. Validated Version is the old MFSversion that is installed. Activated Version is the new (current) MFS versionthat has been installed. The MFS uses the activated version.

2. To return to the GPRS Terminal window, click on [ OK ] .

2.4.2 Access the Software Component Version List

To access the Software component version list:


Software -> Software management -> Software component version list

This displays a dialog box that contains the MFS software componentversion list

2. Click on [ OK ] to return to the GPRS Terminal window.

3BK 21673 AAAA PCZZA Ed.14a 57 / 100

2 IMT Tasks

2.4.3 Install a New Software Version

To install a new software version:


Software -> Software management -> Software change

A confirmation dialog box opens


The new Software version is created, installed and verified. A progressdialog box opens. It offers a choice between activating or uninstalling thenew version.

3. Click on [ Next ] to activate the new version of the Software.

The new version is activated. A progress dialog box opens. It offers a choicebetween starting up or deactivating the new version.

4. Click on [ Next ] to start up the new version.

The newly installed version is started up on the old standby station. The IMTdeletes the old version of the software. A dialog box opens. It declares thatthe Software change is complete.


The dialog box closes and the IMT terminal restarts.

2.4.4 Set Protected Version

To set the GPU protected version:


Tools -> Set protected versionA dialog box opens

2. Select the GPU protected version click on [ OK ] to confirm it.

3. Click on [ OK ] to close the confirmation window.

58 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.5 Synchronize PCM-TTPThe user can redefine PCM-TTP synchronization mode. Three modes areavailable:

YesThis mode synchronizes the PCM-TTP with the component that it is linked to.

NoThis mode does not synchronizes the PCM-TTP with the component thatit is linked to.

UnknownThe MFS selects whether the PCM-TTP synchronizes with the componentthat it is linked to.

1. To redefine the synchronization mode of a PCM-TTP board, follow themenu path:

View -> Site ViewThe site view opens.

Alternatively, users can follow the menu path:

View -> Physical ViewThe physical view opens.

2. Right-click on a PCM-TTP board to display a pop-up context menu.

3. Click on Set Attributes in the pop-up context menu.

4. Select the required mode from the drop down list in the ’Synchronizing’ field.

Help: When defining the synchronizing PCM-TTPs for the centralisedsynchronization mode, it is recommended to:

Select two PCM-TTPs that are not connected to the same LIU board

Select two PCM-TTPs that are not connected to the same BSC.

5. Click on [ Set ] .

2.6 Extend to Two ShelvesThis command allows the user to extend its shelf configuration from oneshelf to two shelves.

The menu option is available only if the current configuration is one shelfextendable. It is not available if the current configuration is two shelves or oneshelf not extensible.

To extend the configuration to two shelves:


Tools -> Extend to two shelves

The following message is displayed:

Do you really want to extend the platform to two shelves ?

2. Click on [ Yes ] to confirm the operation.

3BK 21673 AAAA PCZZA Ed.14a 59 / 100

2 IMT Tasks

2.7 Switch from 10 to 12 E1 ExtensionThis command allows the user to switch a standalone MFS in centralizedconfiguration mode from 10 E1/GP to 12 E1 /GP.

This command is executed only if all the following conditions are fulfilled:

MFS is in stand alone configuration

MFS is in centralized synchronization mode

PCM-TTP configuration is 10E1/GP

MUX version is at HTS 1.4.3 level (nE1oE software version is at least1.7.0.0).

To switch the MFS configuration from 10 to 12 E1/GP:


Tools -> Switch from 10 to 12 E1 extension

2. Wait for a control station switch over to complete the operation.

2.8 Gb Configuration

2.8.1 Export Gb Configuration

This command allows the user save the Gb configuration.

To export the Gb configuration:


Tools -> Gb Config -> ExportConfirm gb export? message is displayed.

2. Click on [ Yes ] to acknowledge the export.

Fast GB in progress... message is displayed.

Wait for the message Gb export successful. to be displayed

3. Click on [ OK ] to acknowledge the message.

4. The file containing the backup configuration is located in:

C:/alcatel/fastgb if the Terminal was opened from a local PC

~/alcatel/fastgb if the Terminal was opened from the OMC-R.

2.8.2 Import Gb Configuration

This command allows the user to recover the Gb configuration.

The import works only if current Gb configuration is empty.

To import the Gb configuration:


Tools -> Gb Config -> ImportFrom the "BUL File Chooser" window select the set_config_<mfsid>.bulfile.

Confirm <path>/set_config.bul’s date/hour gb import ? messageis displayed.

2. Click on [ Yes ] to acknowledge the import.

60 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

Fast GB in progress... message is displayed.

Wait for the message Gb import successful. to be displayed

3. Click on [ OK ] to acknowledge the message.

After the Import Gb Configuration action is finished check that the physicalcabling at the MFS site is done according to match the synchronization linksdeclared in the MFS.

3BK 21673 AAAA PCZZA Ed.14a 61 / 100

2 IMT Tasks

2.9 Cold RestartThis command allows the user to perform a shut down of the operating systemand application on the control station followed by a restart.

If the command is used on the active control station a switchover is performed.

To perform a cold restart:


View -> Physical View -> shelf_x -> Front Viewwhere x can be 3 or 4 depending on the used shelf.

2. On the front view right click on the control station and select cold restart .

2.10 Administrative Tasks

2.10.1 View User Activity Log

A log of IMT user activity is stored on the MFS.

To view the IMT User Activity Log, you have two options:

View User Activity Log from a Unix Station

View User Activity Log from a PC.

2.10.1.1 View User Activity Log from a Unix StationTo view the User Activity Log:

1. From Unix command window, enter the following commands:ssh -l rootsys [MFS floating IP address]Are you sure you want to continue connecting(yes/no)?yesrootsys@[MFS floating IP address]’s password:

Enter your password.

2. To access the log file you have to change the usersu

Enter the password for the new user.

You now have access to the active MFS Station.

3. Go to the directory: /omcxchg/IMTactivity to view the User Activity Log.

The User Activity log displays the following information:

Date

Time

Active Station

Name of User

IMT Login

Action Classification

Description of Action.

62 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.10.1.2 View User Activity Log from a PCTo view the User Activity Log from a PC:

1. Open a putty session

Complete the ’Host Name (or IP address)’ field with:

172.17.y.x for a local connectionwhere:

y is 3 for the lower ATCA Shelf

y is 4 for the upper ATCA Shelf

x is 3 for Station_A

x is 4 for Station_B

<MFS floating IP address> for a remote connection

In the ’Protocol’ area select

<Telnet> for a local connection

<SSH> for a remote connection

Click on [ Open ] to start session

Press [ Enter ].

2. Enter your username and password.

You now have access to the active MFS Station.

3. Go to the directory: /omcxchg/IMTactivity to view the User Activity Log.

The User Activity log displays the following information:

Date

Time

Active Station

Name of User

IMT Login

Action Classification

Description of Action.

3BK 21673 AAAA PCZZA Ed.14a 63 / 100

2 IMT Tasks

2.10.2 Manage a User Account

Note: This option is available only for the IMT opened from the OMC-R.

From the IMT Terminal, you can:

Create or modify a user account

Delete a user account.

Only users with Administrator privileges can manage user accounts. SeeTable 7 .

2.10.2.1 Create/Modify a User Account1. From the Tools Main Menu, click on [ User Management ] .

The MFS User Management window opens.

2. Click on the Create/Modify tab.

3. Complete the fields as described in the table below.

Field Description

User name Enter a new user name to create a new user account.The maximum length of the user name is eightcharacters.

Select a name from the drop down list to modify a useraccount.

Shell Enter the shell script for the new user. A shell scriptis proposed by default. You are advised to accept thedefault shell script.

Home directory Enter a home directory for the new user’s account. Adirectory is proposed by default. You are advised toaccept the default directory.

User rights Administrative / operational / basic rights assigned tothe user.

User ID User identification number. Display only field.

Group ID Identification number of the group to which the newuser belongs. Display only field.

Locked Checkbox selected means that the user account islocked.

Checkbox clear means that the user account is notlocked.

Synchronized You cannot modify this checkbox.

Checkbox selected means that the user account is thesame on the active and standby station.

Checkbox clear means that the user account is not thesame on the active and standby station.

64 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

Field Description

Password Enter the new user’s password here.

Re-enter password Re-enter the new user’s password here.

Min change time Minimum number of days between two passwordchanges.

The user is not allowed to change password duringthis period.

Max change time Maximum number of days between two passwordchanges

The user’s password will expire if it is not changed afterthis period.

Inact Number of days the between password expiration andaccount lock.

Table 7: Create User Dialog Box Description

When you change your password, you are advised to create a newpassword that contains the following:

A maximum of eight characters (letters, numbers, and special characters

included)

One capital letter

One number

Two of the following special characters:! $ % & / { } [ ] = ? \ @ + * [ > | , ; . : - ’ ^


2.10.2.2 Delete an User Account1. From the Tools Main Menu, click on [ User Management ] .

2. Click on the Delete tab.

A scroll down list of the user accounts on the IMT terminal is displayed.

3. Select the user account that you want to delete.


3BK 21673 AAAA PCZZA Ed.14a 65 / 100

2 IMT Tasks

2.11 Remote Inventory InformationRemote Inventory lets you read and write inventory information about MFScomponents such as:

Racks

Subracks

Boards.

Examples of information that you can read and write include:

Date that a board was put in service

Date of end of warranty for a piece of equipment

Date of last repair.

2.11.1 Read Remote Inventory

To display inventory information for a shelf or subrack and its associated boards:


View -> Site ViewThis displays the Site View window.

2. Select the appropriate shelf or subrack and right-click to display a contextmenu.

3. In the context menu, click on [ Read Remote Inventory ] .

This displays the dialog box: Remote Inventory Chooser.

4. Select the appropriate boards and click on [ Read Remote Inventory ] .

This displays the window: Remote Inventory Data Read.

See Remote Inventory Data Window (Section 3.25) for a description ofthis window.

66 / 100 3BK 21673 AAAA PCZZA Ed.14a

2 IMT Tasks

2.11.2 Write Remote Inventory

You must have Administrator rights to access this function.

To write inventory information about a rack, its associated subracks, shelvesand boards:



2. Select the appropriate shelf or subrack and right-click to display a contextmenu.

3. In the context menu, click on [ Write Remote Inventory ] .

This displays the Remote Inventory Chooser dialog box.

4. Select the appropriate boards and click on [ Write Remote Inventory ].

This displays a window: Remote Inventory Data Read.

See Remote Inventory Data Window (Section 3.25) for a description ofthis window.

5. In the R/W data tab enter data in the appropriate fields.

If you do not enter correct data in the fields, the system displays an errormessage.

6. Click on [ Apply ] to save the changes on the stations.

A confirmation window opens.

Click on [ Ok ] to close the window.

7. Click on [ Save ] to save changes to the IMT PC.

Select the path for the inventory file and click on [ Save ] .

If a remote inventory file exists a warning message is displayed.

Click on [ Ok ] to overwrite the file.

8. Click on [ Quit ] to close the Remote Inventory Data Read window.

3BK 21673 AAAA PCZZA Ed.14a 67 / 100

2 IMT Tasks

2.11.3 Get No Remote Inventory

To create a Remote Inventory file for modules/objects that do not have aRemote Inventory capability:



2. Select the appropriate rack and right-click to display a context menu.

3. In the context menu, click on [ Get No Remote Inventory ] .

This downloads a configuration file from the MFS directory omcxchg/rito the following directory:c:\alcatel\cfg

A status dialog box displays the progress of the download:Process of the data in progress...

When the download ends, the window: No Remote Inventory (read only)appears.

See No Remote Inventory Window (Section 3.26) for a description ofthe above window.

2.11.4 Update Remote Inventory Files

You must have Administrator rights to access this function.

To update the Remote Inventory on the control stations:


Tools -> Update RI FileWait for the confirmation message.

2. Click on [ Ok ] to close the confirmation window.

68 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3 IMT Windows

IMT Windows describes the windows displayed by the IMT.

3BK 21673 AAAA PCZZA Ed.14a 69 / 100

3 IMT Windows

3.1 Alarm History WindowUse the Alarm History window to view a list of all the alarms since the IMT wasstarted, as described in View Alarm History (Section 2.1.3) .

The table below describes the characteristics of this scrollable window.

Thisfield/button... Gives...

Index The unique number automatically assigned to an alarm.

Date & Time Begin The date and time when the alarm was raised.

Date & Time End The date and time when the alarm was ended.

Object Name The source object for the alarm.

Label Identifier.

Event Type The type of alarm:

Communication

Processing error

Quality of Service

Environment

Equipment.

Severity The level of alarm generated.

70 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.2 Attributes of GPU WindowUse the Attributes of GPU window to view the site attributes of a GPU, asdescribed in View Site Equipment (Section 2.2.1) .

The table below describes the characteristics of this window.

This field/button... Indicates...

creation_date Creation date in the format yy/mm/dd.

adm_upd_date The last time a configuration attribute wasupdated by the MFS system.

rack_number Rack number.

subrack_number Subrack number.

slot_number Slot number.

vendor_id Alcatel-Lucent company identifier.

serial_number Serial number.

version Version of the firmware on the board.

lock_request Yes = Request by operator to lock GPUboard.

No = Request by operator to unlock GPUboard.

failed_status Yes = Board failed, out of service.

No = Board in Service.

failed_comment Reason board is out of service.

logical_number Number computed by the GEM giving theapplication the board’s logical reference.This number never changes, even after aswitch over.

ifap_value The value identifies the Instance of aFunctional Access Point (IFAP) of the board.Nectar translates this value into an addressin it’s network so that the board can beaddressed.

pmd_activated Yes = Post-Mortem Dump (PMD) activated.

No = No active Post-Mortem Dump (PMD).

version_gpu Displays the MFS software version.

version_ne1oe Displays the ne1oe software version.

power_status Displays the board power status.

3BK 21673 AAAA PCZZA Ed.14a 71 / 100

3 IMT Windows


xpu_board_type GPU board type.

syst_upd_date Last time the system was updated.

operational_state Enabled = Board in service.

Disabled = Board out of service.

administrative_state Displays if the board is ’Locked’ or’Unlocked’.

procedural_status Not installed = the board is disabled and/orunavailable.

Not significant = the board is enabled andavailable.

availability_status This field displays additional informationabout the administrative and operationalstates. It displays two values:

Not installed

Not significant.

’Not significant’ is displayed when acombination of the administrative andoperational states make the availabilitystatus meaningless.

restart_number Displays the board’s number of consecutive,unsuccessful restarts.

creation_state Displays ’Not created’, ’Created’, ’Deleted’.

cfg_modif Updates the IMT with the configurationattributes.

ne1oe_ip_address Internal logical IP address of the board usedfor internal communication over ne1oe.

operational_state_ne1oe Displays the operational status for the ne1oe,enabled or disabled.

usage_state_ne1oe Displays the state of the ne1oe, active orstandby.

72 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.3 Attributes of MFS WindowUse the Attributes of MFS window to view the profile attributes of an MFS, asdescribed in View MFS Equipment Global Parameters (Section 2.2.12) .



creation_date The creation date in the format yy/mm/dd.


xpu_filename The boot file name for XPU board.

xpu_filename_old The boot file name for the B8 XPU board.

xpu_locavar The file name which contains a log ofanomalies for the GPU.

xpu_firmware The firmware file name for the GPU.

type_product MFS.

shelf_type_config Number of shelves

mic_type_synchro Reserved for future use.

phase Site, Configuration, or Configuration_Init.

protected_version SW version

vlanid0 VLAN 0 identity

vlanid1 VLAN 1 identity

checked_mib MIB checked: Yes/No.

spare_board_shelf Spare board shelf number.

spare_board_slot Spare board slot number.

ri_activation_time Displays the RI activation time.

version_datap Data patch version.

ipgbenimt Flag to enable/disable Gb views at IMT.

ipgbbaseaddress Base address of the local IP address used todefine the Gb_IP_Address of each GPU.

ipgbsubnetmaskmfs Mask of the subnet where is allocated therange of MFS addresses used for Gb telecomprotocols.

ipbssenbssoip Flag to enable/ disable BSSoIP views at forIMT.

3BK 21673 AAAA PCZZA Ed.14a 73 / 100

3 IMT Windows


ipgslbaseaddress Base address of the local IP address used todefine the IP address used by the IPGSL oneach GPU.

ipgchbaseaddress Base address of the local IP address used bythe MFS to define the IP address used by theIPGCH protocol on each GPU.

ipbsssubnetmaskmfs Mask of the subnet where is allocated therange of MFS addresses used for IPGCH /IPGSL protocol.

ipgbbaseudpport UDP port number of the GPU board for Gbover IP interface.

ipgslbasetcpport TCP port number used to configure the TCPport number of each GPU board of the MFSfor IPGSL interface.

ipgchbasetcpport Base for the TCP port number used byeach GPU boards of the MFS for IPGCHCprotocol.This base is used to define the TCPports for each PTU access.The same base isused by each GPU boards.

ipgchubaseudpport UDP port used by the IPGCHU protocol onMFS side by each GPU board.The same UDPport is used by each GPU boards

ipgchcpriority BSS internal priority used by the IPGCHControl flow in IP network.

ipgchubepriority BSS internal priority used by the IPGCH BestEffort flow in IP network

ipgchugbrpriority BSS internal priority used by the IPGCH GBRflow in IP network

p0layer2mappingmfs Defines the priority indicated in L2 protocol(e.g.ethernet), corresponding to the P0 internalpriority.

p0layer3mappingmfs Defines the priority indicated in L3 protocol(DSCP), corresponding to the P0 internalpriority.



74 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows






gprsaccessintvl Timer used to detect a non response from agateway.

gprsaccesstestcnt The test fails if no reply toGPRS_ACCESS_CNT test messageshave been received.

gprsaccesstestdelay Once an Ethernet port of the GPU is selected,at expiry of the delay, the periodic test of thegateways

gprsaccesstestperiod Each gateway is tested at expiry of this period.

oamvlanid Virtual LAN identifier used to tag the MFSinternal O&M traffic.

telecomvlanid Virtual LAN identifier used to tag the MFSinternal telecom traffic.

ipgslpriority BSS internal priority used by the GSL flow inIP network.

gbsignallingpriority BSS internal priority used by the MFS for theGb over IP data flow

variousippriority BSS internal priority used by the BSC for theDHCP, ICMP and ARP protocols in IP network.

gbdatapriority BSS internal priority used by the MFS for theGb over IP data flow.

spare [n] Provision for further use.

sys_upd_date Date and time

cfg modif Configuration mode

Table 8: Attributes of MFS Window Characteristics

3BK 21673 AAAA PCZZA Ed.14a 75 / 100

3 IMT Windows

3.4 Attributes of PCM-TTP WindowUse the Attributes of PCM-TTP window to view the site attributes of a PCM-TTP,as described in View Site Equipment (Section 2.2.1) .



creation_date The creation date in the format yy/mm/dd.


type_remote Remote equipment, BSC, TC, or SGSN.

remote_equipment The name of the remote equipment.

remote_port The identifier of the remote port on the samePCM link.

trunk_number The trunk number associated with the port.

synchronizing Synchronization of PCM-TTP(synchronization source for GPU):

Yes = Synchronizing

No = Not synchronizing

alarm_filter Alarm-Filter status: activated Yes/No.

fabric CMPS Distinguished Name of fabric objectlinked to PCM-TTP.

lock_request Not used. Ignore any displayed value.

multiplexing_scheme Three_one, four_one, or unknown.

liu_external_slot This field displays the LIU slot number

virtualmic Yes/No

syst_upd_date The last time the system was updated.

operational_state Enabled = in service.

Disabled = out of service.

administative_state Displays if the board is ’Locked’ or ’Unlocked’

76 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows


availability_status This field displays additional informationabout the administrative and operationalstates. It displays two values:

Not installed

Not significant.

’Not significant’ is displayed when acombination of the administrative andoperational states make the availability statusmeaningless.

crc4_status CRC4 status of the PCM-TTP.

cfg_modif Updates the IMT with the configurationattributes.

3BK 21673 AAAA PCZZA Ed.14a 77 / 100

3 IMT Windows

3.5 GPRS Terminal WindowUse the GPRS Terminal window to view a summary of MFS alarms and accessall the IMT facilities, as described in MFS Alarm Handling (Section 2.1) .


Thisfield/button... Lets you...

Sublist View the alarm sublists. Double-click on a specific alarmssublist to display the list of that type of alarm.

The six sublists and their associated screen colors are:

Main Alarm List - black

Critical - red

Major - orange

Minor - yellow

Warning - blue

Indeterminate - white.

Total See the total number of alarms in a sublist.

Nack See the number of alarms in a sublist that have not beenacknowledged.

Warning Icon See that new alarms have been raised since the sublistwas last opened.

BUI Configure and monitor MFS equipment.

Alarm Set a beeper to sound automatically when an alarm israised, to view alarm history file .

View View:

Alarms in relation to MFS equipment

NECTAR platform resources

GPU boards that are linked to a BSS

GPUs IP configuration

MFS gateway.

78 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows


Tools Switch over between active and standby MFS station

Reset MFS Station

Reset Data of all GPU

Update RI file

SCIM traces

Board traces

Set protected version

Extend to two shelves.

Backup/Restore Back up and restore MFS data, see the list of availablebackups and delete a backup from list.

Software View the current version of MFS software, to view theSoftware component version list, or initiate a softwarechange.


3.6 GPRS Mib Usage View WindowThe GPRS Mib Usage View window shows the number of created objects andthe maximum number of objects entries in the mib

This vindow is splitted out in two columns:

First column contains the object class name

Second column contains a progress bar indicating the objects occupancy.The number of already created objects and maximum number of objects areprinted on it.

3BK 21673 AAAA PCZZA Ed.14a 79 / 100

3 IMT Windows

3.7 List of Alarms WindowUse the List of Alarms window to list all the alarms in a specific sublist, asdescribed in the following sections:

View Alarm and Access Alarm Dictionary (Section 2.1.1)

View Physical Equipment (Section 2.2.2) .


This field/button... Lets you...

All List all alarms.

Critical List all critical alarms.

Major List all major alarms.

Minor List all minor alarms.

Warning List all warning alarms.

Indeterminate List all indeterminate alarms.

Index View the unique number automatically assignedto an alarm.

Date & Time View when an alarm was raised.

Object Name View Distinguished Name of the source objectfor an alarm.

Label Identifier.

Event Type View the type of alarm raised.

Severity View the severity level of the alarms.

Ack. Select an alarm in the list to acknowledge it.The acknowledgment is only local to the IMT.

Note: If the window is open when you select another alarm sublist in the GPRSTerminal window, the alarm list in the window is replaced by the new one.

The column width can be adjusted by dragging sideways the column separatorsbetween the headings.

80 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.8 MFS Alarm Detailed View WindowUse the MFS Alarm Detailed View window to view detailed information on aspecific alarm, as described in the following sections:

View Alarm and Access Alarm Dictionary (Section 2.1.1)

View Physical Equipment (Section 2.2.2) .



Event Type View the type of alarm raised.

Severity View the severity level of the alarm raised.

Alarm Label View the Identifier.

Additional Text View additional information.

Date Begin View when an alarm was raised.

Object Name View Distinguished Name of the source object for analarm.

Rack View the rack number.

Subrack View the subrack number.

Slot View the slot number.

Component 1 View additional fault source identifier.

Component 2 View additional fault source identifier.

Note: If the Detailed View window is open when you double-click on anotheralarm in the List of Alarms window, the alarm in the Detailed Viewwindow is replaced by the new one.

3BK 21673 AAAA PCZZA Ed.14a 81 / 100

3 IMT Windows

3.9 MFS Set Attributes WindowUse the MFS Set Attributes window to modify the profile attributes of an MFS,as described in Set MFS Profile (Section 2.2.13) .



xpu_filename The boot file name for XPU board.

xpu_filename_old The boot file name for the B8 XPU board.

xpu_locavar The file name which contains a log ofanomalies for the GPU.

xpu_firmware The firmware file name for the GPU.

ri_activation_time Displays the RI activation time.

ipgbenimt Flag to enable/disable Gb views at IMT.

ipgchcpriority BSS internal priority used by the IPGCHControl flow in IP network.

ipgchubepriority BSS internal priority used by the IPGCH BestEffort flow in IP network

ipgchugbrpriority BSS internal priority used by the IPGCH GBRflow in IP network







82 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows




gprsaccessintvl Timer used to detect a non response from agateway.

gprsaccesstestcnt The test fails if no reply toGPRS_ACCESS_CNT test messageshave been received.

gprsaccesstestdelay Once an Ethernet port of the GPU is selected,at expiry of the delay, the periodic test of thegateways

gprsaccesstestperiod Each gateway is tested at expiry of this period.

ipgslpriority BSS internal priority used by the GSL flow inIP network.

gbsignallingpriority BSS internal priority used by the MFS for theGb over IP data flow

variousippriority BSS internal priority used by the BSC for theDHCP, ICMP and ARP protocols in IP network.

gbdatapriority BSS internal priority used by the MFS for theGb over IP data flow.

3BK 21673 AAAA PCZZA Ed.14a 83 / 100

3 IMT Windows

3.10 MFS Subrack View WindowUse the MFS Subrack View window to view equipment in terms of boardallocations and associated alarms in subrack slots, as described in ViewPhysical Equipment (Section 2.2.2) .

The table below describes the characteristics of the front view window.


Help Access to Online Help

LogicalNumbering

Display slot logical address.

PhysicalNumbering

Display slot address (physical).

View GPname

Display the GPU name in the vertical slot.

View GPversion

Display the current version of the GPU in the verticalslot.

SHELF Display shelf/subrack number. Right-click on theSubrack area to display the context menu. See Table 5for a description of context menu options.

PVFAN Fan unit.

A, B OMCP (station) boards

LSN Display SSW (switch) board. Right-click on a slot tothe display the context menu.

GPU Display GPRS Processing Unit board. Right-click on aslot to the display the context menu. See Table 5 for adescription of context menu options.

Left-click on a board to display its associated ports.

Display Port Equipment Status. Select a GPU board tothe display the Port Equipment Status.

PORT Displays PCM port number and slot number.

A link between a PCM_TTP and a port indicates thatthe port is equipped.

PortEquipmentStatus

PCM-TTP

Displays PCM-TTP number. Right-click on thePCM-TTP area to display the context menu for viewingthe associated alarm lists.

Triangle Displays the alarm state of the board. The color of thetriangle indicates the alarm state of the board.

Clock See that the PCM_TTP is synchronizing.

Green trafficlight

See that the board is enabled.

84 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows


Red trafficlight

See that the board is disabled.

Informationsymbol

Indicates that GP board is not present.

"S" symbol Indicates the spare GP board

The table below describes the characteristics of the back view window.


Help Access to Online Help

Close Closes the window

LogicalNumbering

Display slot logical address.

PhysicalNumbering

Display slot address (physical).

JAXSSW Displays the SSW RTM

PVPEM Displays the power entry module

SMM Displays the shelf manager module

PC Displays the personality card module

Triangle Displays the alarm state of the board. The color of thetriangle indicates the alarm state of the board.

Note: The color of the slot indicates the highest severity alarm generated bythe board in the slot. See Table 2 for a description of the alarm severitylevels and colors.

3BK 21673 AAAA PCZZA Ed.14a 85 / 100

3 IMT Windows

3.11 Site View WindowUse the Site View window to view MFS equipment in terms of racks, subracks,slots and associated alarms, as described in View Site Equipment (Section2.2.1) .

The table below describes the characteristics of this scrollable window.

The field/button... Lets you...

Name View site, rack, subrack, slot, and board objects in treeform.

The following board object types are used:

Stations (A, B)

GPU

FAN (PVFAN)

PCM-TTP

LSN (SSW)

JAXSSW

MUX

Router.

Right-click on the object to display the context menu forviewing attributes (see Table 5 ) or getting Help.

For a subrack, you can also right-click for the physicalview (see Table 5 ).

For the GPU, you can also right-click to perform tasksavailable via the contextual menu.

Alarm View severity level or none (green) of alarms.

Alarm Synt. Display the color of the most severe active alarm.Acknowledged alarms are not used in calculating thesynthesis.

Admin. Display administrative status - Locked or Unlocked(icons).

Oper. Display operational status - Enabled or Disabled.

Avail. Display availability status - Not significant or Notinstalled.

Proc. Display procedural status - Not significant or Notinstalled.

Usage Display activity status - Busy or Idle.

86 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.12 Telecom Parameters WindowUse the Telecom Parameters window to view the CM, TRANSPORT, and NSresources managed by the NECTAR GOM agent as described in View TelecomParameters (Section 2.2.3) and Set Telecom Parameters (Section 2.2.4)

The following table describes the characteristics of this window.


Class Selection Select one the following resources:

CM

TRANSPORT

NS.

Left Arrow/Right Arrow Navigate between thedifferent resource windows;CM/TRANSPORT/NS.

Class Data Display the data for the resourceselected in the Class Selection.

Reset* Reset the data for the resourceselected to default settings.

Apply* Apply changes that you made toresource.

To File* Save changes to a file, rather thanapply them automatically.

Help Access the On-Line Help

Quit Exit the Telecom Parameters window.

* : Only Alcatel-Lucent personnel have access to this function.

3BK 21673 AAAA PCZZA Ed.14a 87 / 100

3 IMT Windows

3.13 Gateway View WindowUse the Gateway View window to view the information related to gateways:Rank, Gateway, Subnet Mask, Subnet Value and Host Name, as described inView Gateway (Section 2.2.5).



Close Close the window.

Rank Display the rank of the gatewayaddress.

Gateway Display the gateway IP address.

Subnet Mask Display the subnet mask of the SGSNIP EndPoint.

Subnet Value Display the subnet value of the SGSNIP EndPoint

Host Name Display the name of the SGSN.

88 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.14 Gateway Set WindowUse the GPRS Terminal window to manage the information related to gateways:Relevant, Rank, Gateway, Subnet Mask, Subnet Value and Host Name, asdescribed in Set MFS Gateway (Section 2.2.6).




Reset Refresh the data with values retrievedfrom the MIB.

Apply Submit and check the data entered.

3BK 21673 AAAA PCZZA Ed.14a 89 / 100

3 IMT Windows

3.15 Gateway Pinger WindowThe Pinger View manage the IP address of the GPU used to ping the gateway,as described in Ping Status (Section 2.2.8)




GPU Logical Position Display the logical position of GPU.

Bss Name The name of the Bss maped on theGPU.

Align Status Display the aligment status(aligned/misaligned).

Rank Display the rank of the gatewayaddress.

Gateway@IP Display the gateway IP address.

Host Name Display the name of the SGSN.

Ping Status Display the reachability of the host(IP gateway address) across the IPnetwork (enable/disable).

90 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.16 GPU View WindowUse the Gateway View window to view the information related to GPUs, asdescribed in View GPUs IP Configuration (Section 2.2.9).


Ports Display the following:

GB (IP Gb Base Address Port)

GSL (IP Gsl Base Address Port)

Gch Tcp (IP Gch Base Tcp

Address Port)

Gch Udp (IP Gch Base Udp

Address Port).

Subnet masks Display the following:

Gb subnet mask

Ater subenet mask.

Bss Name The BSS user label.

Gb Transport Mode The Transport Mode for GboIP.

Bss Transport Mode The Transport Mode for Bss.

GPU Logical position Display the logical position of GPU.

Gb Addresses Display the IP address used by aGPU board in a NSE instance.

GSL Addresses Display the IP address of the IPGSLlink on MFS side.

GCH Addresses Display the IP address of the IPGCHlink used by a GPU on the MFS side.

3BK 21673 AAAA PCZZA Ed.14a 91 / 100

3 IMT Windows

3.17 GPU Set WindowUse the GPU Set window to manage the information related to the IPconfiguration of the GPU for both GboIP and BssoIP, as described in Set MFSGPU Telecom IP Configuration (Section 2.2.10)






92 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.18 Reachability View WindowUse the Reachability window to view the information related to the reachabilityconfigurations, as described in View Reachability IP Addresses (Section 2.2.25)

This field/button... Displays...



Reachability from Control Platform The reachability for Control Stationover O&M and Telecom planes.

Reachability from GPU The reachability of GPU on GboIPand BSSoIP interfaces.

3BK 21673 AAAA PCZZA Ed.14a 93 / 100

3 IMT Windows

3.19 Reachability Set WindowUse the Reachability Set window to manage the information related to theReachability IP addresses and Label for configuration of the Control Platformand GPU (for both GboIP and BssoIP) as described in Set Reachability IPAddresses (Section 2.2.24)




Reachability from Control Platform Set the reachability for Control Stationover O&M and Telecom planes.

Reachability from GPU Set the reachability of GPU on GboIPand BSSoIP interfaces.



94 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.20 Vlan Config View WindowUse the VLAN Config view window, to view the information related to thevlan configurations.




VLAN_CONF_INDEX View the value of IP flow separation.

3BK 21673 AAAA PCZZA Ed.14a 95 / 100

3 IMT Windows

3.21 Vlan Config Set WindowUse the VLAN Config view window to set the information related to the vlanconfigurations, as described in Set VLAN Configuration in MFS (Section 2.2.7).




VLAN CONF INDEX Set the value of IP flow separation.



96 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.22 Condition Status ViewFrom the GPRS Terminal window, follow the menu path:View->IPView->Conditions Status->View to view the information related to theIP criteria condition status.

This field... Lets you...

GPU Level Criteria View the following:

GPU Logical Position

GPU Version

GboIP Status

GboIP Cause

BSSoIP Status

BSSoIP Cause.

Global Inputs View the following:

ipGbBaseAddress

ipGslBaseAddress

ipGchBaseAddress

VLAN Config

Relevant Gateway.

Mask Values View the following:

IpRouteReadyGBoIPMask

IpRouteReadyGBoIPMaskB10

IpRouteReadyBSSoIPMask.

VLAN Sparation Type VLAN_CONF_INDEX.

3BK 21673 AAAA PCZZA Ed.14a 97 / 100

3 IMT Windows

3.23 View All WindowUse the View All window to list information on all objects of the selected type,as described in View Site Equipment (Section 2.2.1) .


The field/button... Displays...

Title Bar Type of objects in list. The following are available:

Site View object types - rack, shelf/subrack, slot,GPU, SHMC, HUB/SSW, Fans, PCM-TTP, PEM,

MUX.

Telecom View object types - BSS, cell,

PDCHGroup, PowerCtrl, NSE, NSVC, FrBearer,

PVC, GicGroup, and LapDLink.

Name Name of the object.

Alarm Severity level or None (green) of alarms.

Alarm Synt. The color of the most severe active alarm(acknowledged alarms are not used in calculatingthe synthesis). See Table 2 .

Admin. Administrative status - Locked or Unlocked (icons).

Oper. Operational status - Enabled or Disabled.

Avail. Availability status - Not significant or Not installed.

Proc. Procedural status - Not significant or Not installed.

Usage Activity status - Busy or Idle.

98 / 100 3BK 21673 AAAA PCZZA Ed.14a

3 IMT Windows

3.24 Sub-BSS View WindowUse the Sub-BSS View window to view equipment that is linked to a particularBSS.

See View GPU Link to BSS (Section 2.2.11) for a description of how to viewthe Sub-BSS.

The following table describes the Sub-BSS View window.

This field... Lets you...

Sub-BSS Tree View the resources linked to the BSSin tree form.

3.25 Remote Inventory Data WindowUse the Remote Inventory Data window to view and write data about MFScomponents.

See Read Remote Inventory (Section 2.11.1) for a description of how to

view the Remote Inventory Data window.

See Write Remote Inventory (Section 2.11.2) for a description of how

to write to the Remote Inventory.

The following table describes the windows: Remote Inventory Data (read only)window and the Remote Inventory Data window.

This field/button Lets you...

Remote Inventory Display the slot number and name of the object selected.This field contains two buttons that enable you tonavigate between slots where more than one slot isactive on a board.

R/W data Displays data that can be modified. You must haveAdministrator rights to access this function.

Read only data Displays data that is read only.

Apply* Applies the changes you make to the data in the’R/W data’ field. Click on [ Apply ] before you displayinformation on another slot. Otherwise, the systemredisplays the old data.

Quit Close as the window.

Save Saves the data displayed to a file: reminv.txt .

* : You must have Administrator rights to view this button.

3BK 21673 AAAA PCZZA Ed.14a 99 / 100

3 IMT Windows

3.26 No Remote Inventory WindowUse the No Remote Inventory window to view the No Remote Inventory.

See Get No Remote Inventory (Section 2.11.3) for a description of how to viewthe No Remote Inventory.

The following table describes the properties of the No Remote Inventory (readonly) window and the No Remote Inventory window:

Field Description

NAME OF MODULES Name of the module, for example: Telecom Subrack1.

RACK Rack Number.

SUBRACK Subrack Number.

SLOT Slot Number.

MNEMONIC Short name for module.

PART NUMBER + ICS Number of the module and number of the ItemStatus Change.

SERIAL NUMBER Serial Number of the module.

FLASH EPROM ID Identification number of the Firmware part, includingthe software loaded on the board.

APPLY* Applies changes that you make to the No RemoteInventory.

Save Saves the inventory information displayed in thewindow.

Close Closes the window.

* : You must have Administrator rights to view this button.

100 / 100 3BK 21673 AAAA PCZZA Ed.14a

Documents

9130 MFS Evolution IMT User Guide