The Alarm Server (nas) stores and administers alarm messages for the UIM Alarm product. The nas package in the Archive contains two probes - nas and alarm_enrichment:
This release is compatible with all versions of UIM going back to 7.6 and forward to 8.5.1 and beyond.
This version of nas is available as part of the CA UIM 8.4 SP2 release.
Multiple Auto-Operators Are No Longer Ignored
This version of nas is available as part of the CA UIM 8.4 SP1 release.
|4.75||Made additional performance improvements for viewing USM alarm information in large-scale environments.||Controlled Release||Sep 2015|
Improved performance while viewing USM alarm information in large-scale environments.
||Controlled Release||Jul 2015|
|4.10||Alarms not stored in replication database when message suppression is turned off||GA||Nov 2012|
|4.00||Added a pre-processing alarm_enrichment probe to substitute data in alarms from CMDB||GA||Jun 2012|
|3.75||Added handler to fix SqliteBusyHandler terminating request||GA||Mar 2012|
|3.74||Fixed: Lua call to note_create fails only on RHEL 6.1||GA||Feb 2012|
|3.73||Fixed I18N issue affecting UMP and Localized GUIs||GA||Jan 2012|
||GA||Oct 31 2011|
|3.71||Defect fixes||GA||Oct 13 2011|
||GA||Jun 24 2011|
|3.63||Fixed defects relating to the GUI, MySQL, and Unix||GA||Jun 23 2011|
|3.62||Defect fixes||GA||Jun 2011|
|3.61||Improved handling of duplicate message-ids (constraint violations) in incoming alarms||GA||Mar 2011|
||GA||Feb 4 2011|
|3.54||Auto-configured NAS to activate I18N support on fresh installs||GA||Feb 3 2011|
|3.53||Defect fixes||GA||Jan 2011|
|3.52||Fixed a problem with Oracle restart||GA||Nov 2010|
|3.44||Added support for NiS databases other than MS-SQL||GA||Jun 2010|
|3.41||Defect fixes||GA||Mar 2010|
|3.40||Added NMS libraries with SSL support||GA||Jan 2010|
|3.31||Various defect fixes||GA||Nov 2009|
|3.28||Fixed a variety of internal defects||GA||Aug 2009|
|3.27||Fixed buffer overrun possibilities||GA||Jul 2009|
|3.26||Defect fixes||GA||May 29 2009|
||GA||May 26 2009|
|3.24||Removed restriction for the 'clear' severity as a candidate for pre-processing.||GA||Mar 2009|
|3.22||Defect fixes||GA||Nov 2008|
|3.16||Added possibility to create custom pre-processing rules and event laundering.||GA||Sep 2008|
|3.15||Improved replication over low-bandwitdh communication lines||GA||Aug 2008|
|3.14||Fixed problem with operator period crossing Sunday night
Fixed name-resolution issues due to lookup aging.
|3.12||Fixed issues with restart and reconnecting to the hub queue||GA||Apr 24 2008|
|3.11||Changed permission requirements||GA||Apr 4 2008|
||GA||Feb 15 2008|
|2.75||Enhancements||GA||Feb 4 2007|
|2.74||Added origin, domain, hub, robot and probe information to network transactions.||GA||Dec 2006|
|2.71||Fixed issue with auto-operator and the ability generate a command after alarm ack||GA||Jan 2006|
|2.68||Fixed problems with import/export and hubnames containing the label "hub"||GA||Mar 31 2005|
||GA||Mar 4 2005|
|2.64||Fixed defects||GA||Jun 2004|
|2.63||Modified the name lookup algorithm to permanently exclude more than 3 consecutive lookup failures||GA||Mar 23 2004|
|2.62||Added support for automatic and manual database reorganization||GA||Jan 2004|
|2.60||Enhanced the auto-operator and filter time-specification properties||GA||Jul 2003|
|2.51||Added support for 'Copy' auto-operator method in UI||GA||Feb 17 2003|
|2.50||Added support for different ip/name lookup methods||GA||Feb 13 2003|
|2.47||Fixed problem with export/import (slave alarm servers)||GA||Nov 2002|
|2.46||Fixed synchronization problems with mirrored alarm servers||GA||Aug 2002|
|2.45||Added suppression time when escalating an alarm. Fixed problems with get_alarms from Alarm Console||GA||Jun 2002|
|2.42||Added support for time variables in auto-operator message decoder||GA||May 2002|
|2.41||Prepared code for Nimsoft 2.51 release||GA||Feb 14 2002|
|2.40||Fixed problems with "assignment"||GA||Feb 2002|
|2.39||Improved handling of corrupted/invalid messages||GA||Jan 17 2002|
|2.38||Fixed problems with name/ip caching mechanism||GA||Jan 15 2002|
|2.37||Use "default" robot-name in alarm messages||GA||Dec 2001|
|2.36||Improved "default" hostname algorithm||GA||Nov 2001|
|2.35||Added transaction-log administration, fixes to auto-operator and transaction-log browsing||GA||Oct 2001|
|2.34||Corrected network trans. logging tokens/data||GA||Jul 2001|
|2.33||Fixed problems related to clearing/ack. Termination/shutdown problems fixed.||GA||Jun 2001|
|2.3||Fixed problems related to Auto-Operator||GA||May 2001|
|2.0||Added Auto-Operator as a thread.||GA||Apr 2001|
This section contains the requirements for the nas probe.
The nas probe is supported on all UIM hub platforms, except for AIX--which is unsupported for nas. This includes 32-bit hub platforms.
This section contains the considerations for the nas probe.
The nas requires a permanent queue on the Hub. If you are upgrading an existing alarm server, the queue will already be defined.
Issue: The NIS Bridge thread will not start after a NAS probe upgrade to 9.00. SQL related errors are showing up in nas/log
Symptom: The new alarms (Alarms happened after NAS probe upgrade) are visible in IM tool (Alarm Window in Infrastructure Manager). However, no new UIM alarms are visible in UMP - USM.
1. Stop alarm_enrichment probe.
2. Stop NAS probe.
3. Open <NAS>/sqlserver-nis-create.sql
4. Find SQL statements described in NIS_BRIDGE_UPDATE_V9 SECTION. You have some SQL statements.
5. Copy (to avoid typo) the first SQL statement.
6. Open SQL database tool (for example, management studio) and select UIM database.
7. Run the first SQL in the tool.
8. Repeat the same step for the next SQL statement.
9. Repeat the same step to cover all the SQL statement(s).
10. Activate NAS probe.
11. Activate alarm_enrichment probe.
Note: Even if NIS Bridge is started, alarm histories occurred during problematic time (NAS_TRANSACTION_LOG) will not be re-populated into SQL database from sqlite (<NAS>\transactionlog.db)