Release Notes for Infosim StableNet, Version 6.7

Release Notes for Infosim StableNet, Version 6.7 Document Number RL-SN67-E&T-01 Revised: March 31 st 2014 These release notes provide the latest cumulative release information for Infosim StableNet Telco and Enterprise, Version 6.7. This document describes new features, changes to existing features, limitations, restrictions or caveats, upgrade instructions, and related information. These release notes supplement the Infosim StableNet documentation included with the distribution. Read these release notes carefully and refer to the upgrade instructions prior to installing the software. Document Contents Infrastructure Requirements StableNet Licensing StableNet 6.7 New Features StableNet 6.7 s StableNet 6.7 Fixed Issues Upgrade Procedures Legal Information

Infrastructure Requirements Hardware requirements StableNet Enterprise Due to the performance and memory requirements, the StableNet is not supported on 32-bit architecture platforms. This does not apply to the StableNet Web. Please contact sales@infosim.net if you need extended 32-bit architecture support. Version 6.7 will be the last version of StableNet where this extended support option is available. We are currently working on improvements to the Web to provide an alternative to 32-bit users. Infosim recommends using high-availability server hardware for both the StableNet Server and the StableNet Agents, including redundant power supplies, fan trays etc. For network connectivity, teamed or paired network interfaces connected to a high-availability network infrastructure should be used. Disk redundancy should be performed using hardware-based raid controllers either as Raid-1 Mirrored (Best) or Raid-5 Block-level striping with parity volumes. Recommended StableNet Server, Agent and sizing for 100,000 measurements: Server Agent CPU 4 Socket, 32-64 Cores 8 Cores 4 Cores RAM 64 GB 16 GB 8 GB Storage 2 * 300 GB (Raid-1) 2 * 1 TB (Raid-1) 2 GB Minimum StableNet Server, Agent and sizing for < 5,000 measurements and < 500 devices: Server Agent CPU 16 Cores 4 Cores 2 Cores RAM 32 GB 4 GB 4 GB Storage 128 GB 64 GB 1 GB

Database requirements StableNet Enterprise Free Database Software (Small Installations) MySQL 5.5.22 or higher Commercial Database Software (Large Installations) Oracle Enterprise 11g R1, R2 with Partitioning Software requirements StableNet Enterprise Server and Agent Windows Windows Server 2008 R2 Windows Server 2012 Windows Vista SP2 (x64 only) Windows 7 Windows 8 Linux Novell SLES 11 SP3 RHEL 6.x Ubuntu LTS 12.04 Novell SLES 11 SP3 RHEL 6.x Ubuntu LTS 12.04 OS X (> 10.8) Web Google Chrome 22.0+ Mozilla Firefox 19.0+ Internet Explorer 9.0+ Hardware requirements StableNet Telco Due to the performance and memory requirements, the StableNet is not supported on 32-bit architecture platforms. This does not apply to the StableNet Web. Please contact sales@infosim.net if you need extended 32-bit architecture support. Version 6.7 will be the last version of StableNet where this extended support option is available. We are currently working on improvements to the Web to provide an alternative to 32-bit users. Infosim recommends using high-availability server hardware for both the StableNet server and the StableNet Agents, including redundant power supplies, fan trays etc. For network connectivity, teamed or paired network interfaces connected to a high-availability network infrastructure should be used. Disk redundancy should be performed using hardware-based raid controllers either as Raid-1 Mirrored (Best) or Raid-5 Block-level striping with parity volumes.

Recommended StableNet Server, Agent and sizing for 150,000 measurements: Server Agent CPU 4-8 Socket, 32-64 Cores 8 Cores 4 Cores RAM 64-128 GB 16-32 GB 8 GB Storage 2 * 300 GB (Raid-1) 2 * 1 TB (Raid-1) 2 GB Minimum StableNet Server, Agent and sizing for < 5,000 measurements and < 500 devices: Server Agent CPU 16 Cores 4 Cores 2 Cores RAM 32 GB 8 GB 8 GB Storage 128 GB 64 GB 1 GB Database requirements StableNet Telco Free Database Software (Small Installations) Commercial Database Software (Large Installations) Oracle Enterprise 11g R1, R2 with Partitioning Software requirements StableNet Enterprise Server and Agent Windows Windows Server 2008 R2 Windows Server 2012 Linux RHEL 6.x Windows Vista SP2 (x64 only) Windows 7 Windows 8 RHEL 6.x Web Google Chrome 22.0+ Mozilla Firefox 19.0+ Internet Explorer 9.0+

Other requirements All devices under management must have their time synchronized to ensure correct analysis of messages from those systems. As a manual time configuration is liable to drift, Infosim strongly recommend using NTP time synchronization. The StableNet Servers, Agents and Databases must use static IP addresses. The use of DHCP for these critical servers is not supported. Any virus scanning software installed on the StableNet Servers must ignore the StableNet application folders. Scanning files within these folders will impact service performance. Intrusion detection systems, end-point protection systems or local software firewalls must not impact StableNet performance. Virtualization of the StableNet Server and the is supported if the virtual instance matches the physical hardware requirements as documented above. Virtualization of the StableNet Agent is NOT supported. StableNet Appliance No change to the StableNet Appliance s configuration is needed when running StableNet 6.7. StableNet Licensing Customers with an existing maintenance contract may upgrade to StableNet 6.7 free of charge. Please note: an updated license file may be required to complete the upgrade. Please contact a StableNet Support Agent for further assistance.

StableNet 6.7 New Features New Features Raspberry PI full featured StableNet Agent This agent can be used besides the standard monitoring to check IP SLA parameters and simulate VoIP, IPTV or Video Conferencing traffic with small sites or offices, instead of an economically often not applicable shadow router (more details are available on request). New Java Look & Feel The new look and feel improves the daily workflow and makes working with StableNet more efficient. New User Tracking Based on discovery data it is now possible to show which device or user is connected to which port in the network. This connection information is being stored and used as a basis for user tracking (e.g. which WLAN endpoint was used in a certain time period). New LogNG Module /Log File Analysis The log file reader LogNG is a simple state machine which reads data from a defined source, processes it with the help of a filter rule file and reports the processed results. The advantage of LogNG is, that you can choose from different flexible URL sources like file://, sh://, ssh:// and so on. The processing engine allows the use of regular expressions, variables and states. Using the client agent technology you can keep the log files on the observed system and simply forward the required information to StableNet. New Dynamic Reports can be predefined to enable dynamically generated content. For example a chart for all processors of the device or for all interfaces that were once down in the defined period can be generated. It is also possible to choose a top-n report and use the result as a filter to select the corresponding number of individual elements. Furthermore these reports will be made available as a "right click" option for devices or subtrees in the measurement tree. (This feature will be available in the first service release to StableNet 6.7) Enhanced Application and Business Process Monitoring More out of the box scripts for enhanced Application and Service Monitoring have been made available in this release (details in the listing further down below). Abort functionality is now supported for every job. Added thread count per job, maximum Execution Time per job and CPU Load Throttling (Improved Resource Management). Added basic discovery for Force 10 devices. Added basic discovery for Motorola Symbol devices. Added basic discovery for Alcatel Lucent devices (mainly GPONs).

Added basic discovery for Ubiquiti Networks devices. Added support for data import in XML discovery to import data like CDP, LLDP, FWD, ARP using script files which can utilize CLI, database, web and other data sources. Extended interface handler which can create auto measurements for interfaces based on database variables. Measurements (Application Monitoring) IBM AS/400: o Checking the scheduling and last execution of AS/400 jobs. Additional Linux business process scripts: o Checking of free memory. o Checking for processes in d-state between two measurement intervals. o Checking CPU load of processes which are above a certain threshold. o Checking the system load. o Checking the presence of a specified process (or service) in the list of running processes. o Checking free space on local mounts. o Checking the availability of NFS mounts. Additional Windows business process scripts: o Checking Windows performance counters. o Additional Windows Server measurement scripts (e.g. Kerberos, Active Directory). o Enhanced Windows Event Log Monitoring (remote or via Client Agent). Additional shared Windows/Linux business process scripts: o Monitoring files by file pattern in any given location (local/remote) including modification date. o Enhanced script for executing a shell command and simple output parsing. of existing Oracle database measurements and additional business scripts (details to be found in the StableNet product documentation). Monitoring for Application Servers based on JMX. Additional Templates (WMI and SNMP) are also provided with this StableNet release.

Agents Added local WMI measurement on client agent. Licence file check for normal/client agent was enhanced. and Change / NCCM Performance Improvement for Policy Checking. Create Jobs directly from selected devices or tables. Execute Jobs directly for selected devices or tables. Database Variable Extended (variables in WHERE Clause, Input Variables can be used). Info Command Extended (List of Error Matchers, List of Ignore Line Matchers, Partial Ignore Line Matcher). Config Jobs can be aborted by the user in the or by XML syntax. Improved Backup and Restore Support (e.g. TFTP Servers). Extended capability of automatic device config creation. Added support for backup/config of Adva (Covaro Brand) devices. Added support for reading operating system for Juniper NetScreen devices. Added support to backup Apcon devices. Added backup function for Extreme Networking using TFTP. Inventory Added MPLS Tunnel to Service Analyzer. Integration Enabled ticket module for ticket integration (Ticket module is now also available for StableNet Enterprise). Interface to FNT Command is supported (more details are available on request).

Added CLI parameters to Modify Attributes dialog. Added the ability to import/export maintenance intervals for business hour groups from and to a csv file. Added syntax highlighting in Database Variable Manager. Web : New FilterPlotServlet to find and plot measurements by measurement type and filter values. Web: Added new FilterStatusServlet to deliver measurement states matched by text filter. Added a new tab "All" to the Default Properties Dialog which shows all properties and allows searching for a property by name independent from the category of a property.

StableNet 6.7 s StableNet Agent Agent Added a feature to allow individually increasing/decreasing the disk size of agent stores. This is useful in scenarios where a larger number of agents is used like in the distributed syslog pre-processing. Single agents might have more or less disk space so the size of the stores can be increased/decreased since the global size setting might not fit here. Divided agent synchronization into two separate parts: agents and client agents based. This enables synchronization of the specific part if required. and Measurements Bug Fixed Improved error handling during processing of monitor-update elements. Added a feature to the XML that allows the importing of device connectivity data like CDP, LLDP, FWD and ARP entries by using a script. The script can be used to import the data from any data source like the command line interface of the device or external databases. This feature can be used if the data provided by the device via SNMP is wrong or insufficient. Improved discovery of Juniper NetScreen devices. The operating system is now read properly. Added basic discovery support for vendor "Force 10". Performance Added detection of Microsoft Windows Server 2012 R2 and Microsoft Windows 8.1 operating systems during device discovery. Enhanced operating system detection of Huawei devices. The license based product version is now included in the discovered operating system string. Added a new field in the discovery process to allow setting the device model via the XML. The field name is "devicemodel" and can be used in database variable and csv file based device blocks. Improved performance of discoveries. If the discovery has to handle many devices and most of these have few changes the performance has been improved a lot.

Backup and Bug Fixed Bug Fixed Performance Enhanced the device selection wizard in the job configuration dialog to allow the import of the device selection from a csv file. Added a check to ensure that there aren't multiple device info commands with the same name per device. If multiple commands with the same name are found, the backup job will abort and log the error. If multiple device info commands with the same name exist StableNet can only store one result for these commands and therefor duplicates were discarded. This lead to unexpected results. When connecting to IXIA devices the password is now masked in debug log if the login failed. Previously the password was readable in plain text. Fixed issue where the specific connection handler for Cisco WLC devices was only used for "Cisco" vendor but not for "Cisco WLAN" vendor. This is fixed now and in both cases the specific handler is used. Added support to backup and configure devices of the vendor "Adva Covaro". Optimized internal handling of REF placeholders used in Jobs and Database Variables. Improved handling of job results. This results in a major performance improvement on device backup jobs that check old backups to decide if a new backup has changes compared to the previous one and therefore has to be stored in the database. Policy, Lifecycle and Vulnerability Jobs Added a configuration structurer (pearl library) for RAD DATACOM devices to allow policy checks for these devices. Job Management Jobs Added a feature to create new jobs and fill the device selection from any table (Analyzer / Inventory / etc.). This allows filtering in various sources for a set of devices and creates a new job for exactly this selection. Added new menu entries in the "Job Analyzer" dialog. Job results that contain detailed information on devices (backup jobs, configuration jobs and policy check jobs) now allow using a "Jump To" and "Connect to " function as this functionality is also available in other parts of the.

and Weather Maps Weather Maps Added new replacement parameters in Report options. The new parameter $TYPE$ allows to replace the text in the legend of a chart with the monitor type of the displayed value(s). The new parameter $CHARTTYPE$ allows to replace the title of the chart with the chart type. The intended use of these parameters is to shorten the texts in the chart title and legend. Improved handling and display of legends in charts. Added a new chart type "Monitor Availability DNA Noise" which shows information about monitors that changed their state multiple times. This can be used to check for flapping monitors in a specific time interval. Added a new feature to include availability of images via URLs. User Interface Jobs Added the ability to import and export maintenance intervals for business hour groups from and to a csv file. Improved performance when selecting elements in the measurement tree from the measurement and monitor table. Added a confirm dialog to the "Edit Subtree Elements" feature to prevent accidental modifications of large numbers of elements in the measurement tree. Added a feature to create new jobs and fill the device selection from any table (Analyzer / Inventory / etc.). This allows filtering in various sources for a set of devices and creates a new job for exactly this selection. Improved handling of the "Global" tab in the Information Dialog. The table didn't have horizontal scrollbars which made it difficult to see all data. Added new menu entries in the "Job Analyzer" dialog. Job results that contain detailed information on devices (backup jobs, configuration jobs and policy check jobs) now allow using a "Jump To" and "Connect to " function as this functionality is also available in other parts of the. Improved the message in various confirm dialogs when working with the measurement tree.

Java Enhanced the transfer of Open Alarms, Action Events, Syslog Entries, Trap Entries and StableNet Log Entries from the server to the. All data will now be compressed. This reduces the time to transfer the data and the generated traffic. The "About" dialog now contains information about the number of entries transferred as well as their respective size. Platform Bug Fixed Feature Performance Added a new default property for the web - "Fetch GeoMap data via StableNet Server". This property controls whether GeoMap data is fetched either via the StableNet server or via using the internet connection of the workstation the is running on. Using the StableNet server to fetch GeoMap data allows the use of an internal OpenStreetMap server. This is useful in restricted environments where an internet connection is not available. Fixed issue where automatic backups of StableNet 's metadata lead to a corrupt archive file for tables bigger than 2GB. Added the agent id to entries in the audit log. Reduced the start-up time of the server using parallel reading and processing of data during the server start-up process. Improved log messages during the database maintenance. Web Performance Improved performance when handling large numbers of maintenance entries in the "Maintenance Table". Improved the performance of the maintenance view.

StableNet 6.7 Fixed Issues The following fixes apply to StableNet Version 6.5 initial release dated August 8 th 2013. All fixes are also included in the latest StableNet Service Pack dated April 1 st 2014. Agent Alarming Backup Job Backup Jobs Database Database Database Database Database Fixed NetFlow handling with Cisco Nexus devices. Fixed issue where action events for monitors were sometimes processed in the wrong order. Fixed issue when configuring a backup job. The backup server settings couldn't be changed. Fixed issue related to device backups of Cisco devices. s with old firmware use a different error message syntax for some commands which was not handled properly. Fixed issue related to the database table for stored "Database Variables" which was syntactically wrong for fresh installations. Installations updated from previous versions of StableNet were not affected. Fixed issue in the creation of sn_measrmnt_group table during first installation of StableNet. Installations updated from previous versions where not affected. Fixed issue during full maintenance where the compression of measurement data could fail if measurement data has the exact same timestamp as a database table partition border. Fixed issue during the database maintenance. In rare cases the data aggregation could fail due to an issue with the primary key after the data was compressed. This lead to an internal error and the aggregation couldn't finish properly. Fixed issue in the partitioning detection related to MySQL databases. If StableNet was configured to use a database name different from "pme" (the default value) the detection if partitioning is supported by the database failed. This is a very important bug fix if a non-default database name is used. Fixed issue in the search dialog of the device backups due to the search term not being case insensitive. Filtering for agents in the " Selection" tab is now working as expected. Optimized handling of software and license updates on IXIA devices. The job will wait until the device responds again and will report the status correctly. Previously the job was reported as "failed" when there was a timeout due to a device reboot. Fixed issue during update of Cisco operating system when using an image. Required commands were not sent in the proper order. Fixed issue where new binary backups of device configurations were always recognized as equal to the last valid backup stored in StableNet. The new backup was then discarded. This now works as expected. Fixed issue where backups of devices could contain spaces in the file path when stored to disk. Since not all devices can handle filenames with spaces properly restoring these backups didn't work for these devices. Fixed issue where empty "Ignore Line Matcher" settings in Info Commands were treated wrong and in some cases ignored all lines. Fixed issue where the timeout in the connection handler for IXIA devices was

too low. The login procedure was sometimes aborted because the device didn't respond in time. This can be caused by external authentication like TACACS or low latency of the connection to the device. Fixed issue in the command line interface connection handler for old Foundry (Brocade) devices that do not support the "terminal length 0" command. Fixed issue in the command line interface connection handler for Cisco devices. The detection of the operating system was improved to be more reliable. Improved error handling in the command line interface connection handler for Cisco devices when switching to "enable" mode. In some cases errors were not recognized and subsequent commands didn't work due to the missing privileged mode. Fixed issue in the command line connection handler for RAD devices: The login prompt was not properly matched when connecting to a device using telnet. Fixed issue in the command line connection handler for Juniper devices. Special prompts on master/slave device pairs were not properly parsed and an error was produced. Fixed error handling in the command line connection handler for Cisco devices while switching to privileged mode. Error conditions were not recognized in rare cases. Added special handling for operating system updates on Cisco devices when the system boot image is not present. Added a workaround for an issue during the OS update on Cisco devices. If the "show version" command doesn't contain the system image name a "dir" command will be used as fall back to get the name of the system image. Fixed an issue where auto measurements for the StableNet Agent were not created properly. Fixed an issue related to the monitor-update element in XML Discoveries. Column names in database variables used in monitor-updates were used case sensitive where a case insensitive behaviour was expected. Fixed the XML scheme for the subgroup element. The scheme didn't match the actual implementation of the element and supported attributes which were actually not supported. Measurement descriptions can be changed in the xml discoveries by using monitor overrides. Errors during the discovery of IP SLA capabilities won't stop an XML discovery job but will let the discovery continue with the next device. Information on how to access devices via the command line interface (cli) will not be removed if you discover devices again without cli information. Fixed a race condition during the discovery. If a new maintenance is created for measurements and the measurements are modified in the XML at the same time the maintenance entry could be lost. This happened only in very rare cases. Fixed issue with some properties specified in the XML discovery file that were lost during the discovery. Fixed issue during handling of monitor-update elements in the xml discovery. In some cases too many monitors were updated because a specified filter was not applied. During the discovery of a device the agent is updated with the agent executing the discovery if the device already existed before. Prior to this fix

the agent was not updated. This was not intended and thus, the handling is correct now. This can have an impact on existing discoveries if keeping the initially used agent is expected. Fixed issue during discovery of Cisco Nexus devices where the model name was taken from the wrong entity module. Prior to this the model shown was for example "Fabric Extender Module: 48x1GE" Fixed issue during creation of syslog measurements in the XML. The attributes "severity", "priority" and "info" of the syslog measurement didn't support variables. Improved handling of LLDP and CDP data during the discovery. Fixed issue where the original creation date of measurements sometimes was lost when a discovery tried to create a measurement which already existed before. Added new fields for device specific replacement parameters. The fields $%deviceagentid$, $%deviceagentname$, $%deviceagentip$ and $%deviceagentport$ can be used for filtering on the respective properties of the device's agent. Fixed issue during discovery where agent settings for measurement groups were not handled correctly if elements below the group were assigned to different agents. Added missing short interface names and improved matching of interface names for connectivity detection on Cisco Nexus devices. Fixed issue during the discovery. Additional checks were performed that increased the duration of the discovery job. These checks were redundant and are now only performed when actually required. Fixed issue during the discovery of Cisco devices. If sensor modules were detected the creation of cpu and memory measurements were skipped. Fixed issue related to short interface names on Cisco Nexus devices. Fixed issue during the discovery of cisco devices. Details about sensors can be found in the module name or in the module description. After this fix both possibilities are checked and the correct field is used to generate the measurement name. Fixed issue during the discovery of CDP neighbours. Detection of invalid IP addresses was improved. Prior to this an error was reported when invalid data was parsed. Fixed issue related to FWD data on Cisco devices. While trying to read FWD data per VLAN the previously found FWD data was lost if the device didn't respond. Changed the behaviour of device discoveries. Now all discovery related properties (discovery and automeasure) are stored per device. These stored parameters will be used for the rediscovery. This allows for an easier overview of the properties used f or the discovery of a specific device. Fixed issue in the rediscovery of a device after a manual modification in the. In some cases the device specific discovery parameters were not used. Fixed issue in the XML where resetting alarm groups and alarm parents didn't work in the monitor-update element. Fixed issue in XML Discoveries where subgroup elements didn't allow using variables in the relative path attribute. This was not intended and now works as expected. Removed deprecated attribute "type" for monitor overrides. Please use

Feature Feature Feature Feature Generic Generic Generic Generic Generic "filtertype" now. Fixed issue in the XML. When deleting unused groups in the measurement or inventory tree the application was stuck in an endless loop if the simulate flag was enabled. Improved handling of internal caches. This could lead to an optimized memory usage in some cases. Improved handling of internal caches. This will optimize memory usage in some cases. Optimized the internal heuristic to detect an overflow related to interface counters. Extended list of available operators for "Derived Measurements". A new operator "xor" was added. Fixed security issue where internal servlets allowed reading files outside the StableNet installation directory. Fixed issue during restart of the StableNet server. The StableNet server restarts itself if it detects another StableNet instance accessing the database (HA environment). This restart failed sometimes and the StableNet server was shut down. Changed the SSL ciphers for the web portal. Some old and less secure ciphers were removed. Fixed issue in the StableNet Database Manager related to very large tables. On some operations an error was reported if a table had too many rows. Removed the expert default property "expert_discovery_ping_packet_interval". Changing this property was not recommended and led to various issues with ping measurements. Fixed issue with the "Services Management" dialog. Changes were saved when the "Cancel" button was pressed. DNS resolving is now also working in the connectivity view and the device information dialog. Fixed issue where the export of tables to csv format didn't work properly if the table columns contained quoted text. Fixed issue when creating new derived rules. The combo box for the selection of monitors which should be used in the rule was only displaying a subset of the monitors. This is fixed and all monitors (within the selected agent) are now selectable. Fixed issue in the measurement tree where parent groups of elements where shown even if the user didn't have rights to them. This is fixed now and elements with missing rights on parts of the tree path from root to current element will be moved to a "Lost and Found" group. Fixed issue in the "Agent Update Manager" dialog. When the dialog was open while an agent disconnects an error was shown. Fixed issue where SNMP and SNMP Trap templates created from a measurement wizard were not stored in the database. Fixed issue where the "Connectivity" table in the " Information" dialog didn't show the interface description. Fixed issue when importing or deleting entries in the "End-of-Life Manager" dialog. An error was shown while the content of the table was being updated. Fixed issue during the import of reports that had a "Single" execution trigger configured. Fixed issue during the modification of "Derived Rule" measurements where an

error was shown in some cases. This is fixed now and the internal handling is correct. Fixed issue where the inventory link state was not updated properly. This happened only in rare cases. Fixed issue where the selection of a proxy alarm in the "Open Alarms" table selected the wrong element in the list. Fixed issue during the import of Config Snippets and Vulnerabilities. The "Inverted" flag in device filters embedded in the imported data was handled incorrectly and set the "Regex" flag instead. Fixed issue when selecting multiple open alarms in the "Open Alarms" table. The element which causes the alarm is also selected in the measurement tree. This didn't work properly when multiple alarms were selected. Fixed issue when modifying multiple open alarms at once. Changes are now applied to all selected open alarms. Prior to the fix the change was only applied to the first alarm. Fixed issue related to the "Edit Subtree Elements" feature. This didn't work properly for trap measurements. Fixed issue during the creation of "Derived Measurements". Some elements where not displayed due to an internal error which made it impossible to use these elements in the measurement. Fixed issue in the Connectivity View. Searching for a device name actually searched for all devices where the search text was included in the device name. This lead to an unexpected result when the search text for example was "device-1" and the results also contained entries for "device-10". Fixed issue where the feature "Edit Subtree Elements" did not work if the node "Status" was selected in the measurement tree. If this node was selected an error was reported. Fixed issue related to VMware hosts. The connectivity of virtual machines inside these hosts was not displayed properly. Fixed issue related to the Open Alarms table. In some cases the calculation of the open alarms count was wrong. Fixed issue related to the Open Alarms table. In rare cases the acknowledge flag of open alarms was lost after a server restart. This was caused by an internal race condition. Fixed issue related to monitor alarm groups. Alarm groups are now being correctly displayed as "inherited" if this is actually the case. Before the fix the "inherited" flag was also displayed if the alarm group was explicitly set on that monitor instead of being applied from a parent element. Fixed issue where the opened dialog when searching in combo boxes didn't scroll to the selected element. Prior to the fix only the topmost element was visible. Fixed issue where the Database Variable Manager in the Automation Theme was only available if the "policy" license module was available. Since database variables can also be used in XML jobs this was changed. Fixed issue where the field "Report Info" on measurements was truncated to a length of 64 characters when being stored in the database. This was wrong and the correct maximum length of 255 characters is being used now. Fixed issue related to "Derived (Rule)" measurements. The flags "Immediate Alarm" and "Maintenance Alarm" where in rare cases deleted after the modification of a measurement. The "Log Colour Mapping" menu entry in the options menu now uses the

Jobs Jobs Jobs Jobs Jobs Jobs Jobs Performance Improvement correct user role to determine if it should be available for the current user. Improved error handling during import of reports. Fixed issue in Server Log Dialog. The dialog was sometimes displayed in the background and therefore was hidden. Changed the user role "Web Portal" to "NOC" which is the correct terminology for this role. Fixed issue during the serialization of Custom Service Jobs where the "Rediscover all devices before starting service" setting wasn't stored in the database. Fixed issue where devices have been used in jobs when no valid credentials were provided. These devices are skipped now and reported in the Job Analyzer. Fixed issue with the new feature to create jobs and populate the device selection from any table (Analyzer / Inventory / etc.). This didn't work in the Policy Analyzer. Fixed issue with backup jobs where the global default credentials were not used properly. The username was used for the username and password field. Fixed issue in the " Automation" theme. An error occurred while using the "Jump To Config" menu entry on a device configuration backup. Fixed issue during processing of job parameters for "Custom Service" jobs. Fixed issue during check for modifications of Config Snippets. The snippet type was not included in the check. Changing the snippet type therefore wasn't recognized as a change and neither a new revision of the snippet was created nor was the snippet stored in the database. Fixed multiple minor issues related to the measurement tree. During discoveries the is updated frequently which could have led to rendering issues in the tree. Fixed issue related to the "Stroke Line" element in reports. The error occurred during the export of reports in PDF format. Fixed issue where configuration backups were sometimes not found in Backup Diff reports. Calculation process of the last interface state change was fixed. If the system uptime counter in snmp had an overflow (due to integer data type) the calculation could have been wrong and the calculated value was negative. Fixed issue related to filters in the reporting function. Added title, subtitle and legend to report elements shown in the browser when the report element is opened using the "Web" button in the Analyzer. Prior to this these fields were missing. Added a unit for total bars in reports and in the Analyzer. Fixed issue related to EOx checks on Cisco devices. The device sometimes provided the vendor without case sensitivity. This prevented some EOx checks from working correctly. Fixed typo in the validation schema of XML report definitions. This has caused issues during the import of reports. Fixed a race condition created by heavy concurrent usage of the reporting function. This has in some cases lead to false values in reports. Fixed miscalculation in the "total" column that is used in NetFlow statistics tables. Fixed issue where an error during importing a report lead to excessive logging.

Improvement Fixed issue related to EOx and Vulnerability reports where the TopN setting of the report was ignored and all contents was displayed. Fixed issue in reporting where filtering on data that contains a date value didn't work properly. The date provided in the filter was not parsed correctly. Added missing colouring in EOx module reports. Furthermore these reports now use the vendor of the device instead of an empty value in case the module does not contain a vendor. Fixed issue where the date of End of Sales was not properly shown in EOx reports. Improved software version handling of devices in EOx checks. Versions are now being compared based on the version model of the respective vendor. Fixed issue in the open alarms statistics where the severity of proxy alarms was not displayed correctly. Renamed columns in the "Interface Busy Hour Table" report. Columns were labelled as "Avg In/Out" while the correct naming is "Max In/Out". Fixed issue during creation of reports for users with limited roles/permissions. Fixed issue in the "Interface Daily Traffic Sum" report. The time axis didn't cover the whole reporting interval if there was not enough data available to fill the interval. Fixed issue in the "Interface Daily Traffic Sum" report where a wrong interval was used to calculate the values. This has sometimes led to gaps between the actual measurement points. Fixed issue in syslog and trap reports where the column "Matched Template" was missing in the report's table header. Renamed various chart value descriptions from "standard deviation" to "std deviation" to make naming more consistent. Fixed issue related to chart legends. Overriding them did in some cases not work as intended. Fixed issue in the "Inventory Summary" report where the device state was not always reported correctly. Added support of quoted strings for user script measurements. For example "<" and ">" can be used inside of measurement result comments now. job results now also contain information about updated measurements. Enhanced importing of EOL data and colouring of EOL reports. Improved error handling of external template measurements in xml discoveries. The button "Fixate Selected s" in a job's device selection wizard was renamed to "Save Selection". Enhanced the export of table contents to csv format. If tables are filtered only the filtered data is exported. Before the export always contained all data. Added some checks to prevent issues during the creation of StableNet users. Text fields shouldn't contain a trailing space. This leads for example to issues during the login when the space was accidently added after the username. Added a dialog to show the member states of maintenance entries in the "Maintenance Entries Management Dialog". This was missing in the Web. Changed the texts of error messages in jobs related to the "4-eyes principle" to provide clearer information about the reason for this error. In various dialogs the text "Controller" was replaced with "Agent" to make

Improvement User Roles Weather Maps Weather Maps Weather Maps Weather Maps Web Portal naming more consistent. Renamed the field "External Authorization" in the user settings dialog to "External Authentication". Fixed a minor error that was raised when sorting a table. Users are no longer allowed to see traps or syslogs of devices that belong to unmanaged devices or to devices where the user does not have access to. Fixed issue where the "Jump To" menus in weather maps were sometimes not enabled and therefore not available. Fixed issue during creation of weather maps. An error occurred if the default measurement for a device was not found so in case a device had no measurements at all this happened. Fixed issue while creating URL images in weather maps. Prior to the fix it was possible to add other weather map via a URL. This could lead to an internal deadlock. Fixed internal issue related to storing positions of newly created weather map elements. Added function to remember the current zoom state in weather maps in order to restore this value after an automatic refresh of said weather map.

Upgrade Procedures Please note, the update procedure will make adjustments to the database tables. While this process is fully automatic, it will require some time to complete and sufficient available storage space on the database server. Please contact a StableNet Support Agent for more information. Before you start updating your StableNet installation, please make sure that you: Because StableNet 6.7 is using now Java Version 7 the has to be reinstalled using the installer Because StableNet 6.7 is using now Java Version 7 all agents and client agents have to be installed using the respective installers The reporting format has been enhanced. Please check all your existing reports if they are affected by these changes (e.g. columns have been added). Check that the repository is up-to-date. New scripts are installed into the snagent\userscript folder and have to be copied into the repository prior to the update. Update the Client s on Citrix or RDP servers. Check the Default Properties in "Default Property Editor" and update them if needed. Check the XML for deprecated syntax. An editor with XML validation functionality can help to look for warnings in the log file. Check if all user groups have correct rights configuration as new functionality has been added. Check the web portal for menu access as new menus have been added.

Legal Information Copyright 2006-2014 Infosim GmbH & Co KG Infosim, StableNet and the Infosim logo, whether or not appearing with the registered symbol, are registered trademarks of Infosim GmbH & Co KG, hereafter called Infosim. All third-party trademarks and/or company names are the properties of their respective owners and are hereby acknowledged. This document contains information that may be subjected to periodic changes or updates. At the time of writing, Infosim has made all reasonable efforts to ensure that the statements contained within this document are accurate. No warranties are expressed or implied. Applicability or provision of services is subject to Due Diligence. No part of this document may be reproduced by any means nor modified, decompiled, disassembled, published or distributed, in whole or in part, or translated to any electronic medium or other means without the written consent of Infosim. All rights, titles, and interest in and to the software and documentation are and shall remain the exclusive property of Infosim. INFOSIM DISCLAIMS ALL WARRANTIES, CONDITIONS OR OTHER TERMS, EXPRESS OR IMPLIED, STATUTORY OR OTHERWISE, ON SOFTWARE AND DOCUMENTATION FURNISHED HEREUNDER INCLUDING WITHOUT LIMITATION THE WARRANTIES OF DESIGN, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE, AND NONINFRINGEMENT. IN NO EVENT SHALL INFOSIM, ITS PARTNERS, NOR ITS SUPPLIERS BE LIABLE FOR ANY DAMAGES, WHETHER ARISING IN TORT, CONTRACT OR ANY OTHER LEGAL THEORY EVEN IF INFOSIM HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES. All rights reserved.