1. Release Notes
  2. Caveats, Known Issues, and Limitations
  3. Known Issues

Known Issues

The following table lists Known Issues and provides the Service Request ID number, a description of the issue, any workaround, when the issue occurred, and when Oracle fixed the issue. This table includes issues from previous releases that either remain open or are resolved in this release. Issues from previous releases that do not appear here do not apply to this release. You can also find information about resolved issues in the Build Notes for this release.

ID Number Description Found In Fixed In

31630190

 ECB going out of service after upgrade from PCZ3.1.0p4 to PCZ3.1.0p5. PCZ3.1.0p5 PCZ3.1.0p6
29401925

The GUI does not allow you to edit a user database entry that contains an Address of Record.

Work-around: Delete the entry and add it as a new entry with the changes that you want.

PCZ3.1.0 PCZ3.1.0p2
No ID number

If you want to establish a High Availability pair that uses IP addresses other than the defaults, perform the following procedure. Use this procedure regardless of whether the ECBs run on virtual or physical systems.

The IP addresses you use must be available and valid in your network. If not, you must directly connect the two ECBs before performing this procedure to establish the HA pair initially.

Note
  • Primary default—169.254.1.1
  • Secondary default—169.254.1.2

Procedure

  1. Perform the standard HA setup with the run setup command, and allow both systems to come up in an HA pair.
  2. From the GUI, go to General, General, High Availability and assign the IP addresses that you want to use to the Primary and Secondary ECBs.
  3. Move the wancom1 connection to the network that you want to use. (Either the physical connection, or for VMs, change the vswitch used by the wancom1 interface.)
  4. Double reboot both systems, and they will come back up in an HA pair.
PCZ3.0.0
28314178

When you turn on SIP debugging, you may see various unrelated messages displayed on the console. The messages do not prevent the ECB from generating logs, but they can make the console hard to use.

Work-around: Use SSH when you turn on SIP debugging.

PCZ3.0.0 PCZ3.1.0p2
No ID number

If you see mapping errors after upgrading, for example errors about redundancy or media traffic, you may need to swap interface addresses.

Work-around: Compare the MAC addresses on your Virtual Machine (VM) to those on your hardware. If the addresses are different, you need to swap interface addresses. Set the addresses on the hardware to match those from your VM. Use the swap command from the ECB command line.
  1. Use SSH to access the command line prompt on the ECB.
  2. From the ECB prompt type sho interface mapping, and press ENTER.

    The system displays its mappings.

  3. Compare the mappings to your VM mappings.
  4. Type interface-mapping, and press ENTER.
  5. Type swap <eth-if-name_1 eth-if-name_2>, and press ENTER.

    Example: swap wancom0 s1p0

    The system displays the interface mapping information after the swap and a warning that the change can affect services and requires a reboot.

  6. At the Continue prompt, type yes, and press ENTER.
  7. Exit the configuration.
  8. Reboot the ECB.
PCZ3.0.0 PCZ3.1.0
30576125 The ECB is reporting session limit inaccurately. PCZ3.1.0p2 PCZ3.1.0p3
30574675 Inbound TLS fragmented packet failure when using Acano. PCZ3.1.0p1 PCZ3.1.0p3
30355590, 30406870, 30464332

Some versions of ECB unable to load on some versions of OCSDM. PCZ3.0.0p4 PCZ3.1.0p3