User guide

Release Notes
Fingerprint Analysis
44
• [Ref. #24578] When the GSM is restarted while the Event Log Viewer or Incident Log Viewer is
open in Auto-Update mode, a
stackOverFlowError message may appear in the Java
Console window.
Workaround: If using iControl Navigator, re-open the Event Log Viewer (or Incident Log
Viewer). If using iControl Web, refresh the Web page.
•
[Ref. #21735] When the Create an incident for each alarm automatically option is not
enabled, and the Resolved filter is set to No, the Incident Log Viewer may still show
resolved incidents.
Workaround: Assuming the Clear filter is also set to No, manually clear the unwanted
incidents.
•
[Ref. #21720] Some router drivers (e.g. Emulator, SW-P-02, ETL, HRS-1801, VikinX Modular,
NV9000, Pesa, Pesa USP, RC2000) publish crosspoint status updates to the Event Log even
when there is no change on the matrix.
•
[Ref. #21255] When you perform a filtered search while the Log Viewer’s auto-update mode
is active, rows that do not match the specified criteria may eventually appear among the
filtered search results.
Workaround: Disable the auto-update mode, or click the Search button to remove
unwanted results from the view.
•
[Ref. #21197] When you perform a filtered search based on a duration, rows that do not
match the specified duration may appear among the search results.
•
[Ref. #18445] After a GSM restart, it could happen that the Event and Incident Log
Configuration window does not open when you click Log properties on the Incident
Viewer’s File menu.
Workaround: Close and reopen the Incident Viewer.
•
[Ref. #17340] If the system clock on the client PC with iC Navigator is behind compared to
the Application Server’s, incidents shorter than the difference between the two clocks will
appear with a duration of zero in the Incident Viewer. Likewise, an incident duration may
briefly stall at zero before starting to increment, depending on the time difference
between client and server.
•
[Ref. #17032] Log entries are timestamped using the client PC’s internal clock rather than the
Application Server’s. This can cause some correlation issues when viewing log entries,
including acknowledgements being ignored on some client PCs.
Fingerprint Analysis
• [Ref. #29630] In iControl installations, the following parameters and limitations currently
apply:
• If you have a Dell PowerEdge R200 Application Server, iControl supports a maximum of
40 audio fingerprint comparisons
• If you have a Dell PowerEdge R210 Application Server, iControl supports a maximum of
60 audio fingerprint comparisons