OMS V9.5.16 Release Note

******************************************************************
OTN Management System Release Notes August, 2013

******************************************************************
OMS v9.5 build 9.5.16
Copyright (c) 2013 OTN Systems n.v.
******************************************************************
This text file provides late-breaking and version-related
information you should know about in this version of OMS. Please
read it before proceeding and keep it as a FAQ repository.
--------
CONTENTS
--------
1. PRODUCT DESCRIPTION
2. INSTALLATION
3. VERSION HISTORY
4. FIXED AND VERIFIED DEFECTS
5. KNOWN BUGS, LIMITATIONS, AND WORKAROUNDS
6. FIRMWARE - LOADWARE VERSIONS
7. MISCELLANEOUS
******************************************************************
1. PRODUCT DESCRIPTION
******************************************************************
OTN Management System, short OMS, is the Microsoft Windows XP
Professional SP3 (32bit) based network management system developed
for the OTN (Open Transport Network) by OTN Systems NV. OMS can
also be used with , Windows server 2008 Standard R2 64 bit,
Windows 7 Professional SP1 (32 bit en 64 bit), Windows 8
Professional (32 bit and 64 bit).
Remark: OMS does not support 32-bit character language sets.
OMS provides the facilities to configure the OTN subnetworks in
a communication network, and to monitor and log the behavior of
the network.
******************************************************************
2. INSTALLATION
******************************************************************
=====================
HARDWARE REQUIREMENTS
=====================
See OMS User Manual 2.1
==============
INSTALLING OMS
==============
Follow the steps in the OMS User manual 2.3 to install OMS v9.5.
Make sure you have administrator rights on your Windows machine.
Remarks :
- The "Computer Browser" service should be running when using OMS.
This is necessary for Microsoft SQL server.
When using Windows server 2008, the service "Computer Browser" is
disabled by default. Please set this service to start automatically at
startup of your PC.

===================================
INSTALLING JAVA RUNTIME ENVIRONMENT
===================================
THIS IS ALSO MANDATORY !!
If not yet installed the OMS installation program will
automatically install JRE
The JRE installer is available on the OMS DVD under
01.Setup\ISSetupPrerequisites.
Proceed in the same way during the install procedure : click
<Next> when asked, and choose a location (or accept the
default location).
OMS v9.5 requires JRE 7 update 21. If you have an older version,
please de-install this version first before installing the new one.
OMS v9.5 also does not support higher JRE versions.
When the following warning appears:
OMS Warning 5439490
Initialisation failure
Communication with one or more server(s) failed
it can be that the wrong Java Runtime environment version has been
installed.
In the <oms path>\bin\ostartgui.cmd file, the default installation
path e.g.
@start "OMS GUI" "C:\Program Files\Java\jre7\bin\java" -Xms256m -Xmx512m -jar OG
ui.jar
is filled in. When the java 7 update 21 is installed in a different
directory please change the path in order to start up the GUI correctly.
=========================
INSTALLING ACROBAT READER
=========================
Acrobat Reader X (10.0.1) is not automatically installed during setup but
is available under the <oms path>\Programs\Acrobat Reader.
You need this program (or another version) to browse the OMS
documentation.
===============================
SET-UP OF THE OMS CONFIGURATION
===============================
Perform the configurations as described in the OMS User
Manual 3.1 and 3.2 or refer to the tutorial in the OMS
user manual.

Remarks:
* In case of an OTN2500 network remember to enter the IP
-address of the BORA2500 in the hosts-file:
- <WINNT-dir>\system32\drivers\etc\hosts
- e.g. 220.220.220.10 BORA2500
* For X3M networks the subnetmask of the network interface card should
be 255.255.0.0
* For X3M networks please fill in the following
parameters in the OMS.cfg file found under <oms path>\config\oms.cfg:
- X3M_multicast=
- VPNMULTICASTHOST=
with the IP address of the network interface card of the PC that
is connected to the OTN-X3M network
========
PCANDIS
========
The PCANDIS driver is needed when connected to a BORA in an
OTN-Classic network.
The universal protocol driver that OMS uses to communicate with the
network interface card i.e. PCAsp50.SYS version 5.50.18.5
(for Windows XP/2008/7) is a different version as of OMS V5.4.
This version will NOT work with lower OMS versions (<OMS V5.4)!
To connect with the new version of PCANDIS again, no .bat file has to
be excecuted anymore.
For Windows 64-bit another version is needed PCAsp50a64.sys
===================
START-UP OMS SERVER
===================
Sometimes during startup of the OMS server following message can
appear: Hostname lookup returned localhost (127.0.0.1). This
indicates that the protocol stack has been rebuild. You can ignore
this message.
In case you have a large database it can happen that during startup
of the OMS server, the poller starts before the OMS kernel has been
successfully started. You can avoid this by enlarging the value of
the timer in the boot sequence::
- open the OMS Console
- via Edit - Options - OMS - Boot Sequence you can enter a
larger value in the Delay (ms) column.
=============
UPGRADING OMS
=============
Take the existing configuration information as an example for the
new configuration settings, but do not simply copy the old files
over the new ones.
If upgrading from an old version (< OMS 7.0), you won't be able to
keep using your database as is. Check out the upgrade procedure for the
database migration actions in the next paragraph.
Important remark on upgrading OTN-X3M subnetworks from OMS version < v6.1:
--------------------------------------------------------------------------
Before upgrading your X3M network from OMS version < v6.1 to OMS v9.5
please contact the OTNSystems helpdesk (services@otnsystems.com).
They will advise you on the way to handle it!
The BORA cards will need new firmware which is NOT compatible
with previous OMS versions.
==================
DATABASE MIGRATION
==================
*****************************************************
1. SQL database (From OMS v7.x -> Latest OMS Version)
*****************************************************
When migrating from OMS 7.x to OMS v9.5, you can keep using your old SQL
database. See OMS User Manual 8.10.2 for more information.
***************************************************************
2. .db database (From OMS v[2,3,4,5,6].x -> Latest OMS Version)
***************************************************************
This procedure can be applied to upgrade a vx.y database towards a v9.5
compatible database.
As the OMS databases created before v7.0 are not compatible with
databases from OMS v9.5 or future releases, it has to be re-generated.
This can be done without disturbing the operational services.
This can be done in three ways:
1. save of the subnetwork (recommended)
2. real migration
3. real migration when using H264 cards
These methods will be subscribed in the following text. Please
follow all the steps carefully.
---------------------------
2.1. SAVE OF THE SUBNETWORK (recommended)
---------------------------
With this method you retrieve information on the configuration and
the services from the subnetwork so you have to be online all the
time! Only one subnetwork at the time can be saved.
remark: For saving an existing ULM Network: see OMS user manual 5.7.8!
remark: For saving an existing network with H264 cards, you first have
to delete all the services where H264 cards are involved in and
also delete the H264 cards in your old database. After saving
your subnetwork in the new db, you have to recreate every H264 card
and service you deleted. If this is not allowed, then see
3. real migration when using H264 cards.
1. Create a new DB;
2. Create a network;
3. Create a subnetwork;
4. Select the subnetwork in the treeview and select "Save SubNetwork"
from the menu (this option is grayed out for a certain time after
connection has been established)
5. As a result a "Save services report" appears: check this file to see
whether no undefined or incomplete services are present;
6. If everything is OK according to your report, your DB is ready;

Remark: Sometimes the GUI does not include all saved services.
Workaround: close the current GUI and open it again.
Remark: when you have services over OLM, it is not possible to save and you
have to use the real migration.
Remark: after the migration/save from OMS v2.3 to OMS v9.1, please check
the port settings on the audio cards and adjust if necessary.
-------------------
2.2. REAL MIGRATION (not recommended for X3M networks)
-------------------
2.2.1 Export the database :

Make sure that the OTN network is in a stable state and the OMS
database is up to date (no mismatch alarms). Also avoid to have
'spawned' and 'reserved' services. If you have such, remove
those services. Also verify whether no portless services exist.
Remove these if any.
Open <oms path>\script\python.exe in the current OMS version and
type the following commands:

from OScript import *
Export ("<exported_filename.py>")

where <exported_filename.py> is a file name of your
choice.

Remark: these python commands are case-sensitive!
Remark: When exporting a database that contains an ULM-10G subnetwork,
make sure that the order of creating subnetworks is correct.
The 10G subnetwork has to be created first!

This command generates a script file with the configuration and
the services of your network.

2.2.2 Migrate the script :

To bring the exported script (see step 2.2.1.) to the OMS v9.5
scripting syntax, a translation is necessary (perl script).
Following translation scripts need to be used:

* If you migrate from OMS v2.x to OMS v9.5

migration_to_OMS3_1.pl




* If you migrate from OMS v5.0 or OMS v5.1 to OMS v9.5

* If you migrate from OMS v5.2 to OMS v9.5




* If you migrate from OMS v6.2 or v7.x, v9.0, v9.1 or v9.2
or v9.3 or v9.4 to OMS v9.5
Enter the following command to start the translation:
perl.exe *.pl <exported_filename.py>

If you are migrating from OMS v2.x,, you also need to copy the'oms.cfg'
file from your v2.x config-directory to the <oms path>\script\migration
directory of OMS v9.1 together with the exported scriptfile.
If this 'oms.cfg' is omitted, the script will ask you to enter
the IPaddess(es) or MACaddress(es) of your central node(s) before
proceeding.

There are 2 ways of migrating from one version to another:
1. online;
2. classic.

2.2.2.1 ONLINE

When running the perl-script choose option 0 (convert for on-line use).
With this migration type the hardware part of the exported script-file
is being replaced by following commands:
- CreateNetwork
- CreateSubNetwork
- Set acquisition parameters (SetProperty of the subnet settings)
- ConnectOTNSubNetwork
- Wait
- MeasureSubNetwork
This will "save" the properties of the hardware in your network.

The services part consists of the creation, detection and load of the
different services.

2.2.2.2 CLASSIC

When running the perl-script choose option 1 (convert for classic use)
With this migration type all the network elements and their properties
will be created/set via scripting commands.

The services part consists of the creation, detection and load of the
different services.
2.2.3 Database import :
This new script can now be run into an empty OMS v9.5 database.
Start up the OMS console, create a new database via the OMS console and
start the OMS server via the Start OMS server button.
Under tools in the OMS console you can start the scripting console:
Tools - Start Scripting Console.

execfile <exported_filename_converted_xx.py> >result_file.log

where <exported_filename_converted_xx.py> is the exported and
converted script file
and the ">result_file.log" sends the output (=result) of the
commands to a separate file (you can choose a different
name)

Make sure that OMS is online, because the script will try to
detect the services. The result of the script is the same
database contents as under OMS v2.x, v3.x, v4.x, v4.5, v5.x,v6.1,
v6.2, v7.x, v9.0, v9.1, v9.2, v9.3, v9.4 or v9.5.
TIP : It is best to split the converted script in two pieces
(configuration of the HW elements and retrieving the services)

Remark: For OTN classic subnetworks:
Don't forget to enter the command
"DisableWriting()" in both the scripting files to avoid writing
anything to the network!

Remark: For X3M subnetworks:
Do not use 'DisableWriting()'!
Replace DetectService by ReserveService
Remove any line with SetSubnetConnectionUuid

2.2.4 Load :
After migration towards OMS v9.5, a number of settings will get a
value that can differ from before the migration. this is e.g. the case
with properties that were unused before and now get a default value.
This will at first lead to a number of 'property mismatch' alarms.
Load the configuration in order to correct this situation :
Select therefor the menu item 'load subnetwork' while pointing at
the subnetwork in the Tree View.

Remark:
With an ONLINE migration or SAVE of the network the node names are lost
(node name information is not stored in the BORA). An extra command has been
provided in scripting (Python) to change these names:
ExportNames('<filename>')
A file <filename> is generated in the utilities-directory and the
names can be edited by an ordinary text editor. After the names have
been changed, run the following command in scripting (Python):
ImportNames('<filename>')
These commands can also be used to change the service names.
Service names (limited to 30 characters) in an OTN-X3M network are saved.
For more information see OMS User Manual 5.2.6
---------------------------------------
3. REAL MIGRATION when using H264 cards
---------------------------------------
3.1 Export the database :

Open <oms path>\script\python.exe in the current OMS version and
type the following commands:

from OScript import *
Export ("<exported_filename.py>")

where <exported_filename.py> is a file name of your
choice.

Remark: these python commands are case-sensitive!
Remark: When exporting a database that contains an ULM-10G subnetwork,
make sure that the order of creating subnetworks is correct.
The 10G subnetwork has to be created first!

This command generates a script file with the configuration and
the services of your network. Edit the generated script file and
only keep the hardware configuration. This means remove the creation
of the resource domains and services.

Make sure that the OTN network is in a stable state and the OMS
database is up to date (no mismatch alarms).
3.2 Migrate the script :

To bring the exported script (see step 3.1.) to the OMS v9.5
scripting syntax, a translation is necessary (perl script).
Following translation scripts need to be used:


* If you migrate from OMS v6.2 or v7.x, v9.0, v9.1, v9.2,
v9.3 or v9.4 to OMS v9.5
Enter the following command to start the translation:
perl.exe *.pl <exported_filename.py>

Use classic migration for migrating from one version to another!

3.2.1 CLASSIC

When running the perl-script choose option 1 (convert for classic use)
With this migration type all the network elements and their properties
will be created/set via scripting commands.
3.3 Database import :
This new script can now be run into an empty OMS v9.5 database.
Start up the OMS console, create a new database via the OMS console and
start the OMS server via the Start OMS server button.
Under tools in the OMS console you can start the scripting console:
Tools - Start Scripting Console.

execfile <exported_filename_converted_xx.py> >result_file.log

where <exported_filename_converted_xx.py> is the exported and
converted script file
and the ">result_file.log" sends the output (=result) of the
commands to a separate file (you can choose a different
name)
3.4 Change database version number :
1. Stop the OMS server
2. Close the OMS console
3. Open the SQL management Studio via
Start - All programs - Microsoft SQL server 2008 R2 -
SQL server Management Studio
4. Login to the OMS SQL server via Windows Authentication or SQL server
Authentication
5. Expand Databases via the + button
6. Expand your database
7. Expand tables
8. Right click dbo.DatabaseInfo and choose "Edit Top 200 rows"
9. Change the DatabaseVersion value from 7.x.x.0 to 7.0.22.0
10 Close the SQL management studio
3.5 SQL migration
- Open the OMS console.
- A message is prompted "The selected database is not compatible with
the current version of the OMS system. Do you want to migrate the
selected database."
- Choose "Yes"
- Database migration succesful
- Restart the OMS console
- Start the OMS server
See OMS User Manual 8.10.2 for more information.
3.6 Save services:
You can save your services.
1. Select the Network in the treeview and select "Save Services"
from the configuration menu
2. As a result a "Save services report" appears: check this file to see
whether no undefined or incomplete services are present;
3. If everything is OK according to your report, your DB is ready;
Remark: Sometimes the GUI does not include all saved services
It is advised to open another GUI after performing a save services
as it can happen that not all saved services are included in the
list in the services tab.
Workaround: close the current GUI and open a new one.
3.7 Load:
After migration towards OMS v9.5, a number of settings will get a
value that can differ from before the migration. This is e.g. the
case with some unused properties which now get a dummy value.
This will at first lead to a number of 'property mismatch' alarms.
Load the configuration in order to correct this situation :
Select therefor the menu item 'load subnetwork' while pointing at
the subnetwork in the Tree View.
==========================
MIGRATION OF 2W4W SERVICES
==========================
In case you have programmed 2W4W-MD or BrdCast services in an earlier OMS
version, please read following procedure carefully!
A:Migration from OMS v2.4 (2W4W-MD) to OMS v9.5 (2W4W-BrdCast).
- 2W4W-MD-service configured in OMS v2.4.
- Use the migration-tool "migration_to_OMS3_1.pl" to migrate to OMS v4.x.
=> in the resulting py-file the name "2W4W-Mdrop" will be changed to
"2W4W-BrdCast".
- Reload the service
=> same situation as in OMS v2.4
The multidrop-service of OMS v2.4 is equal to the broadcast-service in
OMS v4.5.
B: Migration from OMS v3.x (2W4W-Mdrop) to OMS v9.5 (2W4W-Mdrop)
- Use the migration-tool "migration_to_oms5_4.pl" to migrate to OMS v9.1
- Run the script and you will have the same functionality as in v3.x
C: Migration from OMS v3.x (2W4W-BrdCast) to OMS v9.5 (2W4W-BrdCast)
- Use the migration-tool "migration_to_oms4_2.pl" to migrate to OMS v4.x
- Run the script
=> the broadcast service in OMS v3.x only has drop capacity. This will
also be the case in OMS v4.0 unless you add/remove ports to the service
or reload the service in OMS v9.1. In that case the port also has
add-functionality.
D:Save OMS v2.4 E&M MD-service in OMS v9.5.
- Service has the same functionality as in OMS v2.4.
=> Service can be saved in OMS v9.5.
E:Save OMS v3.x E&M BrdCast-service in OMS v9.5.
- Service will function as in OMS v3.x. After deletion of a port and
creation afterwards the concerning port has add-functionality as well.

F: Save OMS v3.x E&M Mdrop service in OMS v9.5
- Service has the same functionality as in OMS v4.2

Note : Suppose you want to upgrade your network from OMS v2.4 to a newer
version and you use the 2W4W-MD-service of OMS v2.4. To keep his application
working it's best to upgrade to OMS v4.x.
==========================================
MIGRATION OF ET100 SERVICE IN 15-BIT MODE
==========================================
As of OMS v4.2 the 15-bit mode for ET100 (and ET100E) card is no longer
supported. When you have programmed an ET100 service in 15-bit mode in
an earlier version of OMS, you will only be able to delete this service
and recreate it using a lower mode value.
===========================
MIGRATION OF ET100 SERVICE
===========================
As of OMS v5.0 there is no difference anymore in the service type for
ET100((A)E) cards: when you want to create a service between ET100((A)E)
cards, service type ET100 has to be selected (ET100HX no longer exists).
The conversion script will rename these services.
As of OMS v7.1 there is a new service type, ET100HX4. When you migrate
an OTN-10G-X3M subnetwork from OMS v6.2 or OMS v7.0 you have to rename
the service type to ET100HX4 if the Backplane mode of the ET100DAE card(s)
involved in the service is HX4. To be checked in the ET100DAE card view
in the OMS Gui.
The conversion script will not rename ET100 services in ET100HX4.
============================
MIGRATION OF VIDEO SERVICES
============================
As of OMS v5.0 the naming of the service type for the video service connections
has been changed:
"VIDEO channel MPEG OTN" has been renamed to "VIDEO channel Enhanced".
"VIDEO channel X3M" has been renamed to "VIDEO channel Enhanced".
"VIDEO control MPEG OTN fixed" has been renamed to "VIDEO control".
"VIDEO control X3M" has been renamed to "VIDEO control".
The conversion script will rename these services.
======
BACKUP
======
Please take backups of the database on a regular basis!
Refer to the OMS user manual 8.1 on how to backup your database.
================
UNINSTALLING OMS
================
See OMS user manual 2.5
The database files are NOT removed, nor are the directories
containing those files. Database files are managed by SQL
Express 2008 R2. You can find your database files by default under
c:\Program files\Microsoft SQL server\MSSQL10.OMS\MSSQL\DATA
==========================================
CENTRAL ALARM REPORTER CONFIGURATION FILE
==========================================
With earlier versions of OMS releases a new configuration file was
provided for the OMS add-on "Central Alarm Reporter V2" and
"Central Alarm Reporter IP".
As of release OMS v5.0 this file will no longer be present.
The user can easily retrieve the different alarm codes from the
alarm list provided with the OMS user manual.
Simply put the error code of the required alarm in the carv2.cfg/
carip.cfg file followed by a sequence number.
============
ALARM CODES
============
As of OMS v5.0 the alarm codes of the alarms have been changed.
This can have impact e.g. on the configuration of the central alarm
reporter add-on or when you use SNMP filters based on the error codes.
******************************************************************
3. VERSION HISTORY
******************************************************************
Version 2.2 First full release
New developments and internal improvements, a.o. :
Extension of supported set of OTN equipment :
- N215 node
- BORA150 system card
- VID4-IN-X, VID4-IN-OUT, T1, ATM, 4WVOI-EM interface
cards
General improvements and software enhancements
New utilities (Logexporter, BoraFwDownload, NodeView, ..)
Version 2.3 Enhanced release
- N10, N11, N12 nodes (OTN150 & OTN600 only)
- BORA600 and ORA system card
- 64KBPS, RS232, RS422 and 4WVOI-EM interface cards
- Auxiliary cards and power supplies
General improvements (e.g. monitoring performance,
extension and reduction of ports on an existing service,
...) and software enhancements
New utilities (Configuration tool, Export tool, ..)
- OTN2500 equipment : BORA2500 & OTR2500
- SPM interface card
Extra features on existing OTN equipment :
- audio switching on HQAUD interface cards
General improvements (e.g. service loading performance,
extension of existing Video Switching service, ...) and
software enhancements
Improved utilities (Configuration tool, FW Download tool,
..)
OMS v2.4 also runs on Windows2000 although not fully
supported.
Version 2.4 EB1 Patch release on v2.4
Two issues solved in the area of Video-Switching migration
from v2.3 towards v2.4.
This new release can be recognized via the reference number
on the CD-ROM which has edition 6 : AA31003-Z3931-A330-6-76K5,
and via the OMS build id (Help|About in GUI : v2.4.12)
Version 3.0 Major improvements release
Strong reduction of update delay times
Save of the OTN configuration into the OMS database
(both equipment and services)
Improved user-friendliness, mainly through :
- a re-designed menu navigation,
- understandable and numbered alarm messages,
- limited ruling (some impossible combinations are
avoided),
- service creation wizard,
- GUI indication of server progress,
- on-line selection of central node,
- rename of services and nodes is possible,
- switch of database,
- full use of the programmed card type,
- logical view with indication of central node and node
type
- Implementation of the E1-DACS interface card;
- Security;
- Software enhancements.
Version 3.1 EB1 Patch release on V3.1
Issue resolved concerning the "Element disappeared" alarm.
Resync and poll delay issues on OTN2500 network resolved.
Video switching not functioning on all nodes resolved.
Issue with the new network that does not come online solved.
on the CD-ROM which has edition 10 : A31003-Z3931-A330-10-76K5,
and via the OMS build ID (Help|About in GUI : V3.1.16).
Issue solved concerning the acknowledgement of external
alarms and a further improvement of the "element disappeared"
issue.
on the CD-ROM which has edition 11 : A31003-Z3931-A330-11-76K5,
and via the OMS build ID (Help|About in GUI : V3.1.17).
- implementation of OTN-X3M;
- implementation of ET100E interface card;
- implementation of VID4E-IN/OUT interface cards;
- software enhancements.
Possible to create a VID4E card offline in an OTN-X3M network.
OSD and quality settings of the video card will not be overwritten
by load card, load node or load network operations.
Issue solved concerning the fact that sometimes in OTN-X3M the
programmed card type is overwritten in case of resynchronisation
of the network.

Version 4.2 Beta enhanced release
- implementation of OTN-X3M redundancy;
- implementation of BORA2500-ETX;
- implementation of MPEG card;

Version 4.2 Enhanced release (official release)
- implementation of OTN-X3M redundancy;
- implementation of BORA2500-ETX;
- implementation of MPEG card;
Version 4.4 Enhanced release (V4.4.20)
- implementation of ET100AE (OTN and X3M);
- implementation of E1-24P and corresponding service E1 X3M;
- addition of VIDEO control MPEG OTN fixed and VIDEO channel MPEG OT
N;
Version 4.5 Enhanced release (v4.5.23)
- implementation of MVIDIP;
- addition of MPEG switched in OTN;
- support of Windows 2003 server;
- support of MPEG-AUDIO in OTN-X3M;
- implementation of DVB-ASI interface card;
- implementation of the N415 node;
- backgrounds support in the GUI logical view;
- windows look-and-feel;
- simplified names for the ET100 and video service types;
- database management (possibility to add data- and timestamp
and/or comments when working with different databases);
- implementation of the N2011 node;
- implementation of the BORA2500-X3M-ULM system card;
- Enhanced MVIDIP functionality, support of ethernet service;
- implementation of OTN-622-X3M;
- implementation of the BORA622-X3M system card;
Version 5.2 EB1 release (v5.2.11)
- New PCANDIS driver (version 5.50.18.5);
- for certain E1, E1-DACS and VID4 alarms
the severity changed from major to warning;
- implementation of N2021 node;
- implementation of BORA2500-X3M-ETX system card;
- implementation of H264AVC-4P and
H264AVC-16P interface card (analogue part);
- support of Windows Vista;
- implementation of BORA-OTN;
- redesign of resource domain mechanism;
- implementation of N2021 node phase 2;
- implementation of ET100DAE interface card;
- implementation of the OMS Logger tool;
- implementation of ULM redundancy (single and dual node);
- implementation of OTN-10G-X3M;
- implementation of BORA10G-X3M-ETX system card;
- implementation of N42C node;
- implementation of HX4 for ET100DAE in OTN-10G-X3M;
- implementation of N2021R node;
- implementation of SQL database;
- support of OMS SQL redundancy;
- implementation of HX4 in OTN-2500-X3M;
- implementation of ULM redundancy - single, dual node;
- implementation of H264/AVC Direct streaming incl HX4;
- implementation of ETS;

- implementation of Quick reconfig for X3M;

- support of Windows 7;
- implementation of N5024C,N5024CF and N5048C node;
- implementation of BORA10G-X3M-ULM;
- implementation of N7024C,N7024CF and N7048C node;
- implementation of BORA10G-X3M-ULM redundancy - single, dual node;
- implementation of IP ACL, VRF, VRRP and static routing in OMS FEM.
- implementation of OSPF, IGMP, DHCP and PIM in OMS FEM;
- Support of Windows 7 64-bit and Windows server 2008 R2 64-bit;
- implementation of N42E node;
- Implementation of ETS-4GC24FP;
- MRP integration;
- implementation of STP optimalisations in OMS FEM;

- implementation of N5224C and N7224C node;
- implementation of OSFP monitoring, IGMP monitoring
and IGMP Snooping monitoring in OMS-FEM;
- implementation of Radius in OMS-FEM;
- implementation of Transparent Channel in OMS-FEM;

- implementation of BORA10G-X3M;
- support of Windows 8;
- implementation of PIM monitoring in OMS-FEM;
- implementation of MIB-II in OMS-FEM;

******************************************************************
4. FIXED AND VERIFIED DEFECTS
******************************************************************
Most important fixed and verified defects in OMS version 9.5
================================================================
A. Installation & upgrade
B. Communication
C. User Interface
- Defect 14888 OMS blocks after logout on remote gui
D. Configuration
E. Connectivity
F. Monitoring
G. Performance
H. Scripting
I. Tools
- 15018 Nodes not visible in renaming tool

******************************************************************
5. KNOWN BUGS, LIMITATIONS, AND WORKAROUNDS
******************************************************************
The following is a list of relevant known OMS bugs and their
workarounds in OMS v9.5.
B. Communication
C. User Interface
D. Configuration
E. Connectivity
F. Monitoring
G. Performance
H. Scripting
I. Tools
J. Documentation
For a list of relevant known OMS-FEM bugs, see OMS FEM V9.5.16 Release Note.txt.
- Restriction 1659 : no periods allowed in path/filename of script to
migrate.
The Perl migration script doesn't accept any periods in the path
and filename :
e.g. "perl.exe migration_to_oms4_0.pl c:\oms\oms2.4\db.py"
gives issues; the period in the "oms2.4" path part is seen as
part of the extension of the filename so perl puts
oms2_converted_4 and does not recognize the file.
Workaround : copy the file into a place and name without
periods.
- Defect 11557: During the installation of java, the pc reboots. Java is not
working afterwards.
Workaround: reinstall java manually.
B. Communication
- Under Windows Xp SP3 turn off the firewall before trying to
communicate with the central node.
- De-activate any VPN software installed in order to be able to connect
to an X3M network.
- After the acquisition parameters have been changed, please
restart the OMS server before changes take effect
- Defect 3297: TCP/IP socket error when using the BORA2500 down-
load tool.
Workaround: Please verify following items:
- IP address of the central node is present in the
hosts file (cfr. next defect)
- IP address of the network interface card must be
in the same range as that of the BORA2500
(also mind the subnet mask)
- PCANDIS must have the correct reference in the
registry
=> if necessary copy the PCANDIS5.SYS driver
from the C:\WINNT\SYSTEM32 directory to the
OMS bin-directory
- Defect 2465 : OMS Server crash when IP address changes
In some cases, it may occur that the IP address of the OMS PC
dynamically changes while OMS Server is running. For example,
the IP address obtained from a DHCP may be invalidated after
some time.
Workaround : Windows contains the "Media sensing" feature.
This feature (using the TCP/IP protocol) allows the computer
to detect whether or not the network interface card is in link
state. If not, it removes the protocol from that adapter until
the link is up again. You can disable this feature by editing the
registry:
* go to start - run and type regedit (or regedt32)
* go the key
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Tcpip\Parameters
* add the following key:
Value name: DisableDHCPMediaSense
Data Type: REG_DWORD - Boolean
Value Data Range: 1 (True)
* restart your computer

Or give your PC a fixed IP-address.
When you install OMS using the installshield, this parameter is
automatically set in the registry.
- Defect 10927: Communication between OMS and OTN network drops when
connecting multiple classic rings in the OMS.
Workaround: Do not use an intel NIC for the connection with the bora's.

C. User Interface
- Restriction 2487 : OMS GUI does not start with non-Western
regional settings
Workaround : a US-version of the Windows operating system is
required for OMS; the input locales should be set on a Western
regional settings choice.

- Defect 3460: When the loading of a service is somehow interrupted
(reconfiguration, no link with network,...) it can happen that
everything seems to work according to the GUI however in practice
some services are not working.
Workaround:
* go offline (DisconnectSubnetwork)
* load a random service
* go back online => this will cause timestamp mismatches in
all the nodes
* load the same service => the whole ACRAM of the nodes
will be overwritten

- Restriction 4018: Additional card information stays on screen while
card is not present.
When valid additional card info is present and you unplug the card,
this information will not be updated.
- Defect 6397: In the logical view the outer ring is not always the
primary ring.
Workaround: Change manual layout and save it.

- Defect 7002: MPEG and H264AVC port alarms pop up when OVS is not running.
In OTN-X3M, OVS controls one RD with in/out ports.
When OMS is reconnected while OVS is not running,
a number of mismatch alarms (sometimes) pop up on the
MPEG, H264AVC input port properties : Audio, Invisible Lines,..
This while the port notes that the 'Settings [are] overruled by OVS.'
Workaround: Loading the port/card resolves the mismatch.
- Defect 7484: The Video control port alarms for port 2
refer to port 3 in stead of port 2 on the H264AVC card.
i.e. "99962885 RS mode port"
net\ring\node\IFC\3
in stead of
net\ring\node\IFC\2
- Defect 8244: Virtual OTN node numbers of ULM not correct if layout is saved
Workaround: When saving a layout do not check the box "load this layout by def
ault".
When the issue persists change in the layout.xml file in the bin directory of
OMS
<IsDefaultLayout>1</IsDefaultLayout> to <IsDefaultLayout>0</IsDefaultLayout>
and restart the GUI.
- Defect 8517: links aren't updated after a disconnect of the subnetwork.
Workaround: close the current GUI and open a new GUI.

- Defect 11775: Zoom factor of nodes in logical (sub)network view layout not res
tored
after restart Gui
D. Configuration
- Defect 2829 : Save Subnetwork : Univoice module not saved if
not present
The 'save' action is based on the programmed card type, meaning
that the card does not have to be there physically. A Univoice
module (having no programmed type) is however not saved if the
Univoice card or the Univoice module is not present.
Result : services terminating on that Univoice module aren't
saved successfully neither.
Workaround : if you want to save a network including 'missing
Univoice modules' (or cards), follow this workaround :
+ identify the Univoice modules or cards that are physically
missing in the hardware
+ don't launch the 'save' action from within the GUI, but use
the scripting tool instead, with following commands :
+ save the hardware part with the "Save ('<subnetwork URL>')"
scripting command
+ use the GUI to create the missing Univoice cards and/or
modules based on your information
+ save the services part with the "SaveServices ('<subnetwork
URL>')" scripting command
Remark that this is only needed for the Univoice card; other
card types don't have this functional restriction.
Remark: Univoice modules will only be discovered when the
Univoice interface card is released.
- Restriction 1633/2725/3239/5437 : A number of characters should not be
used in names of services, nodes and subnetworks.
The characters /\,.[]{}$ are prevented by the OMS GUI.
Also don't use the character " in the name since this can cause
issues in when migrating the DB.
Also in case of a restore layout, some characters may cause issues
(e.g. < ) when this character is present in the blue title bar of
a window that needs to be restored.
For example, if your subnetwork is named Nrnberg and you need to
restore a layout where the subnetwork window is open, a restore
layout fails.
Considerations should be made while migrating an older database
containing those characters, into a new OMS v4.4 database. (The
migration script also takes care of it.)
It is also advised not to use them in network names as well.
Subnet names may not end with a blank character: this causes
issues in scripting.
Remark that those characters are not prohibited by scripting.

- Restriction 2993 : A number of characters should not be used
in names of OMS databases.
The characters /\:*?"<>| can not be used in a database name (as
Windows cannot use it in a file name).
Attention: When executing the ImportNames command in scripting
no check is performed on the characters in the names!
- Defect 5688: When OVS controls the MPEG cards, OMS will show all
the ports as input ports even if they are defined in OVS as output
ports.
- Defect 6347: During migration from an older OMS version to the
current version when VID4(E) cards are involved, an error message
will appear on the property "VID4(E)Card_Spare1". This property has
been replaced in the VID4_IN_X and VID4E-IN card by the property
"VID4Card_CompressionRatio" and "VID4ECard_CompressionRatio".
Please ignore this error message.
- Defect 6735: Order of multiple masters of a video switching service
may be swapped after SAVE services => ImportNames() failure
While this may not be an issue for the video switching service
in order to work, performing an ImportNames() command fails.
Workaround: Manually change the Id of the master
in the ImportNames file.
- Defect 7626: When clicking the show button in the segment allocation tab
ET100DAE view it can happen that at the first time click
it takes a long time for the view to appear.
You can avoid waiting by clicking once more in the grey window.
- Defect 7801: IFC MPEG and ET100AE have "Wrong switch position"
when in reset in OTN classic
The expected card switch value is Off but should be on.
Workaround: Release the card or
Change the value in the expert mode of the IFC Card involved.
- Restriction 8266: off-line a ULM connection is always shown as
a Standby ULM connection even in a redundant ULM configuration.
When you go on-line the connection will become an Active ULM connection.
- Restriction 7965: Modify ULM redundancy
This feature is only to be used by OTN systems service engineers.
Please contact your service engineer for more info.
- Defect 9154: Pink / Magenta striped overlay on the H264 video.
Workaround: do not use 3/4D1 as resolution.
- Defect 14603: N50/N70 node creation gives an error on setting the name
of a discovered node
Workaround: just press ok in this error message.
E. Connectivity
- Restriction 5370: As of OMS V4.4 "PacketSize" is no longer a
service attribute of the ET100 service. When migrating from a
lower version you will see an error in de OMS server window,
indicating that the attribute was not found in the associatable.
You will get a mismatch alarm but after "Load Service" the setting
will be restored.
- Defect 6453: The ports 2 to 6 of an ET100(E) card (in OTN or OTN-X3M)
remain 'Spawned' when a service is activated on the card.
Only port 1 becomes 'Activated', while all the ports work.
This was not the case in previous OMS versions, were all 6 ports
became 'Activated'.
Workaround : none.
- Defect 6815: In the services tab of the N42-ULM node the services of
the corresponding N42 node are shown, even if the services run over
X3M only.
Issues on services using OLM gateway cards :
- Defect 2197 : Fixed High Quality Audio services on not upgraded
cards not prevented over OLM gateways
Only 'upgraded' HQAUD-S/M cards (from edition 2 on) can
communicate over OLM gateways. Programming of such service is
not prevented for 'old' cards.
- Restriction 2540 : Services spanning three subnetworks cannot
be detected
It is possible to program a service from subnetwork A over B
towards a third subnetwork C (using two pairs of OLM cards).
It is however not possible to detect or to save such service
afterwards (i.e. as part of a migration).
Reason : the subnetwork in the center does not have any port
termination.
Workaround : the service has to be re-programmed (re-activated)
when migrating to a new OMS version.
- It is not possible to extend or reduce services over OLM.
- It is not allowed to add a route to an existing connection.
Issues on 'Save Services' :

- Restriction : When OLM gateway cards are used in the network
the 'save' action is only supported on subnetwork level.
This means that is services spanning several subnetworks via
OLM gateway cards are involved, the 'save' function should not
be used (or only for temporary monitoring purposes).
Workaround : Use the other migration path (via Export() and
DetectService() commands) when such services are involved.
- Defects 2764/2848/3168 : Save Services issues with HQAUDIO
cards :
It is advised to take care when using the 'save' function on
your network when you have HQAUD-S/M cards involved.
Details :
+ In some cases, saving the Audio-Switching services fails (and
ends in an incomplete service). The precise circumstances to
having this issue are unknown.
+ Altering or re-loading saved Audio-Switching services (or
audio-fixed services) can harm those services
+ If an RS-ptp data service is programmed between two RS422
ports on HQAUD cards, or between such port on an HQAUD card
and an RS232MM card, this leads to wrongly saved services
(invalid, incomplete,..).
+ Extending or reducing a saved audio-switched service can
break the service or trigger unclearable alarms.
Workaround : do not use the save feature if you have an AUD-X
service, or RS services on HQAUD cards (depending on the case).
- Defect 6722: Sometimes GUI does not include all saved services.
Workaround: close the current GUI and open it again.
- Defect 7751: Service names (limited to 30 characters) in a OTN-X3M
network are saved.
Workaround: use service names smaller than 30 characters or first
do a ExportNames('<filename>') in your old database, to export the
long service names. Later do an ImportNames('<filename>') in your
new database.
Issues on 'extending / reducing existing services' :
- Restriction : Expanding and reducing a HQAudio Switched service
only possible if 'Virtual Slot' not involved.
Removing a HQAudio card from a HQAudio Switched service that is
marked as the 'Virtual Slot' in that node, will be prevented.
Adding a new HQAudio-M card into a HQAudio service in a node
that already contains HQAudio-S cards but not yet HQAudio-M
cards, will not be prevented, but yet won't work.

- Restriction 4722: Removed HQAUD port (M or S) in HQAUD Switched
service keeps functioning i.e. one can still (re)switch audio
to it.
Issues on HQAUD-X :
- Restriction 2227 : HQAUD-X : no internal connection with OLM
In a Switched High Quality Audio service, internal connections
are possible (= several audio cards in same node participate in
one service). Such internal connections are not possible towards
an OLM gateway. This means that, if the HQAUD Switching service
passes over OLM's, those have to be installed on separate nodes.
- Restriction 5588: When you add to an existing audio switching
service an extra master card which is positioned left from the
control center in the same node, the audio signal will be dis-
rupted. The only solution is to recreate the complete audio
switching service.
- When an audio master card is present in the audio switching
service which is not the control center and which is the only
master card in that node, it is not possible to remove that card
afterwards without reprogramming the service since this card is
considered to be the virtual master in that node.
Issues on Video/VID-X :
- Remark: when loading services involving VID4E, MPEG, MPEG-OTN cards
default values will be filled in for the quality parameters in
relation to the reserved bandwidth.
Issues on MPEG:
- When connecting an X3M ring to OMS v6.1 or higher which has been running
on a lower OMS version then OMS v5.1 (during an upgrade) the MPEG cards
will go to reset. This means that all video traffic for that card will
be cut off.
The customer should then save the subnetwork and perform a load service
(fixed connections) or activate video application (for video switching)
to get the cards up and running again.
Remark: It is possible that some properties
(MPEGX3MCard_ColorStandard, MPEGCard_AudioPresent,Control port...)
are not saved correctly.
It is advised to change these via scripting (see HWTemplate.py
example script on how to change the properties
of the MPEG card in X3M) or change it manually.
Issues on H264:
- Defect 9082: If you have programmed a Video Channel Enhanced service of
10 MB in an older OMS version (< v7.0) then a save will fail in OMS v7.x.
Workaround: Delete the service in your old OMS and recreate the service
with a maximum bandwidth of 8 MB.

F. Monitoring
- Restriction 2727 : Wrong switch position alarm on Ringing Generator
It can happen that the 48V/25Hz Ringing Generator wrongly
triggers a 'Wrong switch position' alarm although the card does
not have a card switch.
Workaround : change in that case the 'expected' value for this
setting via the following scripting command :
"SetProperty ('<card URL>','IFCard_CardSwitch','Off','SETTING')"
- When the subnetwork re-synchronizes several times again, it can
happen that the subnetwork turns grey in the OMS GUI and generates
an "Element disappeared" alarm. The subnetwork will return online
after the ring stabilizes again. This is because the OMS is not
able anymore to retrieve correct information from the network during
these re-synchronizations.
H. Scripting
- Restriction 0596 : Scripting commands are case-sensitive.
Take care to use the correct syntax.
- Restriction 0620 : Do not use accents in names of network
elements.
Avoid using accents (and other characters exceeding the ASCII127
range) in (interactive) scripting sessions.
This is only relevant if the scripting utility is used
interactively instead of in batch mode.
I. Tools
- Defect 3161/2003 : Event & alarm reports wrongly sorted in XML
viewer
The log events aren't sorted chronologically but alphabetically
in the report.
(e.g. 'oct 23, 2002 11:20:00' is displayed in between 'oct 22,
2002 9:00:00' and 'oct 22, 2002 9:00:00'.)
Workaround : none
- Defect 6450: When the OTNDownload tool is used for downloading the
firmware to the MPEG cards, it can happen that, when these cards are
programmed in a video switching service which also contains VID4 cards,
the VID4 cards are also listed in the treeview. Downloading to the
MPEG cards will fail in this case.
Workaround: remove the VID4 cards from the video switching service and
try to download again.
- Defect 5904: X3MDownload tool: Download BORA2500-X3M firmware
shows V1 and V2 cards in the treeview of the tool.
When selecting the firmware of BORA2500-X3M V1 cards
all BORA2500-X3M cards (V1 and V2)in the network are shown
in the treeview and vice versa.
When the download is started only the V1 cards will be upgraded
and vice versa. In this case the V2 cards
will have the message "faulty peer". This message can be ignored because
in fact nothing is downloaded to these cards.
Remark: The OExporter tool (and related the reports via the GUI)
will be revised in future OMS releases. Therefor not much
attention has been paid to the contents of these reports
for the new network elements.
******************************************************************
6. FIRMWARE - LOADWARE VERSIONS
******************************************************************
On this OMS DVD following loadware and firmware versions are
provided:
NETWORK ELEMENT VERSION TOOL
-------------------------------------------------------------------
BORA150 003.026 OBoraFwDwnld.exe
BORA600 003.026 OBoraFwDwnld.exe
BORA600_MICRO 003.026 OBoraFwDwnld.exe
BORA/ORA 003.026 OBoraFwDwnld.exe
BORA-OTN 003.026 OBoraFwDwnld.exe
BORA2500 B25FW01_13Gria01_03 OB25FWGriaDwnld.exe
BORA622-X3M 2.15.5 X3M Download Tool.exe
BORA2500-X3M
mix (appl + kernel) 3.0.17 X3M Download Tool.exe
Kernel 3.0.17
Application 3.0.17
BORA2500-X3M (redesign) 4.15.3 X3M Download Tool.exe
BORA2500-X3M-ULM 3.16.4 X3M Download Tool.exe
BORA2500-ETX
mix 2.1.5 X3M Download Tool.exe
Kernel 2.1.5
Application 2.1.5
BORA2500-X3M-ETX 3.15.3 X3M Download Tool.exe
BORA10G-X3M 1.0.2 X3M Download Tool.exe
BORA10G-X3M-ETX 1.16.5 X3M Download Tool.exe
BORA10G-X3M-ULM 2.5.4 X3M Download Tool.exe
MPEG (X3M) 4.3.1 X3M Download Tool.exe
MPEG (OTN) 4.3.1 OTNDownloadTool.exe
ET100AE (X3M) 3.0.1 X3M Download Tool.exe
ET100AE (OTN) 3.0.1 OTNDownloadTool.exe
ET100DAE (X3M) 1.4.0 X3M Download Tool.exe
H264AVC 4.0.1 X3M Download Tool.exe
MVIDIP 4.0.7 X3M Download Tool.exe
VID4E-IN 3.3.3 X3M Download Tool.exe
VID4E-OUT 3.3.3 X3M Download Tool.exe
N5024C 7.0.6 X3M Download Tool.exe
N5024CF 7.0.6 X3M Download Tool.exe
N7024CF 7.0.6 X3M Download Tool.exe
ETS-3GC7F 2.4e ETS Web browser
ETS-4GC24FP 1.2e ETS Web browser
For X3M there are 2 possible FW versions:
v3.0.17: for the first generation BORA2500-X3M board (S30824-Q95-X101);
v4.15.3: for the second generation BORA2500-X3M board (S30824-Q123-X103).
Both BORA2500-X3M cards are interchangeable.
Remark:
- If you mix a first generation and second generation board in one node
for redundancy, make sure they both have the latest firmware. Also make
sure you upgrade the first generation board first. Otherwise it could
happen that the cards don't see eachother.

Also look for updates on the OTN extranet:
https://extranet.otnsystems.com
Go to Services > Downloads or via Compatiblity shortcut
******************************************************************
7. MISCELLANEOUS
******************************************************************
******************************************************************
Copyright (c) 2013 OTN Systems n.v.
All rights reserved.
******************************************************************

OMS V9.5.16 Release Note

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMS V9.5.16 Release Note

Uploaded by

Copyright:

Available Formats

******************************************************************

OTN Management System Release Notes August, 2013

You might also like