Doc:latest/relnotes

Revision as of 05:40, 20 February 2012 by 176.8.88.41 (Talk)



http://www.buyxanaxonlinepill.com/ xanax no prescriptions - buy alprazolam online

http://www.buyxanaxonlinepill.com/ cheap xanax online - purchase xanax online no prescription

http://www.buyxanaxitem.com/ xanax to buy - xanax

Contents

Migration To Latest Version

Migration of a project or model from an earlier version of the OpenClovis IDE to the most recent version is performed automatically when the model it opened for the first time in the newer vesion. The IDE auto-detects the project's version and changes the internal files so that the information is in valid format and can be read by the current version. It also provides an option to create a backup of the project while performing the migration. For more information, refer to OpenClovis IDE User Guide, Section Migrating Project. IDE supports migration from R2.3 and above.

Any issues regarding migration from a previous version of the IDE are documented below.


Change in Log File Locations

As of release 3.0 all SAFplus Platform runtime log files are created in the var/log subdirectory of the SAFplus Platform install directory. It is recommended that you update existing models to also use this directory. To update an existing model edit the clLog.xml file in the model's src/config directory. Change all references of .:log in the <fileLocation> elements 

       <fileLocation>.:log</fileLocation>

to .:var/log 

       <fileLocation>.:var/log</fileLocation>

Once the model is rebuilt and deployed these new settings will take effect.

gmsConfig.xml file

Models of R2.3 may not contain the gmsConfig.xml file if GMS configuration is not done. If you migrate this project you will get error message saying that Migration was unable to create this file. But this is not going to affect further use of model. Model will be OK and user can make changes to it from IDE, generate source, build it, etc without any problem.

Although this error is not going to affect the functionality of the model, there is a work around for this. Before migrating your model, just open up the model in your old IDE setup. Launch "SAFplus Platform Component Configuration" dialog from the Clovis menu. Press OK. Now just migrate the model with new IDE setup, you will not get this error. Bug has been raised for this and it will be fixed in next release.

Known Issues

This chapter describes the known issues in the current release and provides the associated workarounds. These issues arise due to deviation from the normal functioning of the system or as a result of an unexpected behavior of a component or a service.

Known Issues of OpenClovis SAFplus Platform

Following are the known issues for OpenClovis SAFplus Platform:

  • Infrastructure and Communications
    • TIPC address: TIPC with 1.5.12 versions was found to give problems (link unstable) when you have 2 different TIPC netids configured for the same TIPC address. This issue is not seen with the 1.7.x TIPC releases, but in general we recommend you to keep the TIPC addresses unique and not collide with the same addresses on nodes configured with different TIPC netids. One of the symptoms of this is that the TIPC link between 2 machine starts going UP and DOWN continuously when there is another machine in the network, whose TIPC address is conflicting with address of one of those 2 machines. The behavior can be observed through continuous execution of command "tipc-config -l" or through "dmesg".
    • In general, TIPC 1.5.XX has been found to be unstable, especially under high multicast load, and should not be used in production environments.
    • Bug ID #7269 A cluster having a mixture of 32bit little endian, 32bit big endian and 64 bit little endian machines/nodes may find that the GMS service in inadvertently terminates.
      • Workaround - None
    • aspinfo known issues: (1) On some systems, especially systems with Python version 2.3, aspinfo can be slow to respond. (2) Some corner cases may not be properly handled and aspinfo may prematurely exit, dumping its Python stack.
  • System Management
    • Bug ID #7313 If an Alarm Server is restarted after it published an alarm, it won't allow to clear/publish that alarm again.
      • Workaround - Currently there is no workaround.
  • SAF Compliance
    • Deviation from SAF in Event Service: Event Service does not yet support Event Retention as specified in SAF specification. The retention time specified in the clEventPublish() API would have no effect.
    • Bug in SAF specificaion B11: The clEventDataGet() API of Event Service is in compliance with the SAF specification B11. This allows the user to either allocate memory for the event payload or obtain it from the API by passing a pointer. The latter is not possible with this API as the argument needs to be a pointer to a pointer which is not the case. As per the new specification and the recommended way the user is always required to allocate and free the memory.

Known Issues of OpenClovis IDE

  • Bug ID # 6543: X Error in Ubuntu Installation. Starting the IDE in Ubuntu installation may result some X errors in the console. This is not an IDE issue, this will not affect any of the IDE functionalities.
    • Workaround - See the Limitations section of the OpenClovis IDE User Guide.
  • SNMP MIB Enumerated Integer Construct Limitations: During SNMP code generation all enumerated integer labels are converted to #define statements. The constant names used in these statements are the enumerated integer labels converted to upper case. Because of this the all labels used within an enumerated integer construct must be unique regardless of case.
  • SNMP MIB V1 TRAP-TYPE Construct Not Supported: Due to an issue in the Net-SNMP mib2c compiler code generation for MIBs using the V1 TRAP-TYPE construct does not work properly.
    • Workaround - To generate trap code from an SNMP MIB use the SNMP V2 NOTIFICATION-TYPE construct.

Known Issues of Install Package

  • Bug ID # 6749: Potential conflict with net-snmp package on local system: In certain rare instances, building OpenHPI from the included third-party packages during SDK installation fails owing to a conflict with an already-installed version of NetSNMP on the system. In these instances, it is recommended that NetSNMP be removed from the local system before installing OpenClovis SDK, and that it be reinstalled after completing the SDK installation.
  • Installation on Red Hat Enterprise 4: On a Red Hat Enterprise Linux 4 system, the 'Development Tools' subset of packages must be installed to cover the requirements for installing OpenClovis SDK. In general, an installation with the default package set contains all requirements for installation.
  • Installation on Fedora Core 6: On a Fedora Core 6 system, installation of OpenClovis SAFplus Platform automatically builds and installs the TIPC opensource package. To build TIPC, the kernel headers must be present and so these are automatically installed (by our ./preinstall-fedora-core.sh script) using the "yum install kernel-devel" command. On rare configurations, this command does not work correctly. It is supposed to install headers so that the symbolic link located at "/lib/modules/`uname -r`/build" points to a valid directory of Linux header files. However, on some systems this symbolic link points to "/usr/src/kernels/2.6.22.14-72.fc6-i586" but the headers are actually installed in "/usr/src/kernels/2.6.22.14-72.fc6-i686" (note 'i586' vs 'i686'). To resolve this problem, change the symbolic link to point to the correct directory name, and then restart the OpenClovis SAFplus Platform installation.
  • Configuring TIPC and assigning the SAFplus Platform node address to an OpenClovis SAFplus Platform is done by SAFplus Platform start up script. But if manual configuration of TIPC is allowed. Misconfiguration (such as assigning 2 nodes the same TIPC address) will result in an unstable system. When this happens the whole system (all the SAFplus Platform nodes including the ones which are already up and running properly) have to be brought down, the TIPC kernel driver unloaded (to remove its configuration) and the system restarted.
  • Installation of SQLite using Preinstall script: The Preinstall script installs SQLite by default as database engine. It locates SQLite - if it is already installed - without verifying version number. If its version is older than 3.3.13, then SAFplus Platform will fail to start.
    • Workaround - Use SQLite 3.3.13 or newer. The source code can be downloaded from http://www.sqlite.org/download.html. The user can install the latest version of SQLite if its not present in the repository.
  • Installation on Solaris 10/SPARC (beta): Installation of OpenClovis SAFplus Platform requires the following third party packages installed via either installation media or using pkgadd with packages obtained from http://www.sunfreeware.com/. Missing third-party packages may cause unpredictable behavior during installation and SDK use.
    • db-4.2.52
    • fileutils
    • flex
    • gcc-3.4.2
    • gdbm-1.8.3
    • glib-2.14.1
    • gmake
    • gtar
    • libintl
    • libiconv
    • ncurses
    • openssl
    • pkgconfig
    • python-2.5.1
    • readline
    • snprintf
    • tipc-solaris-1.7.5 or SUNWtipc
    • SUNWbtool
    • SUNWsprot
    • SUNWhea
    • wget

Environment Related Observation

  • Bug ID #7549 When SAFplus Platform is running in non simulation mode, if SAFplus Platform is started from one sandbox, then it can be stopped/zapped from another sandbox.

Enabled Firewall Can Cause SAFplus Platform to Shutdown

The enablement of a firewall on a system running a deployed SAFplus Platform image can cause the software to shutdown. An indication that you may be running into this problem is if you see an entry similar to the following in your log file (in the log file it is one line): 

Wed Sep 26 15:06:54 2007   (SCNodeI0.10499 : GMS.---.---.00036 :  ERROR)
   [clGmsEngine.c:448] No nodes in the cluster view to run leader 
   electionLeader Election Aborted

To resolve this problem disable all filtering in the Netfilter framework by issuing the following command. 

iptables -F

Reusing A Project Area With New Version of OpenClovis SDK

Every Project Area is associated with an installation of OpenClovis SDK at a given location. If one elects to reinstall the SDK at a different location or install a newer version at a different location, the project area will stay associated with the original SDK location. This allows one to work with multiple versions of the SDK simultaneously. In order to use an existing project area with a different or moved installation of OpenClovis SDK, remove the .config file from your project area directory and re-run configure as you normally would to work with a model.

Running Multiple SAFplus Platform Clusters in the same Subnet

If you are running multiple SAFplus Platform clusters within the same subnet, please ensure that the TIPC network ID selected for each cluster is unique.

Documentation Issues

This chapter describes the known issues with the OpenClovis Documentation shipped along with the product.

  • Formatting issues
    • Following cross-references pointing to a heading, the PDF viewer will jump to the end of the previous page if the heading is on the top of a page.
    • Firefox web browsers sometimes do not correctly jump to intra-page anchors when the user clicks on a reference. This is a known issue with Firefox. The workaround is to click on Back button and then on the reference again. The browser jumps to the correct position for the 2nd time.
Retrieved from "https://help.openclovis.com/index.php?title=Doc:latest/relnotes&oldid=22716"