Académique Documents
Professionnel Documents
Culture Documents
2009-10-12
Prepared by
U
Subject Resp. Approved by
15892-891861 PFD
PFD/JHei
PFD
Page 1(8)
2009-10-12
U NetMaster
15892-891861
TABLE OF CONTENTS 1. 2. 3. 3.1 3.2 4. 5. 5.1 5.2 5.3 5.4 5.5 5.6 5.7 5.8 5.9 5.10 5.11 5.12 5.13 6. INTRODUCTION ............................................................................................................... 3 SOFTWARE VERSION HISTORY .................................................................................... 3 NEW FUNCTIONALITY..................................................................................................... 4 Inventory Management Reporting via Northbound Interface............................................. 4 Network Element integration changes/updates ................................................................. 4 ERRORS CORRECTED ................................................................................................... 4 KNOWN ISSUES............................................................................................................... 5 Maintenance Installation.................................................................................................... 5 Upgrade to current NetMaster release Permission settings ........................................... 5 Alarm Templates ............................................................................................................... 5 NetMaster displays blocked alarms for CityLink elements with older IDU firmware .......... 5 Limited client functionality during NetMaster server start-up phase .................................. 5 WiLink I SW Inventory ....................................................................................................... 6 Use of character set in element names ............................................................................. 6 Limitations on number of elements in NetMaster .............................................................. 6 Performance Measurements limitations ............................................................................ 6 NE handling in NetMaster during NE maintenance operations ......................................... 7 TCA not supported for Evolution Series ............................................................................ 7 Oracle database tuning issue for alarm list retrieval.......................................................... 7 Upgrade of large database ................................................................................................ 7 FURTHER INFORMATION ............................................................................................... 8
Page 2(8)
2009-10-12
U NetMaster
15892-891861
1. INTRODUCTION
This document describes changes and corrections in the software components of the NetMaster software.
Page 3(8)
2009-10-12
U NetMaster
15892-891861
3.2 Network Element integration changes/updates 3.2.1 Updated support for SmartPack series
SmartPack integration supports:
Network Element System configurations Supported hardware rev. Supported software rev. SmartPack Minipack, Flatpack2, Powerpack All 4.3, 4.2a and 4.1, SNMP version 2c
In general, it is recommended to avoid sofware versions older than 4.3, due to known functional limitations and communications capacity problems on the NE.
4. ERRORS CORRECTED
The current release addresses a number of issues. The most important ones are listed here. If required, further details may be requested via the CSS Help Desk.
Id 3541, 3556 3561, 3584, 3596 3603 Summary Weakness in alarm reconcile function, in some cases alarms were still incorrectly shown as active. Weakness in alarm reconcile function, in some cases alarms were still incorrectly shown as active. Slow opening of Historical Alarm reports, under heavy load the view fails to open due to timeout. Retrieval time reduction in R10M00 is appr. 30 to 80% (depending on actual data set) compared to R10L01. In extreme cases the Historical Alarms View may still fail if the retrieval takes more than appr. 7 minutes. If reading of PM resource capabilities on NE fails during discovery of NE, the system later fails if trying to collect PM data from these NEs. Weakness in alarm reconcile funtion, elements could become out of alarm synchronisation after connection problems combined with manual reset of element log. Applies to CityLink/InterLink Evolution Fixed in R10M00 R10M00
R10M00
R10M00 R10M01
Page 4(8)
2009-10-12
U NetMaster
15892-891861
5.1.2 Workaround
Uninstall the NetMaster client and then perform a new installation.
5.2.2 Workaround
Administrator must grant the user groups permissions to Configuration/Inventory Views using the User Group Administration view.
5.3.2 Workaround
None identified.
5.4 NetMaster displays blocked alarms for CityLink elements with older IDU firmware 5.4.1 Observations
NetMaster displays blocked alarms for CityLink elements with older IDU firmware. This is caused by a defect in the CityLink IDU firmware.
5.4.2 Workaround
Upgrade to IDU application code level higher than R3H00 solves the problem.
5.5 Limited client functionality during NetMaster server start-up phase 5.5.1 Observations
It is possible to login to the NetMaster client short time after a server start-up (or restart) has been initiated. However, it may take some time until all client functionality is enabled. The amount of time depends on the network size.
Page 5(8)
2009-10-12
U NetMaster
15892-891861
5.5.2 Workaround
Wait until message: System started in X minutes appears in the NetMaster Server log before attempting to use the client.
5.6.2 Workaround
Perform a manual SW Reconcile action for the elements in question.
5.7.2 Workaround
To avoid operator confusion and possible errors, it is recommended to use only international characters in element names.
5.8.2 Workaround
Consult Customer Support if system requirements exceed these limitations.
5.9.2 Workaround
None identified.
Page 6(8)
2009-10-12
U NetMaster
15892-891861
5.10.2 Workaround
Moving elements in or out of managed state during the period that a software download, element restart, or configuration backup/restore operation is taking place should in general be avoided.
5.11.2 Workaround
None identified. The error will be fixed in a software update in the future (contact Customer Support for availability info if TCA is used).
5.12 Oracle database tuning issue for alarm list retrieval 5.12.1 Observations
It has been reported that the response time for presenting alarm lists in NetMaster is not satisfactory in some cases. Investigations show that this may be related to incorrect tuning of the Oracle database, i.e. that database instance having too little memory.
5.12.2 Workaround
Use the Advisor General in Oracle Enterprise Manager to verify if too little SGA memory is causing the problem. The System Global Area should be 90% of total physical memory on the standalone database server. Further reading: For Oracle 11G systems, see: http://download.oracle.com/docs/cd/B28359_01/server.111/b28301/instance004.htm#insertedID3. For Oracle 10G systems, see: http://download.oracle.com/docs/cd/B19306_01/server.102/b25416/ch8.htm#i85390
Page 7(8)
2009-10-12
U NetMaster
15892-891861
5.13.2 Workaround
It is recommended to reduce the database size before the upgrade of large databases. This can be done by using the maintenance features to delete old alarms from the database before initiating the upgrade process.
6. FURTHER INFORMATION
For details on how to contact Customer Support see our web: www.neraworld.com.
Page 8(8)