nimsoft server 512 upgrade guide · 2014. 8. 5. · installation of nimsoft infrastructure is part...

Nimsoft Server 5.12 Upgrade Guide

Nimsoft Server Upgrade Guide v5.12 2

Copyright Notice Legal Notices

Warranty

The material contained in this document is provided "as is," and is subject to being changed, without notice, in future editions. Further, to the maximum extent permitted by applicable law, Nimsoft Corporation disclaims all warranties, either express or implied, with regard to this manual and any information contained herein, including but not limited to the implied warranties of merchantability and fitness for a particular purpose. Nimsoft Corporation shall not be liable for errors or for incidental or consequential damages in connection with the furnishing, use, or performance of this document or of any information contained herein. Should Nimsoft Corporation and the user have a separate written agreement with warranty terms covering the material in this document that conflict with these terms, the warranty terms in the separate agreement shall control.

Technology Licenses

The hardware and/or software described in this document are furnished under a license and may be used or copied only in accordance with the terms of such license.

No part of this manual may be reproduced in any form or by any means (including electronic storage and retrieval or translation into a foreign language) without prior agreement and written consent from Nimsoft Corporation as governed by United States and international copyright laws.

Restricted Rights Legend

If software is for use in the performance of a U.S. Government prime contract or subcontract, Software is delivered and licensed as "Commercial computer software" as defined in DFAR 252.227-7014 (June 1995), or as a "commercial item" as defined in FAR 2.101(a) or as "Restricted computer software" as defined in FAR 52.227-19 (June 1987) or any equivalent agency regulation or contract clause. Use, duplication or disclosure of Software is subject to Nimsoft Corporation’s standard commercial license terms, and non-DOD Departments and Agencies of the U.S. Government will receive no greater than Restricted Rights as defined in FAR 52.227-19(c)(1-2) (June 1987). U.S. Government users will receive no greater than Limited Rights as defined in FAR 52.227-14 (June 1987) or DFAR 252.227-7015 (b) (2) (November 1995), as applicable in any technical data.

Nimsoft Server 5.12 Upgrade Guide 3

Trademarks

Adobe®, Acrobat®, Acrobat Reader®, and Acrobat Exchange® are registered trademarks of Adobe Systems Incorporated.

Intel® and Pentium® are U.S. registered trademarks of Intel Corporation.

Java(TM) is a U.S. trademark of Sun Microsystems, Inc.

Microsoft® and Windows® are U.S. registered trademarks of Microsoft Corporation.

Netscape(TM) is a U.S. trademark of Netscape Communications Corporation.

Oracle® is a U.S. registered trademark of Oracle Corporation, Redwood City, California.

UNIX® is a registered trademark of the Open Group.


Contact Nimsoft

Contact Technical Support

For your convenience, Nimsoft provides one site where you can access the information you need for your Nimsoft products. At http://support.nimsoft.com/, you can access the following:

■ Online and telephone contact information for technical assistance and customer services

■ Information about user communities and forums

■ Product and documentation downloads

■ Nimsoft Support policies and guidelines

■ Other helpful resources appropriate for your product

Provide Feedback

If you have comments or questions about Nimsoft product documentation, you can send a message to [email protected].


Document History Version What’s new?

Version 5.10 Version 5.11

■ Initial version

■ Minor updates

■ Adjustments for NMS 5.11 Version 5.12

■ Adjustments for NMS 5.12


Contents Copyright Notice 2

Contact Nimsoft 4

Document History 5

Contents 6

Chapter 1: Nimsoft Server 8

Introduction .......................................................................................................................................................... 8 Overview ............................................................................................................................................................... 8 Prerequisites ......................................................................................................................................................... 8

Installation requirements ................................................................................................................................ 9 Minimum system recommendation ................................................................................................................ 9 Increased database storage requirements ..................................................................................................... 10

Preparation ......................................................................................................................................................... 11 Installation/upgrade ............................................................................................................................................ 11 Verification of successful installation/upgrade ..................................................................................................... 13 Upgrade of indexing for sample data tables ......................................................................................................... 14 Failure ................................................................................................................................................................. 16

Chapter 2: Main Feature changes 17

General functionality ........................................................................................................................................... 17 New operating system platforms supported.................................................................................................. 17 New database platforms support for the NIS database .................................................................................. 17

Windows consoles ............................................................................................................................................... 17 Infrastructure Manager................................................................................................................................. 17

Probes ................................................................................................................................................................. 17 ACE............................................................................................................................................................... 17

Component changes and fixed problems from 4.3 to 5.12 18

Enterprise Console (from 3.43.1)................................................................................................................... 18 Infrastructure Manager (from 3.83.1) ........................................................................................................... 18 Service Level Manager (from 4.71) ................................................................................................................ 18 Alarm Subconsole (from 2.65.1) .................................................................................................................... 18 Dashboard Viewer (from 1.30) ...................................................................................................................... 18 Webpublish (from 2.85) ................................................................................................................................ 18 LogViewer (from 1.1.3) ................................................................................................................................. 18 Dr. Nimsoft (from 1.5.3) ................................................................................................................................ 19 distsrv (from 5.00) ........................................................................................................................................ 19


hub (from 5.12) ............................................................................................................................................ 19 robot/controller/spooler/hdb (from 5.12) ..................................................................................................... 20 install_unix (from 4.42) ................................................................................................................................. 21 nas (from 3.43) ............................................................................................................................................. 21 as400 robot (from 4.01) ................................................................................................................................ 22 group_server (from 2.62) .............................................................................................................................. 22 httpd (from 1.41) .......................................................................................................................................... 22 nimldr (from 3.42) ........................................................................................................................................ 22 dashboard_server (from 1.70)....................................................................................................................... 22 variable_server (from 3.40) ........................................................................................................................... 23 data_engine (from 7.56) ............................................................................................................................... 23 report_engine (from 7.81) ............................................................................................................................ 23 sla_engine (from 3.03) .................................................................................................................................. 23 NIS Manager (from 2.2.0) .............................................................................................................................. 23 audit (from 1.11) .......................................................................................................................................... 23 qos_engine (from 2.06) ................................................................................................................................. 23 cisco_monitor (from 2.80)............................................................................................................................. 23 interface_traffic (from 4.70).......................................................................................................................... 24 net_connect (from 2.40) ............................................................................................................................... 24 ace (from 1.35) ............................................................................................................................................. 24 discovery_agent (from 2.14) ......................................................................................................................... 25 discovery_server (from 2.13) ........................................................................................................................ 25 rsp (from 2.50) .............................................................................................................................................. 25

Chapter 3: Known Issues 26

UMP may need some handling after an upgrade to NMS 5.12 ....................................................................... 26 SDP is not supported with NMS 5.1x or later ................................................................................................. 26 Deploying changes in a package back into local archive ................................................................................. 26 Occasionally some probes do not start after installation................................................................................ 26 Microsoft Vista, Windows 7 and Windows 2008 issues .................................................................................. 27 AIX computers not found by discovery, using SNMP ...................................................................................... 27 Discovery Agent ............................................................................................................................................ 27 Uninstalling Nimsoft, using Add/Remove Programs in the Control Panel ....................................................... 27 Probes not activated after Nimsoft Server installation ................................................................................... 28 Activating discovery and configuration of existing interface_traffic probe on the server ................................ 28


Chapter 1: Nimsoft Server

Introduction NMS 5.12 is a service release of NMS 5.0 with some functional additions. The previous official release was Nimsoft Server 4.3x, and several of the modules which constituted that release have later been replaced by newer modules, which contain a combination of new features and corrections of bugs. Please take notice of the steps described later in this document in order to safely install this software on your system(s).

Overview NMS 5.12 contains a number of new features and component modifications and also several corrections and updates on different components. This document describes the new features in NMS 5.0 and NMS 5.1x, and it also contains a detailed list of fixed bugs and changes from Nimsoft Server 4.3x to 5.12.

Prerequisites Nimsoft Server can be installed on computers running operating systems:

• Microsoft Windows 2003. • Microsoft Windows Vista (SR1). • Microsoft Windows 7. • Microsoft Windows 2008 / Windows 2008 R2.

Please note that certain tasks require Administrator privileges on Microsoft Windows 7, Microsoft Windows Vista and Microsoft Windows 2008 computers. See the section “Microsoft Vista, Windows 7 and Windows 2008 issues” for further descriptions.

• Linux RedHat versions 4 and 5 • Linux SUSE (SLES) versions 10 and 11 • Solaris version 10


Installation requirements Use a login with sysadm privileges when installing or upgrading Please use a login with sysadmin privileges when installing or upgrading to NMS 5.12:

• If using an existing database, make sure that the login used for installation/upgrade maps to the database’s dbo.

• If database is created by the Nimsoft Server installation, the database's dbo will automatically be mapped to the login used in the installation.

Installing on one or two machines? When installing a small system, you may install the components involved on one machine, otherwise we recommend installing on two servers. As a rule, if your Nimsoft installation shall handle more than 1000 QoS messages per minute, we recommend to install on two servers; one for the Nimsoft components and one for the database. Installing one or more Hubs? It is recommended that at least two Nimsoft Hubs should be installed on the same Domain and network to avoid loss of user/security data, such as Nimsoft user definitions ACL’s etc., in case your Hub computer crashes. With more than one Hub, this information is mirrored between the Hubs.

Minimum system recommendation Database Server: - 2 CPUs - 3+ GHz - 2-4 GB RAM (Memory requirement is dependent on number of measurements, sample rate and retention period. More memory than 4 GB will often be required.) - 500+ GB * (Should be RAID 10 for performance and availability) Nimsoft Server: - 1 CPU - 3+ GHz - 2 GB RAM - 100 GB Disk

* Recommended disk configuration: - Operating system on a separate disk. - Transaction log on a separate disk. - Data on a separate disk (or Raid 10).


Installation note The installation contains three main components:

- Nimsoft Availability Server - Nimsoft SLM Server - Nimsoft Discovery ACE Components

During the Setup Wizard, you have the option to install one or more of them. You must ensure you can access the appropriate database; Oracle 11.1 or higher, MYSQL 5.1/5.5 or Microsoft SQL Server 2005/2008/2008 R2 (if you are planning to install a production system) alternatively Microsoft SQL Express (if you are planning to install an evaluation/demo system). Note: For NMS 5.12, database free space check is not implemented for Oracle and MySQL. Note: To install Service Level Manager component on Windows, you also need MDAC 2.8 or newer installed. The database must be case insensitive when handling queries. Installation of Nimsoft Infrastructure is part of the Nimsoft Server installation. If you want to install Nimsoft Infrastructure on an additional UNIX system, the following UNIX systems are supported:

- AIX - HP-UX - Linux - Solaris - TRU64

Note: Increased memory usage when using Dynamic Reports Provided that the Dynamic Reports option is activated in the Report Engine probe, this probe will generate Dynamic Reports based on QoS data found in the Dynamic groups defined in the new Group Server Probe. These reports will be made available in the Nimsoft Service Level Manager and in the Nimsoft Server application. Be aware that this will result in increased memory usage.

Increased database storage requirements The data_engine version 7.53 (NMS 4.3x) changed the set of indexes which it creates on the sample data tables RN_QOS_DATA_xxxx. However, this does not apply to existing RN_QOS_DATA-tables and they will continue with the old index set until updated as described in section Upgrade of indexing for sample data tables.


In general the increased requirement for storage will range from 25 to 50%, where the increase will be about 50% if you start with an installation which have only the clustered index on the sample data table. To illustrate the increased requirements wrt disk, let's assume that we have a table RN_QOS_DATA_0001 which required about 20GB storage when using NMS 4.2 and earlier. If upgrading to f.ex. NMS 5.1 and at the same time upgrading the indexes as described in this section, the same table will now require approximately 30GB storage

Preparation NOTE: Before preparing for the installation/upgrade, make sure you’ve read and understood the contents of Chapter 3 – Known issues! Please make sure that you make a backup of your database. NMS 5.12 contains a non-reversible upgrade script that changes the database structure of some tables. Upgrades from server version 4.1x, version 4.3x, version 5.0 and version 5.1x are tested for version 5.12. If you have version 3.35 or version 3.50, please upgrade to version 3.60 first. You will find server version 3.60 at http://support.nimsoft.com/downloads/360/nimBUS server.exe. Upgrading to version 3.60, please check upgrade guide http://support.nimsoft.com/downloads/360/NimBUS Server 360 Upgrade Guide.pdf.

Installation/upgrade The installation of NMS 5.12 consists of a chain of installations of the associated modules. Some of these modules may request that the system should be restarted. DO NOT restart your system until all modules have been installed. All existing modules will be replaced when installing Nimsoft Server 5.12 as an upgrade. You may choose more freely which modules you want to install when installing Nimsoft Server for the first time on a system. Note: If you want to install the Service Level Manager component on windows using MS SQL Server, you also need MDAC 2.8 or newer installed. If not, the installation wizard will be stopped, and you must upgrade to MDAC 2.8 or newer before starting the installation wizard again. This is the recommended sequence of steps involved in upgrading a Nimsoft domain consisting of several hubs and robots:


- Identify the Nimsoft systems containing Nimsoft Server and upgrade these systems by starting Nimsoft Server.exe. In most cases, the Nimsoft Server is running on the same computer as the Nimsoft Hub.

- On one of the upgraded Nimsoft Servers, find the URL to the Nimsoft Server web page by double-clicking the icon named “Nimsoft Server” on the desktop.

- Identify other systems which contain Nimsoft Infrastructure (Control Panel->Add/Remove programs) and upgrade these systems by starting Internet Explorer browser with the URL in previous step and choose ‘Client Installation’. On the appearing web page, choose the link ‘Windows Robot, Hub, Distribution Server, Alarm Server’ to install the Nimsoft Infrastructure.

- Updating the Nimsoft robot: On Windows systems Simply drop the robot_update being logged in to the upgraded server or another HUB with updated archive. OR: Identify other systems which contain Nimsoft Robot (Control Panel->Add/Remove programs) and upgrade these systems by starting Internet Explorer browser with the URL in previous step and choose ‘Client Installation’. On the appearing web page, choose the link ‘Windows Robot’ to install the Nimsoft Robot. On UNIX systems: Simply drop the robot_update being logged in to the upgraded server or another HUB with updated archive. Note: Do not drop the robot update on a HUB icon in the Infrastructure Manager tree! (Doing this will make part of the distribution fail. This kind of update will include the robot where the HUB is running and restarting the HUB robot. Other robots belonging to this HUB will failover to secondary HUB creating problems for the distribution and end up with some of the robots not being updated.) You can either drop the robot_update on each robot separately or build group(s) of non-HUB robots to mass-distribute the Robot. HUB-robots should be updated individually to the robot and not on the HUB icon.

Check the appropriate check-box for Nimsoft Dashboard Viewer if desired during upgrade. See the Nimsoft Installation Guide for further details.


Verification of successful installation/upgrade The installation procedure does not leave an “all is installed correctly” mark, so one has to follow the output from the installation process closely in order to detect failure(s). One indication that the installation was successful is that one can read the text “Nimsoft Server 5.12” in the main browser window after double-clicking on the “Nimsoft Server” icon on the desktop. Another indication is that all your probes/components in the main windows of the Nimsoft Manager have the correct versions. Check the installed user interfaces (Help->About) for the following versions: User Interfaces Enterprise Console 3.46.1 Nimsoft Manager 3.86.1 Service Level Manager 4.74 Alarm Subconsole 2.72 Dashboard Viewer 1.30 Webpublish 2.95 LogViewer 1.1.3 Dr. Nimbus 1.5.3

Backend components distsrv 5.14 hdb 5.42 hub 5.60 spooler 5.42 install_unix 4.60 aix_5 (4. 60) hpux_11 (4. 60) linux_22 (4. 60) linux_23 (4. 60) solaris_10_i386 (4. 60) solaris_8_sparc (4. 60) tru64 (4. 60) aix_5_64 (4. 60) hpux_11_64 (4. 60) hpux_11_ia64 (4. 60) solaris_8_sparcv9 (4. 60) solaris_10_amd64 (4. 60) linux_23_64 (4. 60) linux_23_ppc64 (4. 60) nas 3.63

robot 2.91 &

5.42 controller 5.42 as400 robot 4.01 group_server (MSSQL only, not needed for new installations) 2.65 nis_server 1.38


httpd 1.45 nimldr 3.54 dashboard_server (MSSQL only, not needed for new installations) 1.70 variable_server (MSSQL only, not needed for new installations) 3.40 data_engine 7.65 report_engine (MSSQL only, not needed for new installations) 7.81 sla_engine 3.49 audit 1.17 qos_engine 2.61 relationship_services 1.53 fault_correlation_engine 1.53

Discovery components NIS Manager 2.2.0 cisco_monitor 2.92 interface_traffic 4.94 net_connect 2.53 ace (windows legacy) ace (new multiplatform version)

1.37 2.18

assetmgmt 1.23 discovery_agent 2.39 discovery_server 2.79 Rsp 2.68

Redist VS-2008 REDIST x86 1.0 VS-2008 REDIST x64 1.0 Checking the database upgrade The best way to check that the database update is successful is to use a SQL tool (e.g. SLM Manager->Tools->SQL Query) and execute the following statement: Select * from S_SLM_VERSION

If this query returns "4.67", the installation has completed successfully.

Upgrade of indexing for sample data tables The data_engine version 7.53 (NMS 4.3x) changed the set of indexes which it creates on the sample data tables RN_QOS_DATA_xxxx. However, this does not apply to existing RN_QOS_DATA-tables and they will continue with the old index set.


Please review section Increased database storage requirements with regards to increased size of sample data tables due to upgrade from NMS 4.2. In most case, it is advisable to also change the indexing for these tables. However, since it is not mandatory and it can take a long time to execute, this task is neither executed by the NMS Installer nor the data_engine. The NMS Installer will detect the missing indexes and point to this section in the Nimsoft Server Upgrade Guide. The following procedure describes how to migrate from old indexing to new indexing for the sample data tables.

1. Stop the data_engine and any other activity against the NIS database (by stopping the hub and robots working against it). This step is required to the speed up the migration of indexes

2. Important: Take a backup of database before executing the steps mentioned below.

3. Using SQL Management Studio or similar, access the NIS database and execute the following steps:

a. Check which RN_QOS_DATA-tables require re-indexing. This can be done by expanding the RN_QOS_DATA_xxxx tables to verify the type of indexing they are currently using.

• If they have one clustered index with the same name as the table, then they are using the old indexing.

• If they have three indexes (_Idx0, _Idx1 and _IdxSDP all prefixed by table name), then they are using new indexing.

b. For all tables found to be using old indexing, execute the following step:

exec spn_utl_Reindex_SampledataTables @TableNamePattern='RN_QOS_DATA_%'

Note: Modify the parameter @TableNamePattern to match the set of tables which should be re-indexed. You can either execute the re-indexing in one step as above or execute it multiple times where each iteration covers one or more RN-tables as in example below:

exec spn_utl_Reindex_SampledataTable @TableName='RN_QOS_DATA_0001'

4. Start any components stopped in step 1.


Failure Nimsoft stands ready to help its customers manage complex networked systems with an advanced performance and service-level management solution built on a flexible architecture. We will therefore be happy to receive your input – problems or any other kind of expression – through any of the following channels: Phone (Scandinavia): +47 99609387 Phone (Europe): +44(0)1932 577766 Phone (USA): +1 650 570 5401 (press 3) Fax: +47 22627161 Email: [email protected]


Chapter 2: Main Feature changes

General functionality

New operating system platforms supported • New operating systems supported for the Nimsoft server 5.x:

• Linux RedHat versions 4 and 5

• Linux SUSE (SLES) versions 10 and 11

• Solaris version 10

New database platforms support for the NIS database • New database platforms supported for the backend NIS database:

• Oracle 11.x

• MYSQL 5.1/5.5

Windows consoles

Infrastructure Manager • Audit trail for all functions in security menu is added. (New

functionality requires minimum version 5.31 of the HUB.)

Probes This section describes new probes introduced with Nimsoft Server 5.0/5.1x and main feature changes for existing core probes.

ACE • ACE (Automatic Configuration Engine) is now delivered in

two versions (which cannot run simultaneously): § Windows legacy, compatible with old ACE

schema. (This version will not support new web based configurations.)

§ Multiplatform, new schema with support for Unified Service Manager (USM) web based configurations from Unified Monitoring Portal (UMP) 2.1. (This version of ACE will not support previous configurations using NIS Manager.)


Component changes and fixed problems from 4.3 to 5.12

This section contains a list of fixed problems and product changes from Nimsoft Server 4.3 to 5.12. Note that the section Main Feature changes describe the new main features of NMS 5.12.

Enterprise Console (from 3.43.1) • All graphs disappeared in multi-line graph object if one has no valid data. This is

fixed. • Making button invisible when no QoS report exist for a dynamic dashboard has

been replaced by a message. • Disabled NIS dependent features when no NIS connection • Removed SDP version check

Infrastructure Manager (from 3.83.1) • Added ‘Check Server Common Name’ option to the DMZ Setup Wizard. • Probe GUI’s will be launched from users temporary folder to avoid file access

problems for WIN7 and WIN2008 R2. • Preventing excessive traffic to HUB when browsing fast through HUBs or robots. • Disabled NIS dependant features when no NIS connection • Removed SDP version check • Extended multi thread logic when browsing fast between robots or hubs to

avoid unnecessary hub requests

Service Level Manager (from 4.71) • N/A

Alarm Subconsole (from 2.65.1) • N/A

Dashboard Viewer (from 1.30) • N/A

Webpublish (from 2.85) • N/A

LogViewer (from 1.1.3) • N/A


Dr. Nimsoft (from 1.5.3) • N/A

distsrv (from 5.00) • Threading stability fix for Linux platforms. • Fixed intermittent problem on Linux platforms introduced in beta version 5.12

where distsrv could stop responding after some time. • Increased limitations for license size. • Changed field type of the server field in the forwarding profile dialog to allow

unlisted values. • 'attempt_number' cleanup done to avoid looping and added specific error

message added for situations where the distribution result cannot be obtained. • Fixed package sort by date in configuration tool. • Fixed dependency checking on forwarded distribution. • Added a small delay between processing forwarding profiles. • Separated license read/write locks. • Added option to enable/disable forwarding. • Configuration tool fix for package forwarding; improved parsing logic for

package list. • Added support for extended NIS data model in alarms. • Fixed achive list 'since' parameter problem on 64-bit Solaris. • Threading implemented for job_status and job_list callback functions. • Improved error handling for session requests. • Version recognition fix. • Added 'file' argument to 'archive_put_start' to enable more consitent archive

management. • Fixed problem with forwarding interfering with the last change parameters from

the 'get_info' callback. • Session request reconnect problem during distribution fixed.

hub (from 5.12) • Fixed potential segfault on Linux platforms in thread and session handling. • Override alarm text with "n/a" when there is a blank error text from the system. • Fix return code at error situations when testing connectivity with ldap server. • Fix return code when testing if there is data on the ssl socket if that socket does

not exist. • Fix problem with client false certificate expiration alarms on the server side

(should only be checked on the client side). • Fix for connecting to spooler on passive robot when proxy mode is set. • Fix for tunnel server binding to localhost instead of all interfaces. • Fixed segfault issue in connection with tunnels hanging which would trigger a

HUB restart. • Fixed segfault issues by shutdown of HUB occurring on some Linux systems. • Fixed problem with expired SID on the way through a tunnel not getting that

status code back to the probe so it can renew the SID. • Improved SSL shutdown in tunnel sessions. • Added extra locking to internal security information to avoid crashes due to

thread issues.


• Upgraded OpenSSL library. • Changed functionality for HUB SSL mode: Hub will not spread “SSL only” mode

to other HUBs in the domain. Each HUB needs to be set individually to “SSL only” mode. Server documentation is not updated with this change and will be updated for next release.

• Added audit flag. Audit settings will now be propagated to the robots when they connect to the hub. (Requires Robot version 5.21.)

• Added hubpost_bulk callback to internal spooler to allow robots with high latency to send several messages in one go.

• Added auditing on login, change password and probe security changes • Fixed problem writing to queue files that grow over 2GB on 32bit systems. • Added clone prevention mode that will send alarm and/or prevent controllers

with same name and different IP to register. (Requires Robot version 5.21.) • Modified splAddSource to check against local IP list (code duplicated from

spooler). • Added support for extended NIS data model in alarms. • Fixed ldap proxy code when going through tunnels. • Added option to specify what size to alarm on for queue sizes through GUI. It

has previously only been editable through raw configure. • Hub checks for valid SID before sending a request through a Tunnel. • Tunnel Access List supports a new field, Source, to control who has access. • Added user_tag_1 and user_tag_2 to header of alarms sent on behalf of a robot. • Added audit messages to edit user and delete probe callbacks. • Avoid brute-force password guessing by blocking a user or ip address for a time

(5 minutes default) after multiple consecutive login failures (5 is default). • Fixed problem where robot with autoremove=yes would not send inactive

alarm.

robot/controller/spooler/hdb (from 5.12) • Unix/Linux pidfile problem fixed. Robot would not start if pidfile was empty. • Variable expansion fix. • Fixed log position problem on probe_tail_logfile_session. • Added functionality to enable NIS cache maintenance. • Added 'interfaces' option to the 'get_info' callback to include a list of known

network interfaces. • proxy mode fix: if used with first probe port, the internal controller port gets

assigned the first probe port. Note that it is not normally recommended to use these options together as all communication should go throught the proxy port.

• Spooler storm protection improvement: saves subject, probe, severity and suppression key of last message discarded message in a message storm.

• Added spooler option to set alarm level for queueing problem alarms. • Spooler error situation on Linux due to ip misconfiguration handled. • Added support for using proxy mode in passive robots. This requires hub version

5.53 or newer. • Changed potentially misleading alarm texts for spooling problem situations.

Made default fail window configurable and changed default from 10 to 15 seconds.

• Fix for distribution requests over tunnel. • More detailed error logging in spooler.


• Bulk transfer problem in spooler with not emptying buffer on multiple bulks fixed.

• Input fields changed to allow spaces in user tags in the controller configuration tool.

• Increased buffer for nimGetIpList to 512 bytes in nametoip and iptoname callback routines.

• Upgraded OpenSSL library. • Fixed problem with license expiration for probe on server. • Implemented bulk message transfer to hub in robot spooler. • Accept audit setting from hub. • Force hub update if maintenance period is changed. • Implemented "iptoname" callback. • Modified spooler to check against local IP list for incoming messages to add

correct source. • Sending of System Uptime QoS message is not attempted until the spooler is

confirmed to be up. • Prepare robot to be able to get audit setting from hub. • Handle duplicate rejection return on robot registration with hub by appending IP

to name and rejecting the license issued by the hub. (Requires HUB version 5.31.)

• Added 'post_raw' callback to spooler command interface. • 'file_put_start' and 'file_put_next' commands will write to a temporary file if the

file already exists. The file is renamed to the destination name on 'file_put_end'. • Added ability to alarm on post-install error situations. • Added support for scheduling maintenance mode. • Added validation of specified robotip against known local interfaces, with alarm

and reversion to last known good ip on error. Add 'local_ip_validation = no' if you need to turn off this functionality.

• Added alarm on missing or disabled spooler. • Added alarm on communiaction error between controller and spooler. • In log and configuration tool, renamed 'maintenance mode' to 'suspend mode'. • Spooler locking problem on message expiration fixed. The problem can be

avoided on previous versions of the spooler by adding 'expire_size_severity = 0' to the spooler section of the spooler configuration file.

• Daylight Savings Time change recalculation fix to avoid disruptive recalculations on slow machines.

install_unix (from 4.42) • Latest versions of the inside components.

nas (from 3.43) • Improved postMessage retry mechanisms for AO (EMAIL,SMS,repost). • Improved handling of duplicate message-ids (constraint violations) in incoming

alarms. • Fixed problem with invisible alarms becoming visible during replication.


• Improved the replication engine to fix intermittent problems causing NAS to be out of sync.

• Fixed memory leak regarding I18N support on incoming alarms. • Fixed problem with replicated NAS'es coming out-of-sync after restarts and

heavy message throughput. • Fixed problem with 'nimts' column being '0' in NiS-

BRIDGE:NAS_TRANSACTION_SUMMARY table. • Fixed logging issue with NAS running without connectivity to distsrv. • Added support for internationalized/tokenized alarms. • Added support for a Oracle NiS database. • Added support for NiS database MYSQL and Oracle. • Allow Boolean variables for 'escalated' and 'visible' elements for language

consistency (i.e. pre-processor, alarm.set()). • Added 'level' and 'severity' to list of adjustable pre-processing alarm fields. • Fixed intermittent problem with nas restart on certain types of alarms. • Fixed a memory-leak when using custom fields in pre-processing scripts. • Auto-configured NAS to activate internationalization support as default on fresh

installs. • Fix for Oracle database used as NIS database

as400 robot (from 4.01) • Version 4.01 of the robot is following NMS 5.12.

group_server (from 2.62) • N/A

httpd (from 1.41) • Return error code if unable to send file. • Removed legacy webservice and legacy mobile web services.

nimldr (from 3.42) • Included support for AIX7 • Included support for GLIBC versions 2.13-2.19. • Fixed problem where autoremove setting was not honored during automatic

installation. • Changed default for unregistering robot during shutdown to "no" so that express

installations can chose to either enable it (with the -a option) or leave it unset. • Add "admin" probe permissions for NAS during installation. • Fixes for recognizing Linux GNU libc (GLIBC) version 2.10 to 2.12.

dashboard_server (from 1.70) • N/A


variable_server (from 3.40) • N/A

data_engine (from 7.56) • If data engine encounters a bad savefile, it will send a critical alarm and continue

processing instead of coming to a halt. • UpdateStatistics on Microsoft SQLServer is now run periodically to ensure

information to MSSQL Query Optimizer is correct. • Fixed issue with update_last_value=1 parameter causing data_engine to restart

at random interval. • mysql: compress data no longer fails for asynchronous qos • data_engine GUI: Fixed list of QOS objects display + hasmax column.

report_engine (from 7.81) • N/A

sla_engine (from 3.03) • Updated sqljdbc driver. • Fixed sla_engine intermittent stopping execution after some random time. • sla_engine stopping executing because of huge RN table. • Added support for MYSQL and Oracle databases.

NIS Manager (from 2.2.0) • N/A.

audit (from 1.11) • Added support for MYSQL and Oracle databases. • Fixed problem with handling strings with special characters.

qos_engine (from 2.06) • Added support for MYSQL and Oracle databases.

cisco_monitor (from 2.80) • Added fix to properly create host profile during drag-n-drop of IP/ hostname

from WordPad. • Added support for web based Service oriented Configuration (SoC). • Fixed the qos target in case of memory_usage_perc checkpoint • Added support for high and low threshold alarms in checkpoints. • Added default configuration template. • Added bulk configuration template.


interface_traffic (from 4.70) • Increased SNMPWalk limitation from 300 to 3000 entries (added key

/setup/max_oids in config file). • Added support for web based Service oriented Configuration (SoC). • Added support for internationalization. • Added new feature for handling of extreme values in Traffic and Processed

Packets section. Added fix to make "does not exist in the MIB" alarm message configurable. Added support to specify the traffic limit required to trigger "No Traffic" alarm.

• Added support to monitor (Alarm and QoS) Error packets and discarded packets as percentage (%) of total processed packets.

• Added fix to allow one threshold value (both thresholds not mandatory now) in Traffic section.

• Added support for a callback to get total number of active and inactive interfaces.

• Added support for all known interface operational status (total 7 as per IF-MIB). • Added support for SNMP V2 and V3 credential details to perform bulk discovery. • Added option in bulk configuration window to remap interfaces after an index

shift. • Added code to allow decimal numbers in threshold fields of 'Traffic' tab

net_connect (from 2.40) • Changed thread pooling implementation to schedule all the profiles from

queue. • Added support for web based Service oriented Configuration (SoC). • Added support for internationalization • Added support for reading alarm tokens from CFG • Added option to send Latency and Jitter with Packet Loss monitoring, when

delay between packet is set. • Added option to continue checking services even if Monitor ICMP Connectivity

fails.

ace (from 1.35) • ACE (Automatic Configuration Engine) is now delivered in two versions (which

cannot run simultaneously): » Windows legacy, compatible with old ACE schema. (This version will not

support new web based configurations.) » Multiplatform, new schema with support for web based configurations.

(This version will not support previous configurations using NIS Manager.)

• Changed XML parser due to a bug in the default JDK parser that sometimes resulted in corrupt XML.

• Fixed a bug for SOC where local monitors where treated as remote due to wrong parsing of remote attribute from <CfgData>.

• added probe distribution for SOC if probe is not already present on robot


discovery_agent (from 2.14) • _stop call will now restart discovery_agent and not only stop the probe. • Computer name is now same as discovered with ssh or wmi, whenever ssh or

wmi is discovered. • snmp version 2 now discovers correctly. • Verifying snmp errors. • Fixed wmi not being discovered because of inherent permissions. • Added support for MYSQL and Oracle databases. • Fixed ping discovery to discover more devices. • Fixed issues with discovery process stopping in poorly responsive environments. • Fixed issues with internal threading, making discovery incomplete.

discovery_server (from 2.13) • Not removing custom scripts when upgrading probe. • Added support for MYSQL and Oracle databases. • Fixed issues with multiple discovery_agents, making discovery incomplete or

stop. • Fixed issue with database connection problems, making discovery stop.

rsp (from 2.50) • Optimized the read buffers for event log to improve performance. • Optimized code to improve performance while reading large amount of WMI

data. • Fixed possible probe restart situation in case of NTevent profile deletion. • Support for reading alarm tokens from cfg. • Fixed CPU discovery LUA script. • Added support for web based Service oriented Configuration (SoC).


Chapter 3: Known Issues UMP may need some handling after an upgrade to NMS 5.12

If you have UMP installed, you might need to restart the wasp and dashboard_engine probes to be able to log into UMP after an upgrade to NMS 5.12.

SDP is not supported with NMS 5.1x or later Using SDP, you will need to upgrade to UMP before installing NMS 5.1x.

Deploying changes in a package back into local archive Having installed NMS 5.1x on Linux or Solaris server, this functionality will not work until you redeploy distsrv.

Occasionally some probes do not start after installation We have occasionally experienced situations where some of the probes do not start after the installation of NMS server. This is caused by lack of system resources available. If you experience this problem, you can do as described below: Edit the registry key EditHKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\Session Manager\SubSystems\Windows

The value marked red is initially set to 512. You can solve the problem by increasing this value to 1024. See also the following article for further information http://support.microsoft.com/kb/184802


Microsoft Vista, Windows 7 and Windows 2008 issues - Problems when launching dashboards from the Nimsoft Server main window. The problem can

be solved by adding the site as a trusted site (Internet Options > Trusted sites).

- Write privileges are required for writing to the Nimsoft Program Files folder. If logged on as a user without administrator privileges after the installation, you must manually set these write privileges.

AIX computers not found by discovery, using SNMP - Certain types of AIX computers might not be found when running discovery, using

SNMP. The reason is that the format in the computer description field cannot be read (AIX sends binary data as description over the SNMP API that we use).

Discovery Agent - The NetBIOS scan performed by the discovery_agent will not work on Windows 7, Vista

and Windows Server 2008. The reason is that the NetBIOS API is not supported on these platforms.

Uninstalling Nimsoft, using Add/Remove Programs in the Control Panel - Uninstalling Nimsoft from the Add/Remove Programs control panel applet may

sometimes fail. The problem is that the path to Ctor.dll does not have quotes, even though there is a space in the path. To solve this, you should find the path to Ctor.dll in the registry and add quotes as shown below: "C:\PROGRA~1\COMMON~1\InstallShield\engine\6\Intel 32\Ctor.dll” Then attempt to uninstall Nimsoft again.


Probes not activated after Nimsoft Server installation - During Server installation several components are distributed and configured. On slow systems

we have occasionally seen situations where some of the probes were not started during the installation. This can be detected in Nimsoft Manager, and can be fixed simply by activating the probe.

Activating discovery and configuration of existing interface_traffic probe on the server

- The Nimsoft discovery function will automatically turn on encryption of community strings in the probe configuration file on the discovery computer. Prior to activating the discovery function, please enable encryption on the interface traffic probe before enabling the discovery function. Failing to enable encryption, will cause existing configurations to stop working caused by invalid community strings. Interface_traffic probes on other robots are not affected.

-DOCUMENT END-

nimsoft server 512 upgrade guide · 2014. 8. 5. · installation of nimsoft infrastructure is part...

Documents