E1/T1 Manager C7.0 (Build 7.0.9)

---

Copyright © 2009 Nokia Siemens Networks. All rights reserved.

Contents

Introduction
System Requirements
Compatibility
Installation
Uninstallation
Document Errata
Version History
Known Issues
Other Information

---

Introduction

This document provides some important information about E1/T1 Manager (referred to as "the Element Manager" or "the EM" hereinafter). Please read this (as well as the documentation for the Elements involved) through before using the Element Manager.

There is more detailed information also in the online Help of the Element Manager.

This Element Manager is used for managing the FXC E1/T1, FXC E1 and FC E1/T1 cards.

Back to Contents

---

System Requirements

In order to use the Element Manager, you need the following:

• Operating System (English versions):
• Microsoft Windows 2000 Server
• Microsoft Windows XP Professional
• Microsoft Windows 2003 Server
• Microsoft Windows Vista

The Element Manager does NOT officially support any other Windows Operating Systems.

• An Intel Pentium compatible PC:
• Processor: min. 300 MHz (recommended 500 MHz or more)
• Memory: according to installed operating system (preferably the recommended amount)
• Monitor: min. SVGA with 800x600 resolution (recommended 1024x768 resolution)
• Hard disk: 10 MB free space exclusively for the Element Manager installation (recommended 25 MB)
• Pointing device: mouse, trackball, touchpad or equivalent
• CD-ROM drive
• (local connection) 9-pin serial port in the PC
• (local connection) LMP cable (see more details in section Other Information)
• (remote connection) Network adapter with connection to DCN
• (optional) Windows compatible printer

Back to Contents

---

Compatibility

This Element Manager release is compatible with the following:

Item	Product Version	HW Version	SW Version
FXC E1/T1 Card	101 – 109	E36133.01 A0, B0, E0, E1, F0, F1, F2, G0	S36122.01 E0, F0, G0, H0
FXC E1 Card	101 – 109	E36123.01 A0, B0, E0, E1, F0, F1, G0	S36122.01 E0, F0, G0, H0
FC E1/T1 Card	101 – 105	E36113.01 D1, D4	C1
MetroHub Manager	-	-	C7.0 (build 7.0.9)
USBTS Hub Manager	-	-	C7.0 (build 7.0.9)
BTS Manager	-	-	CX6 CD2.0
GCS communication stack	-	-	4.2, 5.0, 6.0
NetAct	-	-	NetAct OSS4.1, NetAct OSS4.2

The Element Manager is a part of SiteWizard 6 CD4.0.

Back to Contents

---

Installation

You can obtain the Element Manager through SiteWizard CD-ROM or you can download it via https://www.online.nokia.com/SWD/: Software Delivery > Operations Support Systems > Element Management Products > SiteWizard.

To install the Element Manager, follow the instructions of the SiteWizard installation program.
The installation program should start automatically when the CD-ROM is inserted in the CD-ROM drive. If it does not start, run setup.exe from the CD-ROM manually.

If you received the Element Manager installation package as a compressed file (.zip), extract the zip file contents into some temporary directory in your hard disk. Then run setup.exe from the directory. After the installation is completed, you can delete the temporary directory and its contents.

The Element Manager files are installed into the directory you selected during the installation (referred to as "Installation Directory").

The Element Manager startup (shortcut) icon is added into the "Nokia Siemens Networks" folder.

The Element Manager executable "FXCE1T1Man.exe" is located in the Installation Directory.

To use connection services of the Element manager, GCS communication service (as per the compatibility chart above) must be installed.

Back to Contents

---

Uninstallation

To uninstall the Element Manager, follow the normal Windows application uninstallation procedure (from the Control Panel select Add/Remove Programs).
For more details, see the online Help of the Operating System.

NOTE: If you have saved some extra files (logs, configurations, etc.) to the Element Manager directory, those files and the directory will NOT be deleted. You need to remove them by yourself.

Back to Contents

---

Document Errata

There are no significant documentation updates.

Back to Contents

---

Version History

The Element Manager changes in release 3.1 are:

Features Removed

• D0 option shown in the Equipment dialog is removed when FC card is selected as FC has only B0 and C0 Versions.

Features Added

• EDGE Support Provided. Command line handling changed inline to the EDGE support requirement.
• Hubman is notified with newly activated node software Program ID and Version.
• Menu Prompt messages for Timeslot Monitoring, Circut Management and Trunet Interface Status.
• Message Box is Displayed in the timeslot Monitoring Dialog if the Node software version is lower than D0 as the command is not supported.
• Added Confirmation Message Box before Factory and Hardware Reset when Node Software Version is D0.
• Support for BTS Manager to connect in the Remote.
• Software Download Estimation time.
• Manager confirms before close.
• Diplay unit type in Timeslot monitoring and Reset dialog.
• CPU Reset counter.
• Trunet support.
• Restore factory defaults before sending indoor unit and commissioning & restore backup settings
• Factory reset to selected FEs with one command.
• HW reset to selected FEs with one command.
• Time slot monitoring (read).
• Circuit Management support in File Mode.
• Status bar functionality to show baud rate, type of connection and connection status
• Support for new file extensions (.nod, .xcs, .tmn).
• TFTP package check sum.
• Fault Recovery/ Retransmission during SW download.
• The information regarding the errors(like CRC/ Interrupts) during the SW download will be displayed in progress dialog during the download and a summary will be displayed in a dialog during the end of the software download.
• Support for Remote Transmission Manager in Remote MMI.
• Support for Direct FlexBus commissioning during XML commissioning by HubManagers.
• Support for High Density Radio.
• centering of Interface Loops dialog in the application main window.

Features Modified

• Identification Reading flag is set to false when Node software activated is different
• Alarm properties dialog updated with +5V,-5V supervision and 16MHz Pulse monitoring for FXC card.
• Sleep time increased after Management port speed is changed.
• The New Q1 EOC & Sync Bits/ Graphical View is taken from platform.
• Read Improvement optimization in MetroSite E1T1 Manager.
• New Alarms View is taken from platform which supports history from the node. The Alarms menu now consists of View option.
• The new manager options dialog is a tabbed dialog taken from platform.
• Maintenance menu is modified. Now the "Restore Factory Settings" and "Reset Unit Hardware" are moved under Maintanence->Resets.
• Tools menu modified. Shortcut to generate configuration report is added.

The Element Manager changes in release 3.2 (build 3.2.10) are:

Features Added

• It shall be possible to calibrate the free-run PDH node clock by management action, without the need to be locally present or to use an external measurement device.
• Q1 script tool can be launched from the manager.
• New Sync Functionality.

Features Modified

• File selection for SWDL
• Confirmation dialog is removed, which used to pop up after the severity change.
• Multiple selection in Alarm Properties dialog removed.
• It's possible to enter "," and "." in user notes with ITN C2.2 node SW.
• Unit software download - Software ID and version modification in EM. If inactive bank SW is 2.2 or higher and active bank SW is 2.1 or less.

Bugs Fixed

• Pronto# 4219ES11P : Q1 Switch settings are not sent by the E1T1Manager to the MS BTS when Send all is used.

The Element Manager changes in release 3.3 (build 3.3.3) are:

Bugs Fixed

• Pronto 10257ES11P : Cingular case with launching RRI and E1T1 Manager.

The Element Manager changes in release 4.0 (build 4.0.14) are:

Requirements implemented

• ITN_SysRqt0781 - controlled-slip events PM counter for external E1 or T1 interfaces.
• ITN_SysRqt0782 - line-code-violation events PM counter for external E1 or T1 interfaces.
• ITN_SysRqt0824 - TETRA support.
• ITN_SysRqt0764 - SW to be downloaded matches with the unit type prior to downloading it.
• ITNSysRqt0906 - Default settings to be same with Node SW.
• ITN_SysRqt0880 - User access levels to Element Managers.
• ITN_SysRqt0808 - Support of xml formatted files for backup of configuration data.
• ITN_SysRqt0943 - EM hides cryptic part of Circuit Manager created CC.
• ITN_SysRqt0951 - Support of Site ID as string and using Site ID to select node instead of Site Name.
• ITN_SysRqt0940 - Addition, modification support for nx8k CC.
• ITN_SysRqt0910 - same pilot bit within one node for different protected bi-directional cross-connects.
• Retransmission support while downloading a node software.
• New structures related to BTS Manager added.
• EM setups should clean the registry during uninstallation.

Features Removed

• None.

Features Added

• Statistics dialog shows controlled-slip events counter and line-code vialation events counter for E1 or T1 Interfaces.
• Manager allows connection to TETRA BTS equipment.
• Help updated.

Features Modified

• Software Download - File to downloaded will be verified against file format.
• COM port change - Number of selectable COM ports should be more than 4.

Bugs Fixed

• Pronto 12005ES08P : BTS Manager is not opened when E1T1Manager is closed.
• Pronto 5503ES05X : Connection to E1T1 Manager when opened from BTS Manager (CX4.1 build 4.0.4) is successful but on closing E1T1 Manager BTS Manager doesn't upon automatically.
• Pronto 7687ES11P : BTS Manager Hangs when Confirming Service Interface Settings.
• Pronto 8419ES11P : Differences between E1T1Man offline 'Alarm properties list' and specified values.
• Pronto 8679ES11P : Signal Quality Counters -reset for FXC E1 doesn't work with C2.0 node SW and Build 3.2.4 E1T1 Manager.
• Pronto 9122ES11P : MetroSite E1/T1 Manager alarm properties list errors.
• Pronto 9229ES11P : Site Name is not written to the E1 unit with Restore Settings.
• Pronto 5692ES11P : Severity state change of alarms - handled differently on different cards / different equipment .
• Pronto 8058ES11P : Inactive XC bank does not empty after HW Reset when Bridge in node.
• Pronto 9268ES11P : Trunet settings not stored in configuration file.
• Pronto 11562ES11P : Timeslot monitoring doesn't work.
• Pronto 9166ES11P : Loss of frame alignment (2M) when switching from Sync Input to another synchronization source.
• Pronto 2846ES08P : MHMan allows interfaces with pending CCs to be selected in timeslot monitoring even if they can't be read.
• Pronto 3076ES08P : Limitations in Configuration Report.
• Pronto 10659ES11P : 'Reset Signal Quality Counters' (FXC E1) resets also other counters.
• Pronto 12940ES11P : Help text for Summary of software download dialog is missing.
• Pronto 1-40255233 : RA-1247 :Error 'illegal Command' during commissioning of Metrosite.
• Pronto 12948ES11P : GUI: Q1-Management dialogs.
• Pronto 12898ES11P : Help button is missing from CC properties dialog.
• Pronto 12946ES11P : Extra space character in splash screen.
• Pronto 14886ES09P : Saving node settings with HubMan / USBTSHubMan fails.
• Pronto 2376ES11P : & Symbol not displayed in CC Bank.
• Pronto P234602 : Time stamp in the top of the alarm-view doesn't update when Refresh All is pressed.
• Pronto 9994ES11P : Q1 Ext connection does not recover after chainging speed.
• Pronto 1-54191373 : Combined 32K OMU&TRXSIG on TCH.
• Installation Problem related to GCS - Failure message changed.
• Pronto 13567ES11P : Synch not switching to Internal in E1/T1 Manager C3.3 for FC Unit.
• Pronto 13562ES11P : The synchronization window does not indicate if the synchronization switches to internal clock for FC E1/T1.
• Pronto 13558ES11P : Opening the Traffic manager fails in BTS Manager for FC E1/T1.
• Pronto 13557ES11P : The saving of the BTS commissioning report fails with FC E1T1.
• Pronto 3400D04 : E1/T1 Manager Help : default value of LMP and Q1 interface is not correct.
• Pronto 6019ES08P : E1/T1 Node Manager's UI is hanging.
• Pronto 9097ES11P : RSWDL of wrong software possible on FC-E1/T1 card.
• Pronto 2486ES11P : If rswl is tried with wrong sw to a FXC E1, the manager tries to do the swdl anyway.
• Pronto 12976ES11P : FXC E1 EM - Set to Factory Settings allowed when connected via Q1ext.
• Pronto 13722ES11P : Faulty data structure when sending Circuit Managent data - First char of site name overwritten.
• Pronto 13518ES11P : TETRA Commssioning - Loading a TETRA Node File does not work.
• Pronto 13962ES11P : The pending CC ´s and semi pending CC´s are not shown with the correct font and colout if a FXC unit is ripped out.
• Pronto 14110ES11P : Interface Type 'Unit' within FXC E1(T1) alarm properties.
• Pronto 4938ES03 : 140905 FXC E1T1 metroSite Q1 connection baudrate changes.
• Pronto 14872ES11P : Send all doesn't work E1T1Man.
• Pronto 14873ES11P : Factory reset is disabled after send all.
• Pronto 14868ES11P : Wrong info in E1T1Man status bar.
• Pronto 14803ES11P : Wrong version info in Print review.
• Pronto 15047ES11P : UALC feature does not prohibit remote modification of system although feature installed and enabled.
• Pronto 14546ES11P : FXC E1/T1 - SW activation without the question to confirm the activation.
• Pronto 15066ES11P : Problems with E1T1 manager 4.0.8 with node file handling of FXC E1C2.0 release.
• Pronto 15060ES11P : FC_E1T1 node file not compatible with new E1T1 manager 4.0.8.
• Pronto 14785ES11P : Unexcpected error message comes out if you cancel SW download.
• Pronto 15096ES11P : Manager crashes during software download to old FXC E1.
• Pronto 15123ES11P : Message 'Invalid file' when software download to old FXC E1 is tried.
• Pronto 14957ES11P : All Tools->Options settings are not saved when exit.
• Pronto 15040ES11P : Element Manager always tries to connect to COM1.
• Pronto 15379ES11P : "Manager crashes when upgrading FXC E1(T1) unit SW from C2.0 to C3 LR11".
• Pronto 15529ES11P : Embedded E1/T1 manager starts in read-only mode in file-mode.

The Element Manager changes in release 4.1 (build 4.1.2) are:

Requirements implemented

• ITN_SysRqt0962 - Harmonized PM data view of E1/T1 , STM-1 and RRI
• ITN_SysRqt0922 - A user shall be informed if there are inconsistencies between the cross-connection data represented towards the user via Element Manager and the actual cross-connection data at the ITN/FC STM node. If a inconsistency occured user shall be able to upload the cross-connection data from the ITN/FC STM node to re-establish consistency

Features Removed

• None.

Features Added

• Help updated

Features Modified

• None

Bugs Fixed

• Pronto# 15440ES11P : Node Managers do not fullfil ITN_SysRqt0951
• Pronto# 14735ES11P : Site Identifier restricted to alphanumerical strings
• Pronto# 5694ES11P : Sorting alarms in Alarm States Window only possible for RRI Manager
• Pronto# 1-98532062 : SiteWizard 4.15 CD1.0 makes wrong settings in system path
• Pronto# 1-70382471 : Node Manager server PATH incorrect after sitewizard 4.1 installation

The Element Manager changes in release 5.0 (build 5.0.9) are:

Requirements implemented

• ITN_SysRqt0787 : Polling of Alarms in a separate thread.
• ITN_SysRqt0967 : Full Loop Wizard(Undo the code for LoopWizard).Pilotbits check box functionality should be developed.
• ITN_SysRqt0922 : A user shall be informed if there are inconsistencies between the cross-connection data represented towards the user via Element Manager and the actual cross-connection data at the ITN/FC STM node. If a inconsistency occured user shall be able to upload the cross-connection data from the ITN/FC STM node to re-establish consistency.
• ITN_SysRqt0309 : Remote change of Q1 NE address and baudrate.
• ITN_SysRqt0977 : Node status report
• ITN_SysRqt0978 : Part of Node Status report(ITN_SysRqt0977) : generation of the customer report from one dialog, excluding ability to cancel
• ITN_SysRqt0773 : Save the PM data in a text file for further analysis
• COMITN_xxx : Change of Version number of the EM to C5. Internal version to be changed to 5.0

Features Removed

• None.

Features Added

• Help updated

Features Modified

• None

Bugs Fixed

• Pronto# 18401ES11P : E1/T1 Manager not able to download SW if the active SW does not support retransmission.
• Pronto# 18470ES11P : Wrong Version in node report.
• Pronto# 18397ES11P : Error Window by opening 'statistics history' for FXCE1.
• Pronto# 17100ES11P : Export of alarm history in file contains only deactivation dates, activations dates are missing.
• Pronto# 15592ES11P : Changing the Q1 address or speed is not possible with a remote connection.
• Pronto# 197391385 : Disabled Q1 port settings.
• Pronto# 19961ES11P : DBus 13 doesn't work.
• Pronto# 19778ES11P : Local SW download to FC E1/T1 in MS BTS not possible.
• Pronto# 15793ES11P : MetroSite node file restore may fail due to corrupted communication parameters.
• Pronto# 20395ES11P : Can not modify the new EOC via remote connection.
• Pronto# 20530ES11P : Sync Priority is changed after activating inactive CC bank.
• Pronto# 20766ES11P : Set PDH Node to factory defaults command is not sent by nodemanager in some cases.
• Pronto# 21516ES11P : wrong interface names for FXC E1 Unit, if restored from backup file via MetroHub Manager.
• Pronto# 21250ES11P : Pending and blocked cross-connection information is missing from CC-view.
• Pronto# 21152ES11P : Text missprinted in Action section of enhance Error Handling.
• Pronto# 20733ES11P : Non Combined OMU SIG can be allocated over TCH.
• Pronto# 21243ES11P : TS0 Fixed Bits are not displayed correctly.
• Pronto# 21869ES11P : Slightly different naming conventions for PM history export files.
• Pronto# 21666ES11P : USBTS EM: Inconsistency between graphical view and list view of Cross Connections.
• Pronto# 19220ES11P : Restore of backup settings failed.
• Pronto# 21650ES11P : Problem at creation of Uni_Directional CC in FC-STM1 EM.
• Pronto# 20274ES11P : Error in CC-overview dialog.
• Pronto# 34017ES09P : Company name incorrect in splash screen.
• Pronto# 22307ES11P : Protecting ABIS on SDH interface is shown as CHAIN in Traffic Manager. Necessary Information Missing".

The Element Manager changes in release 6.0 (build 6.0.8) are:

Requirements implemented

• C3CD2_2 : Automatic timeslot monitoring refresh
• C3CD2_1 : Measurement/Display of internal +5V/-5V
• C3CD2_21 : Reduce remote communication time
• C3CD2_28 : Resource conflict checking
• C3CD2_23 : Improvement of Alarm Logging File
• C3CD2_26 : Alarm Rationalization (phase 2)
• C3CD2_12 : Re-branding UI to Nokia Siemens Networks style
• C3CD2_5 : A new Unit should enable to upgrade a complete node to the new SW status : All / Activating the software : remaining : to be completed for IT4

Features Removed

• Resource Conflict Checking

Features Added

• None

Features Modified

• None

Bugs Fixed

• Pronto # P223E02 : It must not be allowed to change the severity of alarms with the severity warning
• Pronto # 5838C02 : Duplicated softkeys for menues in E1T1 Manager
• Pronto # 5836C02 : Softkeys are not working properly in dialogues of Metrohub manager
• Pronto # 5839C02 : Installation setup window is not named properly
• Pronto # 5830C02 : Softkeys are not working for menu in FXC RRI, FXC E1T1, FXC STM1 manager
• Pronto # 5837C02 : Logo is not properly oriented on the GUI
• Pronto # 8878ES05X : Controls in TS Monitoring do not get enabled when same TP is used in an active as well as in a pending CC
• Pronto # 6223C02 : E1T1 Delete Signal for OMUSIGTRXSIG1 is not working properly
• Pronto # 6198C02 : US,MH:Manager is not able to handle conflict for TRXSIG on TCH
• Pronto # 14052ESPE01 : The +5/-5V unit measurement values are displayed incorrectly in the node status report
• Pronto # 13645ESPE01 : E1/T1 Manager does not accept valid FC E1T1 SW file
• Pronto # 6186C02 : E1T1,RRI:Disabled OK button on RRI&E1T1 MGR in file mode
• Pronto # 15321ES11P : E1T1 manager started from BTS manager with MS delivers pointless error message with service interface
• Pronto # 9318ES05X : TRX numbers used in EDAP are displayed under the title 'Traffic Manager' in Traffic Manager window
• Pronto # 9411ES05X : BTS Manager hangs when attempted to delete multiple conflicts
• Pronto # 6043ESPE06 : Cross connection mismatch window occurs unexpected
• Pronto # PR9471ES05X : MH US_EMA Manager crashes when deleting a conflicting signal from a imported file
• Pronto # 9611ES05X : SW activation is not happening via SW upgrade dialogue
• Pronto # 9581ES05X: USMGR OK button is enabled on Traffic Manager when conflict is present
• Pronto # 9474ES05X: US_EMA Conflict is not getting detected for imported files
• Pronto # 6044ESPE06: MH Manager crashs when protected XC condition bit values are selected
• Pronto # 8983ES05X: Resource Conflict is not indicated when 8k CC is created on even numbered bit
• Pronto # 15055ESPE01: Traffic Manager allows Invalid configurations
• Pronto # 9793ES05X: US/MH: Manager crashes when imported .abs file (Dbus).

The Element Manager changes in release C7.0 (build 7.0.8) are:

Requirements implemented

• Migrated the Help from Win Help to chm format.
• Look & Feel of the EM will be as per the look & Feel of the respective OS.

Features Removed

• None.

Features Added

• Windows Vista Support

Features Modified

• None

Bugs Fixed

• None

The Element Manager changes in release 7.0 (build 7.0.9) are:

Requirements Implemented

• “Nokia Siemens Networks” folder shall be in ‘Start’ menu instead of ‘Start->Programs’ menu.

Features Removed

• None

Features Added

• None

Features Modified

• None

Bugs Fixed

• None

Back to Contents

---

Known Issues

The following issues are known for this Element Manager version:

• None currently

Back to Contents

---

Other Information

Product codes for some of the products:

Product	Code
LMP Cable	CS 72451.01 / T55270.01
SiteWizard 6 CD4.0 (via NOLS)	471919A.105
SiteWizard 6 CD4.0 (CD-ROM)	471918A.105

Pentium is a trademark of Intel Corporation.

Windows Vista, Windows 2000, Windows 2003 and Windows XP are registered trademarks of Microsoft Corporation.

Other products may be trademarks or registered trademarks of their respective manufacturers.

© 2009 Nokia Siemens Networks. All rights reserved.

Nokia Siemens Networks operates on a policy of continuous improvement. Therefore we reserve the right to make changes and improvements to any of the products described in this guide without prior notice.

Nokia Siemens Networks is not responsible for any loss of data, income or any consequential damage howsoever caused.

Back to Contents