OCCSM Caveats

This section list caveats related to Version S-CZ9.1.5 of the Oracle Communications Core Session Manager (OCCSM).

• Do not load configurations from sibling products, the Oracle SBC for example, on the OCCSM. Those configurations are incompatible with the OCCSM, causing incorrect operation. Users should configure the OCCSM from scratch or use another valid OCCSM configuration.

• Configuration elements specific to the SLRM, including lb-interface are not compatible with OCCSM configuration elements. The set-component-type command provides a warning indicating that the user must delete any prior configuration and create the new component type configuration from scratch to avoid potential configuration conflicts. Note the sample output below.

  • SCZ715_64# set-component-type core-load-balancer
    WARNING: Changing component type is service impacting.
    ********************************************************  
    Ensure that you follow these steps if you choose to  
    change the component type:  
    1. Issue the delete-config command.  
    2. Reboot.
    ********************************************************
    Continue with the change [y/n]?:

• Multi-stage routing does not work for S-CSCF routing functions.

• The OCCSM does not support 'netboot' when operating on the Oracle VM platform. The user must, instead, upload new images to the OCCSM and boot from them locally.

• By default, storage is not persistent across a reboot of a OCCSM virtual machine. You must create persistent storage space for log and dump file data.

  • Issue - Generic virtual machine installation documentation may not include the requirement to run the command format hard-disk during virtual machine installation.
  • Resolution - Run the command format hard-disk to create a persistent partition for your /opt directory, within which you can store data needed after a reboot. Perform this procedure the FIRST time you start your OCCSM.
• The OCCSM accepts only the first message received from an application server in response to messages from the OCCSM that included an ODI. If it receives subsequent messages from that application server, the OCCSM drops the reused ODI and processes the message as if they were received without an ODI.
  • Resolution - Do not configure an AS to fork responses to the OCCSM that include an ODI originally provided by the OCCSM.
• Geo-redundancy is currently not supported by the OCCSM.
• The OCCSM introduces a system-config parameter named cgroup-enable. This parameter must not be enabled. After starting up at your site, check this parameter and make sure it is disabled.

  For example. In S-Cz8.2.5p2, this parameter is enabled by default. But in S-Cz8.2.5m1, this parameter is disabled by default.

  Contact Oracle Support before you consider changing this configuration.

  Note:

  Always ensure the cgroup-enable parameter is disabled before an upgrade.

Caveats Inherited from the S-CZ9.1.0 SBC

Refer to the Caveats in the S-CZ9.1.0 OCSBC Release Notes to complete your review of issues in this release. Issues within the OCSBC, especially including applicable VNF platform and applicable application issues apply across the S-CZ9.1.x product versions, including the OCCSM.