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

Resolved Known Issues

The following table provides a list of previous Known Issues that are now resolved.
ID Number Description Found In Fixed In
32383916 The system raises the critical alarm Failed to decrypt values if you do not configure the Secret parameter for any active LST element.

Work around: Configure the Secret parameter for all active LST elements to avoid this alarm.

PCZ3.3.0 PCZ3.3.0p1

32179572

 The Session-Agent Status search tool does not work when deployed to the Dashboard. PCZ3.3.0 PCZ3.3.0p3

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 and PCZ3.2.0
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