AppManager for Cisco Unified Communications Management (CiscoUCM) allows you to monitor resources for Cisco Unified Communications servers such as the Cisco Universal Presence Server (CUPS) and the Unified Call Center Express (UCCX).
This hotfix resolves specific previous issues. This document outlines why you should install this hotfix.
This release improves usability and resolves previous issues. We thank you for your time and valuable input. We hope you continue to help us ensure that our products meet all your needs. You can post feedback in the AppManager forum on NetIQ Communities, our online community that also includes product information, blogs, and links to helpful resources.
The documentation for this product is available on the NetIQ Web site in HTML and PDF formats on a page that does not require you to log in. If you have suggestions for documentation improvements, click comment on this topic at the bottom of any page in the HTML version of the documentation posted at the AppManager Modules page. To download this product, see the AppManager Module Upgrades & Trials Web site.
This release of AppManager for Cisco Unified Communications Management provides the following enhancements:
Support for Cisco Unified Communications Manager 12.5: This release of AppManager for Cisco Unified Communications Management provides a support for Cisco Unified Communications (CUCM) 12.5.
Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Cisco Unified Communications Management (CiscoUCM) provides support for TLS 1.2.
This release of AppManager for Cisco Unified Communications Management resolves the following issue:
CiscoUCM discovery fails: Due to invalid host FQDN usage, CiscoUCM discovery fails. With this release, this issue is resolved and CiscoUCM discovery is restored in Cisco Communication Manager 12.5. (ENG349526)
CiscoUCM_HealthCheck does not generate event for Reason code "No such service": With this release, a new parameter option named “Skip event notification for uninstalled services” is introduced in CiscoUCM_HealthCheck Knowledge Script. To generate uninstalled services events, unselect this new option. (ENG350171)
For the most recently updated list of supported application versions, see the AppManager Supported Products page. Unless noted otherwise, this module supports all updates, hotfixes, and service packs for the releases listed below.
AppManager for Cisco Unified Communications Management has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the computers you want to monitor (agents), and on all console computers AppManager Suite Hotfixes |
8.0.3, 8.2, 9.1, or higher One of the following AppManager agents are required:
For more information about hotfixes, see the AppManager Suite Hotfixes page. |
|
Microsoft Windows operating system on the agent computers |
One of the following:
|
|
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer and on all console computers |
7.6.170.0 or higher For more information, see the AppManager Upgrades & Trials page. |
|
Cisco Unified Communications (CUCM) installed on the computers you want to monitor |
12.5, 10.5, 10.0, 9.1, 9.0, 8.6, 8.5, 8.0, 7.1(2), 7.0, 6.1, 6.0, 5.1, or 5.0 |
|
Cisco Unified Presence Server (CUPS) |
10.5, 10.0 |
|
Cisco Unified Contact Center Express (UCCX) |
10.5,10.0 |
|
Cisco Unified Contact Center Express (UCCX) |
10.5, 10.0 |
|
Cisco Unified Connection (CUC) |
10.5, 10.0 |
For more information about system requirements, see the CiscoUCM Management Guide, included in the download package.
AppManager for Cisco Unified Communications Management includes a managed object, qNQCiscoUCM.dll, and Knowledge Scripts to discover and monitor Unified Communications Manager resources. The download package also includes this release notes file, a management guide, Help for Knowledge Scripts, and several files that are used during installation and/or Control Center deployment:
AM70-CiscoUCM-8.1.99.0.msi, the module installer.
AM70-CiscoUCM-8.1.99.0.ini, a configuration file used with the AppManager setup program.
AM70-CiscoUCM-8.1.99.0.xml, a configuration file used for deploying the module with Control Center. This is the file you check into the Control Center Web Depot.
AM70-CiscoUCM-8.1.99.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckCiscoUCM.exe, the pre-installation check used with the AppManager setup program.
When you download the module, these files are copied by default to the local folder on the download computer. Consider copying these files to the \windows_installation\setup\Setup Files folder on the same distribution computer on which you saved your main AppManager software and documentation. By doing so, you maintain all AppManager software in one location that is easily accessible when you want to add more repositories, management servers, or agents.
Run the module installer to install the module components in the following locations:
On all proxy agent computers to install the agent components.
On all console computers to install the Help and console extensions.
Run the module installer only once on each of these computers.
You must also install the Knowledge Scripts. You can install the Knowledge Scripts into local or remote QDBs. When installing to each QDB, select the option to install Knowledge Scripts, and then specify the SQL Server name of the server hosting the QDB, as well as the case-sensitive QDB name.
Important This release provides SQL stored procedures. To ensure module functionality, run the module installer for each QDB attached to Control Center.
You need to install Knowledge Scripts only once per QDB. The module installer now installs Knowledge Scripts for each module directly into the QDB instead of to the \AppManager\qdb\kp folder as in previous releases.
For more information about installing this module, see the AppManager for Cisco Unified Communications Management Guide, included in the download package.
NetIQ Corporation strives to ensure our products provide quality solutions for your enterprise software needs. The following issues are currently being researched. If you need further assistance with any issue, please contact Technical Support.
The event message after discovery fails lacks sufficient information about Security Manager credentials.If you type an incorrect name or password in Security Manager and run Discovery_CiscoUCM, discovery fails. However, the event message does not mention that incorrect credentials may cause discovery to fail. Similarly, discovery fails if you do not select Extended application support in Security Manager, but the event message does not mention that leaving this option unselected in Security Manager may cause discovery to fail. (ENG339433, ENG339434)
The CiscoUCM_SystemUpTime Knowledge Script might return an incorrect value if the monitored system has been running for over a year.The Cisco Unified Communications Management Total CPU Time performance counter cannot monitor a system that has been running for longer than 500 days, which causes the incorrect value to occur in this module. As a workaround, you can measure uptime for a system that has been running for over 500 days by using the NetworkDevice_Device_Uptime Knowledge Script. For more information about the Network Devices module, see the AppManager for Network Devices Management Guide AppManager Documentation page. (ENG339435)
This release of CiscoUCM includes enhancements added in previous releases.
The following issues are resolved and imported from CiscoCM to CiscoUCM and are fixed in CiscoUCM:
Discovery does not resolve servers when a host file nickname (a non-domain name as second entry) is used. When using the hosts file on Microsoft Windows to include alternate names for specific IP addresses, if the host file entry contains multiple names and the second entry was a non-domain name, discovery does not resolve the matching server instance correctly and it creates two copies of the server in the TreeView pane. With this release, correction of the host name lookup allows creation of only one server regardless of the number of names in the host file. (ENG337174)
Improvements to CiscoUCM Scalability. This release provides a performance enhancement to automatically adjust the default for the configurable number of instances of a counter object within a single AXL session according to the size of the monitored system. (ENG343751)
Remove truncation from CiscoUCM AXL communication logs. The AXL communication logs were truncated, limiting debugging for large systems. These logs no longer truncate. (ENG338196)
The following issue was previously released in a PF and is now releasing in this hotfix:
In the Discovery_CiscoUCM Knowledge Script, only the primary node of cluster is discovered. When Cisco returns the server names for the cluster query, the cluster query included a cluster identification prefix, but the name parsing did not take the prefix into account and did not correctly associate the members of the cluster. With this release, the members of a cluster are correctly identified when the alternate name format is returned. ENG342103)
The following issue is new to this hotfix:
There is web page type differentiation for known types and overrides for unknown types. When the CiscoUCM WebPageCheck Knowledge Script is targeting a non-CUCM server, the Knowledge Script always attempts to monitor the web page URLs as if the server was a call manager. With this release, the web page script adapts to the server and selects the URLs appropriate to the server type. In addition, an override is provided to allow customized URL monitoring. (ENG343091)
Support for Windows 2016. With this release, CiscoUCM supports Windows Server 2016 and Windows 8.1. The displayed windows versions in the prerequisite report are updated to display the correct Windows release versions. (ENG344139).
HealthCheck Knowledge Script cannot handle more than 64 services. With this release, the HealthCheck Knowledge Script added support for monitoring more than 64 Cisco services at once. (ENG344490)
This release provides the following enhancements:
GeneralCounter does not display the names of monitored counters. This release provides a new event in the CiscoUCM_GeneralCounter Knowledge Script that lists the names of the performance counters matching the regular expression filter. (ENG340194)
Added CiscoUCM Scalability Improvements. This release provides a performance enhancement to allow the retrieval of a configurable number of instances of a counter object within a single AXL session, as specified using a registry entry. For additional information about adding the registry entry, see Installing AppManager for CiscoUCM in the AppManager for CiscoUCM Management Guide. (ENG340407)
This release of AppManager for Cisco Unified Communications Management resolves the following issues:
GeneralCounter unexpectedly stops the NetIQmc service, if running on a system with a large string of objects. With this release, the CiscoUCM_GeneralCounter Knowledge Script increased the maximum size of its target object list, so that more objects may be monitored by a single job. (ENG339792)
Cluster tag not generated. This release resolves an issue in which the root cluster object in the treeview did not include the CM-Cluster tag, when Discovery_CiscoUCM is run on a cluster where one or more of the Call Manager services are disabled. With this release, the CM-Cluster tag is included in the treeview, even when some of the Call Manager services are disabled.(ENG339752)
60-second AXL throttle timer back-off is activating for non-throttling errors. This release resolves an issue in which non-throttling errors cause the timer backoff to engage, which delays all CiscoUCM messaging. With this release, when a non-throttling error occurs, an event is raised that the errors occurred while messaging to the device continues without delay. (ENG340490)
This release of AppManager for Cisco Unified Communications Management resolves the following issues:
Support for Discovery of Cisco Unity Connection.This release of AppManager for Cisco Unified Communications Management allows you to monitor the Cisco Unified Connection (CUC) servers version 10.0 and 10.5.
Support for Regular Expression in GeneralCounter Knowledge Script. This release of AppManager for Cisco Unified Communications Management allows the use of regular expressions to specify instance names in the GeneralCounter Knowledge Script.
This release of AppManager for Cisco Unified Communications Management adds the following Knowledge Scripts:
UCCX_CUIC_Database_Unavailable: Monitors for critical database error condition on the UCCX server.
UCCX_CUIC_DB_Replication_Failed: Monitors for database replication failure condition on the UCCX server.
UCCX_CUIC_Live_Data_Feeds_Stopped: Monitors for live data feeds have stopped on the UCCX server.
UCCX_CUIC_Report_Execution_Failed: Monitors for a condition where the reporting server is unable to run a report on the UCCX server.
UCCX_CUIC_Service_Unavailable: Monitors if the Cisco Unified Intelligence Center service is unavailable on the UCCX server.
UCCX_CUIC_Unrecoverable_Error: Monitors for internal errors within the reporting server of UCCX which may prevent it from functioning correctly.
Recommended Knowledge Script Groups: Adds essential monitoring for your Cisco Unified Contact Center Express (UCCX) environment.
This release of AppManager for Cisco Unified Communications Management also resolves the following issues:
Improved handling of AXL throttling errors for Scalability. When Cisco servers, which support SOAP/AXL communications, receive more than 50 requests/second, the servers may respond with an “AXL throttling” exception. This may occur on systems when monitoring a large number of counter entries. The retry method for SOAP/AXL errors was modified to add an additional delay when AXL throttling is detected which slows down the overall request rate to allow larger systems to be monitored without error. (ENG337767)
Allow use of Security Manager entries without a cluster type tag. A type-specific tag was added to the cluster name to help identify the server types in the cluster, for example -CM, -UCCX, -CUPS, -CUC. This type-specific tag was used to look up security manager keys, which may be a problem in cases where the cluster type was not known prior to discovery. The lookup has been changed to use only the cluster name, not the type-specific tag. (ENG337891)
Discover servers when a host file nickname (a non-domain name as second entry) is used. Use the hosts file on Microsoft Windows to include alternate names for specific IP addresses. If a host file entry contained multiple names and the second entry was a non-domain name, discovery did not resolve the matching server instance correctly and it created two copies of the server in the TreeView pane. The host name lookup was corrected so only one server is created regardless of the number of names in the host file. (ENG337174)
Remove truncation from CiscoUCM AXL communication logs. The AXL communication logs were truncated, limiting debugging for large systems. These logs are no longer truncated. (ENG338196)
GeneralCounter datastreams with [ ] in counter names were truncated. Counters containing square brackets in the name were not being correctly displayed as datastreams. These counters now display correctly. (ENG337905)
WebPageCheck did not return events or datastreams. The WebPageCheck Knowledge Script did not return events or datastreams regardless of the options selected. This has been corrected. (ENG339535)
AppManager provided the following Knowledge Scripts for monitoring resources for Cisco Unified Communications servers such as the Cisco Universal Presence Server (CUPS).
CiscoUCM_CTIManager: Monitors the usage of the Cisco Unified Communications server CTI Manager.
CiscoUCM_CUPS_ActiveCalendarSubscriptions: Monitors the number of calendar subscriptions that are currently active on a Cisco Unified Presence server.
CiscoUCM_CUPS_ActiveIMSession: Monitors the number of active instant message sessions between SIP and XMPP on a Cisco Unified Presence server.
CiscoUCM_ActiveJsmSessions: Monitors the number of client emulation sessions between Presence Engine and Jabber Session Manager for a Cisco Unified Presence server.
CiscoUCM_CUPS_IncomingSIPSubscriptions: Monitors the number of active incoming subscriptions for a Cisco Unified Presence server.
CiscoUCM_CUPS_JsmFailedLogins: Monitors the total number of failed logins for the Jabber Session Manager on a Cisco Unified Presence server.
CiscoUCM_CUPS_JsmMsgsInLastSlice: Monitors the total messages in the last time slice for the Jabber Session Manager on a Cisco Unified Presence server.
CiscoUCM_CUPS_JsmOnlineUsers: Monitors the current number of online users being managed by the Jabber Session Manager component of a Cisco Unified Presence server.
CiscoUCM_CUPS_JsmTotalMessagePackets: Monitors the total message packets through the Jabber Session Manager on a Cisco Unified Presence server.
CiscoUCM_CUPS_OutgoingSIPSubscriptions: Monitors the number of active outgoing SIP subscriptions for a Cisco Unified Presence Server.
CiscoUCM_CUPS_TotalAdhocChatRooms: Monitors the total number of ad hoc text conferencing rooms for a Cisco Unified Presence server.
CiscoUCM_CUPS_TotalPersistentChatRooms: Monitors the total number of persistent text conferencing rooms for a Cisco Unified Presence Server.
CiscoUCM_ExtensionMobility: Monitors activity for the Extension Mobility application.
CiscoUCM_GeneralCounter: Monitors activity for the Performance Monitor counter.
CiscoUCM_HealthCheck: Monitors the operational status of active services on Unified Communications servers.
CiscoUCM_SystemUpTime: Monitors the number of hours the Unified Communications server has been operational since its last reboot.
CiscoUCM_SystemUsage: Monitors CPU, memory, and disk usage for a Unified Communications server.
CiscoUCM_WebPageCheck: Monitors the availability of and round-trip time to the ccmadmin and ccmuser Web pages.
Discovery_CiscoUCM: Discovers configuration and resource information for Cisco Unified Communications servers and Cisco Universal Presence Server (CUPS) resources.
Recommended Knowledge Script Groups: Performs essential monitoring of your Cisco Unified Communications server environment and Cisco Unified Presence Server environment.
The CiscoUCM product and all updates and modifications thereto (“Software”) is distributed with certain third-party software and open source software (as may be defined in the license agreement provided with the Software).
The following third-party and open source software are included with the Software and are licensed for distribution according to the terms described in this document and any use thereof must be in accordance with such terms, solely in conjunction with your internal use of the Software, and - unless explicitly contradicted below - consistent with the terms and conditions set forth in the applicable license agreement for the software. No further licenses are granted.
Xerces. Licensed under the Apache License, Version 2.0 (the “License”); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an “AS IS” BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License.
Boost License.
Boost Software License - Version 1.0 - August 17th, 2003
Permission is hereby granted, free of charge, to any person or organization obtaining a copy of the software and accompanying documentation covered by this license (the “Software”) to use, reproduce, display, distribute, execute, and transmit the Software, and to prepare derivative works of the Software, and to permit third-parties to whom the Software is furnished to do so, all subject to the following:
The copyright notices in the Software and this entire statement, including the above license grant, this restriction and the following disclaimer, must be included in all copies of the Software, in whole or in part, and all derivative works of the Software, unless such copies or derivative works are solely in the form of machine-executable object code generated by a source language processor.
THE SOFTWARE IS PROVIDED “AS IS”, WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, TITLE AND NON-INFRINGEMENT. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR ANYONE DISTRIBUTING THE SOFTWARE BE LIABLE FOR ANY DAMAGES OR OTHER LIABILITY, WHETHER IN CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
Net-SNMP. Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read all the parts. Up until 2001, the project was based at UC Davis, and the first part covers all code written during this time. From 2001 onwards, the project has been based at SourceForge, and Networks Associates Technology, Inc hold the copyright on behalf of the wider Net-SNMP community, covering all derivative work done since then. An additional copyright section has been added as Part 3 below also under a BSD license for the work contributed by Cambridge Broadband Ltd. to the project since 2001. An additional copyright section has been added as Part 4 below also under a BSD license for the work contributed by Sun Microsystems, Inc. to the project since 2003. Code has been contributed to this project by many people over the years it has been in development, and a full list of contributors can be found in the README file under the THANKS section. o ---- Part 1: CMU/UCD copyright notice: (BSD like) ----- Copyright 1989, 1991, 1992 by Carnegie Mellon University Derivative Work - 1996, 1998-2000 Copyright 1996, 1998-2000 The Regents of the University of California All Rights Reserved Permission to use, copy, modify and distribute this software and its documentation for any purpose and without fee is hereby granted, provided that the above copyright notice appears in all copies and that both that copyright notice and this permission notice appear in supporting documentation, and that the name of CMU and The Regents of the University of California not be used in advertising or publicity pertaining to distribution of the software without specific written permission. CMU AND THE REGENTS OF THE UNIVERSITY OF CALIFORNIA DISCLAIM ALL WARRANTIES WITH REGARD TO THIS SOFTWARE, INCLUDING ALL IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS. IN NO EVENT SHALL CMU OR THE REGENTS OF THE UNIVERSITY OF CALIFORNIA BE LIABLE FOR ANY SPECIAL, INDIRECT OR CONSEQUENTIAL DAMAGES OR ANY DAMAGES WHATSOEVER RESULTING FROM THE LOSS OF USE, DATA OR PROFITS, WHETHER IN AN ACTION OF CONTRACT, NEGLIGENCE OR OTHER TORTIOUS ACTION, ARISING OUT OF OR IN CONNECTION WITH THE USE OR PERFORMANCE OF THIS SOFTWARE. o ---- Part 2: Networks Associates Technology, Inc copyright notice (BSD) ----- Copyright (c) 2001-2003, Networks Associates Technology, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of the Networks Associates Technology, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. o ---- Part 3: Cambridge Broadband Ltd. copyright notice (BSD) ----- Portions of this code are Copyright (c) 2001-2003, Cambridge Broadband Ltd. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o The name of Cambridge Broadband Ltd. may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. o ---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) ----- Copyright (c) 2003 Sun Microsystems, Inc., 4150 Network Circle, Santa Clara, California 95054, U.S.A. All rights reserved. Use is subject to license terms below. This distribution may include materials developed by third parties. Sun, Sun Microsystems, the Sun logo and Solaris are trademarks or registered trademarks of Sun Microsystems, Inc. in the U.S. and other countries. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of the Sun Microsystems, Inc. nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. o ---- Part 5: Sparta, Inc copyright notice (BSD) ----- Copyright (c) 2003-2006, Sparta, Inc All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of Sparta, Inc nor the names of its contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. o ---- Part 6: Cisco/BUPTNIC copyright notice (BSD) ----- Copyright (c) 2004, Cisco, Inc and Information Network Center of Beijing University of Posts and Telecommunications. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o Neither the name of Cisco, Inc, Beijing University of Posts and Telecommunications, nor the names of their contributors may be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDERS AND CONTRIBUTORS ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDERS OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. o ---- Part 7: Fabasoft R&D Software GmbH & Co KG copyright notice (BSD) ----- Copyright (c) Fabasoft R&D Software GmbH & Co KG, 2003 oss@fabasoft.com Author: Bernhard Penz Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: o Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. o Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. o The name of Fabasoft R&D Software GmbH & Co KG or any of its subsidiaries, brand or product names may not be used to endorse or promote products derived from this software without specific prior written permission. THIS SOFTWARE IS PROVIDED BY THE COPYRIGHT HOLDER ``AS IS'' AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE COPYRIGHT HOLDER BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE.
OpenSSL License. The OpenSSL toolkit stays under a dual license, i.e. both the conditions of the OpenSSL License and the original SSLeay license apply to the toolkit. See below for the actual license texts. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org. Copyright (c) 1998-2006 The OpenSSL Project. All rights reserved. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 1. Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer. 2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 3. All advertising materials mentioning features or use of this software must display the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).” 4. The names “OpenSSL Toolkit” and “OpenSSL Project” must not be used to endorse or promote products derived from this software without prior written permission. For written permission, please contact openssl-core@openssl.org. 5. Products derived from this software may not be called “OpenSSL” nor may “OpenSSL” appear in their names without prior written permission of the OpenSSL Project. 6. Redistributions of any form whatsoever must retain the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL Toolkit (http://www.openssl.org/).” THIS SOFTWARE IS PROVIDED BY THE OPENSSL PROJECT “AS IS” AND ANY EXPRESSED OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE OPENSSL PROJECT OR ITS CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). This product includes software written by Tim Hudson (tjh@cryptsoft.com).
SSLeay License. Copyright (c) 1995-1998 Eric Young (eay@cryptsoft.com). All rights reserved. This package is an SSL implementation written by Eric Young (eay@cryptsoft.com). The implementation was written so as to conform with Netscape's SSL. This library is free for commercial and non-commercial use as long as the following conditions are adhered to. The following conditions apply to all code found in this distribution, be it the RC4, RSA, lhash, DES, etc., code; not just the SSL code. The SSL documentation included with this distribution is covered by the same copyright terms except that the holder is Tim Hudson (tjh@cryptsoft.com). Copyright remains Eric Young's, and as such any Copyright notices in the code are not to be removed. If this package is used in a product, Eric Young should be given attribution as the author of the parts of the library used. This can be in the form of a textual message at program startup or in documentation (online or textual) provided with the package. Redistribution and use in source and binary forms, with or without modification, are permitted provided that the following conditions are met: 0. Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer. 1. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution. 2. All advertising materials mentioning features or use of this software must display the following acknowledgement: “This product includes cryptographic software written by Eric Young (eay@cryptsoft.com). The word 'cryptographic' can be left out if the routines from the library being used are not cryptographic related :-).”3. If you include any Windows specific code (or a derivative thereof) from the apps directory (application code) you must include an acknowledgement: “This product includes software written by Tim Hudson (tjh@cryptsoft.com).” THIS SOFTWARE IS PROVIDED BY ERIC YOUNG “AS IS” AND ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE ARE DISCLAIMED. IN NO EVENT SHALL THE AUTHOR OR CONTRIBUTORS BE LIABLE FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION) HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGE. The license and distribution terms for any publicly available version or derivative of this code cannot be changed. i.e. this code cannot simply be copied and put under another distribution license (including the GNU Public License). Last Modified October 2011
Our goal is to provide documentation that meets your needs. If you have suggestions for improvements, please email Documentation-Feedback@netiq.com. We value your input and look forward to hearing from you.
For detailed contact information, see the Support Contact Information Web site.
For general corporate and product information, see the NetIQ Corporate Web site.
For interactive conversations with your peers and NetIQ experts, become an active member of our community. The NetIQ online community provides product information, useful links to helpful resources, blogs, and social media channels.
For information about NetIQ legal notices, disclaimers, warranties, export and other use restrictions, U.S. Government restricted rights, patent policy, and FIPS compliance, see https://www.netiq.com/company/legal/.
Copyright (C) 2019 NetIQ Corporation. All rights reserved.
For information about NetIQ trademarks, see https://www.netiq.com/company/legal/. All third-party trademarks are the property of their respective owners.