User guide

iControl
Release Notes
53
• [Ref. #30978] iControl’s Edit Service Location Web page may not function properly when
using Mozilla Firefox version 4.x.
Workaround: Use Mozilla Firefox version 3.6.
•
[Ref. #21437] When a system takeover is performed, the redundant unit will be missing the
Data Management Tool tables, if any, from the main system. The DMT tables are also
missing when a system is restored from backup.
Workaround: If you have exported data from DMT, you can restore the DMT tables by
importing the data into DMT once the system takeover or restore is complete.
•
[Ref. #20914] Mixing application servers that have different iControl versions in the same
cluster is not supported. Although it is possible to configure an application server with
iControl Version 3.20 to replicate a server that has Version 3.30 (using the Profile
Replication Management Tool), any attempt to have the Version 3.20 system take over will
fail.
•
[Ref. #18748] An unexpected power disruption, such as might occur during a power failure,
can damage the file system on an iControl Application Server. It is strongly recommended
that all Application Servers be connected to a standby power source, such as a UPS
(Uninterruptible Power Supply), as a preventive measure.
•
[Ref. #9059] It is impossible to tell whether a TSL controller is actually connected to the
Application Server over RS-422, so the service may reflect a normal status even though the
device has been disconnected.
•
[Ref. #3496] After the system is configured, changing the Application Server host name will
require that all devices be renamed in iC Navigator, and all assignments be re-done in
iC Web after the change. Changing IP addresses has a much smaller impact limited to re-
assigning streams in iC Web. Also, “Reference Configuration” must be removed after
changing the Application Server name. Otherwise, devices will still keep attributes based
on previous host name. Contact Miranda Technical Support if this is required. There is a
way to recover the user settings after a system rename.
Redundancy / Failover
• [Ref. #27148] If a failover occurs and a scheduled action is already in progress, the scheduled
action continues indefinitely regardless of the configured duration period.
Workaround: After a failover occurs, verify the configured time frames of scheduled
events to ensure the command to end an action was not scheduled to happen while the
Application Server was offline.
•
[Ref. #27156] When performing a reverse takeover, the Webmin services of the Main
Application Server may fail to start.
Workaround: Before configuring redundancy groups, disable the eth1 port.
•
[Ref. #25510] After performing the following steps, the Main IP address may be unknown
according to the Redundancy page of the Backup Application Server, and the Reverse
button may not be present:
Steps: