Known issues are software issues that have been discovered in the current release or a previous release, and have not yet been resolved.
Synergis™ Softwire 10.11 GA includes the following known issues:
|Interface module||Issue||First reported in||Description|
|AA IP||956660||10.5 GA||When opening a door that has an assigned door sensor, no Entry detected or Entry assumed events are generated.|
|AA IP||756219||10.4 GA||Cx-type locks: When a passage mode-enabled door is unlocked, it does not relock when security clearance is applied through threat level.|
|AA IP||543039||10.2 GA||Px-type locks: A door that is opened during unlock passage mode relocks
Workaround: Set the Door relock option to On close.
|All||2055777||10.10 GA||If the serial numbers of two OSDP readers differ only by
their leftmost digits, both will have the same unique identifier (UID) in Security
Center. In this case, using the UID as
an identifier for key storage causes a conflict while attempting to pair the
readers for Encrypted communication.
Workaround: Use fixed keys rather than random keys.
|All||1572489||10.7 GA||In Security
Center 5.7 SR2, when a
hardware zone arming input goes into a trouble state, it leaves the zone in a
state where some other transition events might no longer work.
Workaround: Set the arming input to a normal state, then make it active again to rearm the zone after the input enters a trouble state.
|All||778548||10.4 GA||A Synergis™ unit cannot be enrolled using its hostname if the system is in DHCP mode and IPv6 is enabled.|
|All||772705||10.4 GA||I/O zones are not shown in the correct state if the interfaces in use are created after the Peer-to-peer option has been enabled.|
|Axis||2341278||10.11 GA||Door forced open and Door held open events are not generated for readerless doors.|
|Axis||2151077||10.10 GA||When Synergis™ Softwire is upgraded from 10.7 to 10.9 SR1, OSDP readers fall offline until Synergis™ Softwire is restarted.|
|Axis||2121955||10.9 GA||OSDP readers configured to 115,200 bps do not produce
Workaround: Set the reader to a lower bit rate.
|Axis||771427||10.4 GA||When access is denied while the unit is offline, only a generic Access denied event is reported when the unit returns online. The reason for the denied access is lost.|
|Axis||691063||10.4 GA||Axis A1001: If the Door forced option is disabled and the Axis controller is disconnected from the Synergis™ unit, the card reader still beeps when the door is forced open.|
|Axis||654656||10.4 GA||The OSDP reader state is displayed as offline when the connection is lost between the reader and the Axis controller.|
|Mercury||2355360||10.11 GA||When a Mercury controller reconnects to the Synergis™ unit, offline events that should be logged as Access denied: Denied by access rule are logged as Access Denied: Out of Schedule instead.|
|Mercury||2353514||10.11 GA||If a reader is shunted and the Synergis™ unit restarts or is rebooted, the shunted readers are set back to an active state until the Synergis™ unit reconnects to the Access Manager.|
|Mercury||2222290||10.10 GA||When the two-person rule is in effect, a door set to either TurnstileMercury1 or TurnstileMercury2 only unlocks after every second badge.|
|Mercury||2211589||10.10 GA||The Maximum delay between card presentations setting from Config Tool is not applied. The value is fixed at 15 seconds for all Mercury controllers.|
|Mercury||1957490||10.8 SR1||Mercury EP with FICAM layout enabled: When Auxiliary Authentication Mode is enabled, cardholders with a long credential cannot have more than one credential.|
|Mercury||1957467||10.9 GA||Mercury EP4502 with TI EntryPoint plugin and Veridt PIV reader: Presenting a valid card might trigger reader errors.|
|Mercury||1350397||10.6 GA||Allegion Schlage AD-400 or LE: In apartment mode, an Access granted event while the door is locked unlocks the door and set Apartment: On, but the door does not stay unlocked.|
|RIO||2315828||10.11 GA||If the bus name includes spaces and ends with repeating characters, the bus
cannot be accessed.
Workaround: Do not include spaces in device names.
|Synergis™ IX||2354370||10.11 GA||On the Synergis™ IX unit's web page, changing the Module Type or Module Input values of Trouble Inputs might break functionality.|
|Synergis™ IX||2315882||10.11 GA||If no DHCP server is available on your network when the Synergis™ IX unit is powered on, the unit might not use the expected default 192.168.1.2 address.|
|Synergis™ IX||2243787||10.11 GA||Synergis™
IX input configuration is not
displayed or managed in Config
Workaround: Configure the input settings from the Synergis™ IX unit's web page.
|Synergis™ IX||2122008||10.11 GA||Intrusion detection area alarms must be acknowledged from the keypad of the Synergis™ IX unit, instead of from Security Desk.|
|Synergis™ IX||2158297||10.10 GA||When a cardholder enters a duress PIN into a Synergis™ IX intrusion keypad, the triggered duress event lacks the cardholder information.|
|Synergis™ IX||2100411||10.10 GA||When a door in an interlocked area denies REX or manual unlocks from Security Center due to another door being open, the reason is listed in the Synergis™ IX controller portal, but not in Security Center.|
|Synergis™ IX||2100379||10.10 GA||Access denied: Interlock events are not listed in Security Center.|
|Synergis™ IX||1956962||10.10 GA||Making configuration changes from the Synergis™ IX interface web portal causes the interface to momentarily drop offline in Security Center as the configuration reloads.|
|Synergis™ IX||1901465||10.10 GA||Activating Trigger pre-alarm events and setting a Pre-alarm delay time in Security Center correctly synchronizes the pre-alarm timer to the panel, but the setting does not get enabled in the web portal, and the check box to enable the pre-alarm in the portal does not work.|