AppManager for Avaya (Heritage-Nortel) Communication Server 1000 7.4.0.4 Release Notes

Date Published: April 2017

AppManager for Avaya (Heritage-Nortel) Communication Server 1000 (Avaya CS1000) helps you gain access to CS1000 data and then analyze and manage that data. The AppManager for CS1000 solution minimizes the cost of maintaining CS1000 services and functions, aids in capacity planning, and can prevent downtime.

Note The AppManager for Avaya CS1000 module displays the previous name, Nortel CS1000, in several places.

This release improves usability and resolves previous issues. Many of these improvements were made in direct response to suggestions from our customers. 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.

1.0 What’s New?

This release of AppManager for Avaya CS1000 provides the following enhancement:

  • Support for Microsoft Windows Server 2016: This release supports Windows Server 2016. For more information, see the System Requirements.

This release of AppManager for Avaya CS1000 resolves the following issues:

  • BMZ objects are not discovered: The BMZ_CallQuality jobs failed because the BMZ objects were not discovered. In this release, the issue is fixed. (ENG344059)

  • NortelCS1000_HealthCheck fails with a SNMP error: The HealthCheck jobs failed because the devices did not respond to SNMP even though the devices were running. In this release, the issue is fixed. (ENG340954 and ENG343712)

  • Few exceptions for NortelCS1000_Alarms are not handled properly: Few exceptions for the NortelCS1000_Alarms jobs were not handled properly. In this release, the issue is fixed. (ENG342636)

To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent computer, and then propagate changes to any running jobs for the Knowledge Scripts that were updated in this release. AppManager 7.x does not automatically update renamed or copied Knowledge Scripts. For more information, see the “Upgrading Knowledge Script Jobs” section in the management guide.

This release of AppManager for Avaya (Heritage-Nortel) Communication Server 1000 replaces all Previous Releases.

2.0 System Requirements

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 Avaya CS1000 has the following system requirements:

Requirement

Details

NetIQ AppManager installed on the AppManager repository (QDB) computers, on all proxy agent computers, and on all console computers

8.0.3, 8.2, 9.1, or later.

One of the following AppManager agents are required:

  • AppManager agent 7.0.4 with hotfix 72616 or later

  • AppManager agent 8.0.3, 8.2, 9.1, or later

The proxy agent computer’s network interface must be on the CS1000 ELAN, not the TLAN.

IMPORTANT:If you use NetIQ Vivinet Diagnostics to diagnose VoIP quality problems in your CS1000 environment, the proxy agent computer must have both ELAN and TLAN connectivity. For more information, see the AppManager for Avaya (Heritage-Nortel) Communication Server 1000 Management Guide.

Microsoft Windows operating system on all proxy agent computers

One of the following:

  • Windows Server 2016

  • Windows Server 2012 R2

  • Windows Server 2012

  • Windows 8 (32-bit and 64-bit)

  • Windows Server 2008 R2

  • Windows Server 2008 (32-bit and 64-bit)

  • Windows 7 (32-bit and 64-bit)

  • Windows Server 2003 R2 (32-bit and 64-bit)

AppManager for Microsoft Windows module installed on repository, agent, and console computers

7.6.170.0 or later. For more information, see the AppManager Module Upgrades & Trials page.

Avaya Communication Server 1000 (CS1000) version 7.65, 7.6, 7.5, 7.0, 6.0, 5.5, 5.0, 4.50, 4.0, or 3.0 installed on the computers you want to monitor

For version 6.0 systems:

  • Avaya patch MPLR29703 must be installed. The patch supports OM Report retrieval.

For version 5.5 systems:

  • Avaya patch Q01857201-p25859_1.ss1 must be installed on Signaling Servers. The patch corrects a problem in which entries for unregistration attempts for model 2211 phones are missing in the OM Report.

For version 5.0 systems:

  • Avaya patch MPLR24316 must be installed on Call Servers. The patch corrects the entityPhysicalDescr MIB variable, which falsely reports IP telephony phones as Digital phones.

  • Avaya software load MGCCAD35 or later must be installed on Media Gateway Controllers. The load enables OM Report retrieval.

For version 4.50 systems:

  • Avaya patch MPLR21714 must be installed on Signaling Servers. The patch enables BMZ support and requires manual configuration on the Call Server. For more information, see the patch ReadMe.

  • Avaya patch MPLR22309 must be installed on VGMCs. The patch enables VGMC trap retrieval.

  • Avaya patch MPLR23300 must be installed on Call Servers. The patch corrects a problem with Call Server QoS messages containing the wrong severities.

  • Avaya patch MPLR23560 must be installed on Call Servers. The patch corrects a problem with Zone statistics in which average bandwidth value may be higher than peak bandwidth value.

NOTE:You can obtain all patches and software loads from your Avaya support and maintenance provider.

Microsoft Windows SNMP service installed and configured

Configure AppManager Security Manager as follows:

  • For the Call Server, Media Gateway, ECM, NRS, and SIPL, configure the read-only SNMP community strings

  • For the Signaling Server, VGMC, MC32S, and MGC, configure the read/write SNMP community strings.

  • For a co-resident Call Server and Signaling Server, configure the read/write SNMP community strings.

For more information, see the AppManager for Avaya (Heritage-Nortel) Communication Server 1000 Management Guide.

SL1 Level 1 login ID and password configuration

For CS1000 version 3.0 only, configure AppManager Security Manager with the SL1 Level 1 login ID and password. For more information, see the AppManager for Avaya (Heritage-Nortel) Communication Server 1000 Management Guide.

PDT password configuration

For CS1000 version 3.0 only, configure AppManager Security Manager with the PDT password. For more information, see the AppManager for Avaya (Heritage-Nortel) Communication Server 1000 Management Guide.

ELAN IP addresses for all CS1000 devices that you want to monitor

Provide these addresses when setting up the Discovery_NortelCS Knowledge Script job.

To identify the ELAN IP address of the Call Server, issue the following command from Overlay 117: prt elnk.

Contact your CS1000 system administrator for the IP addresses of the other devices that you want to monitor. Each additional IP address needs to belong to the same subnet as the IP address of the Call Server.

NOTE:Do not use a TLAN IP address in place of an ELAN IP address.

File Transfer Protocol

Ensure FTP (File Transfer Protocol) works in your environment.

Ensure that no firewall prevents FTP from functioning on the ELAN.

AppManager for Avaya CS1000 uses FTP to transfer OM reports. For more information, see the AppManager for Avaya (Heritage-Nortel) Communication Server 1000 Management Guide.

AppManager for Network Devices module

Although the AppManager for Network Devices module is not required, you can greatly enhance your monitoring efforts by using the NetworkDevice scripts to monitor your CS1000 devices.

For more information, see the AppManager Module Upgrades & Trials page.

For more information on configuration, hardware requirements, and supported operating systems and browsers, see the AppManager for Avaya (Heritage-Nortel) Communication Server 1000 Management Guide, included in the download package.

3.0 Contents of the Download Package

AppManager for Avaya CS1000 includes a managed object, qNortelCSE1Ka4.dll, and Knowledge Scripts to discover and monitor Avaya CS1000 resources. The download package includes this release notes file, a management guide, Help for Knowledge Scripts, and several files that are used during installation:

  • AM70-NortelCS-7.4.104.0.msi, the module installer.

  • AM70-NortelCS-7.4.104.0.ini, a configuration file used with the AppManager setup program.

  • AM70-NortelCS-7.4.104.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-NortelCS-7.4.104.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.

  • ckNortelCS.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.

4.0 Installing This Module

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. 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.

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 Avaya (Heritage-Nortel) Communication Server 1000 Management Guide, included in the download package.

5.0 Known Issues

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.

5.1 General

  • The CallCapacity Knowledge Script does not work on recent versions of Avaya Communication Server 1000. This Knowledge Script does not work on computers running Avaya Communication Server 1000 version 5.5 or later. (ENG264132)

  • ELAN IP address required for discovery. Although it is possible to discover some CS1000 devices using the TLAN IP address, the Discovery_NortelCS job will not create objects that can be monitored successfully. Always specify ELAN IP addresses, not TLAN IP addresses, when discovering CS1000 devices. For more information, see the Help for the Discovery_NortelCS Knowledge Script. (ENG286390)

  • No event information if alarm severity is changed. An event for the Alarms Knowledge Script does not include a brief description of the event or recommend any corrective action if you changed the severity of the alarm from its default value.

5.2 Version 5.0

  • CallCapacity script returns incorrect data streams from CPPM Call Servers. The CallCapacity Knowledge Script returns incorrect data streams from CPPM Call Servers on CS1000 version 5.0. Avaya has filed CR Q01672353-01 to rectify the problem in a future release.

5.3 Versions 4.0 and 4.50

  • No phones in Entity MIB after Call Server reboot. The Entity MIB does not contain any IP phones after a Call Server reboot. Although you may have issued the proper Overlay 117 commands prior to discovery, the INV ENTITY SETS ON command does not persist after a Call Server reboot. If your Call Server has rebooted, re-issue the command and rerun Discovery_NortelCS.

  • SNMP v2 not supported on Call Server 4.50. The Call Server for CS1000 version 4.50 supports only Simple Network Management Protocol (SNMP) version 1.

6.0 Previous Releases

This release of AppManager for Avaya CS1000 includes enhancements added in previous releases, which were released under the name AppManager for Nortel CS1000.

6.1 Release 7.4.85.0, April 2015

This release of AppManager for Avaya CS1000 resolved the following issues:

  • Discovery_NortelCS Knowledge Script fails if you run it on both encrypted and non-encrypted NortelCS MIB files. This release addresses an issue in which the Discovery_NortelCS script failed and generated an event stating that AppManager detected an internal coding bug. This situation occurred when the environment on which you were running this script included both this module and the AppManager for SNMP Traps module, which handle encrypted and unencrypted MIB files differently. With this release, the Discovery_NortelCS script can handle duplicate definitions in encrypted and unencrypted MIBs without failing. (ENG336487)

  • NortelCS_Alarms Knowledge Script takes too much time to stop. This release addresses an issue in which a NortelCS_Alarms job remained in a state of Pending for an unexpectedly long time before it stopped. With this release, an update to the timeout value for the NortelCS_Alarms script ensures that jobs complete in the expected amount of time. (ENG336956)

6.2 Release 7.4.78.0, May 2014

This release of AppManager for Avaya CS1000 provided the following enhancement:

  • Support for Avaya CS1000 version 7.65. You can use this release of AppManager for Avaya CS1000 to monitor Avaya CS1000 version 7.65.

This release resolved the following issue:

  • Discovery_NortelCS Knowledge Script fails when trying to discover a CS1000 7.65 computer. This release resolves an issue in which the Discovery_NortelCS did not recognize CS1000 7.65 computers as call servers, and discovery failed as a result. With this release, the script successfully discovers 7.65 computers. (ENG334098)

6.3 Release 7.4.63.0, July 2013

This release provided the following enhancements:

  • Support for Windows Server 2012 and Windows 8. This release now supports computers running Microsoft Windows Server 2012 and Windows 8.

  • Support for Avaya CS1000 versions 7.0 and 7.5. All Knowledge Scripts in the NortelCS category support versions 7.0 and 7.5, except the CallCapacity Knowledge Script.

This release resolved the following issues:

  • Call Server version incorrect for 4.50. This release resolves an issue where object details for switches running Call Server version 4.50 reported the version as n/a. (ENG304097)

  • Alarms Knowledge Script does not properly exclude alarms. This release resolves an issue where the Alarms Knowledge Script stops filtering alarms once a five minute interval occurs between alarms. (ENG300765)

6.4 Release 7.4.34.0, June 2010

This release resolved the following issues:

  • Support for CS1000 version 6.0. This release provides support for monitoring Communication Server 1000 version 6.0 environments. All Knowledge Scripts in the NortelCS category support version 6.0 except for the CallCapacity Knowledge Script. Support for version 6.0 includes the following new features:

    • Alarms Knowledge Script can run on SIP Line resources.

    • Version 6.0 Bandwidth Management Zone resource objects are children of Call Servers. For previous versions of CS1000, BMZ resource objects are children of Signaling Servers.

    • Data stream legends generated by the BMZ_CallQuality Knowledge Script provide the complete BMZ object name, which is a combination of the device name and BMZ number. In previous releases of this module, legends provided the device IP address and BMZ number.

  • Discovery of SIP Line Gateway servers. The Discovery_NortelCS Knowledge Script now discovers SIP Line (SIPL) Gateway servers.

  • Discovery of co-resident Signaling Servers, Call Servers, and Element Managers. The Discovery_NortelCS Knowledge Script now discovers co-resident Signaling Servers, Call Servers, and Element Managers. When co-resident, these components reside on a single server.

7.0 Third-Party Software

NetIQ AppManager for Nortel Communication Server 1000, as well as any and all adapters, modules, updates, modifications thereto (“Software”) is distributed with certain Third Party Software and Open Source Software (as may be defined in the license agreement between you and NetIQ).

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 use 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.

Nexgen

NexgenServer.dll

Copyright (c) 2003-2006, Brian Davis

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:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • 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.

  • 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/)"

  • 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.

  • 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).

Original 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:

  • Redistributions of source code must retain the copyright notice, this list of conditions and the following disclaimer.

  • 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.

  • 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 :-).

  • 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.]

netSNMP

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.

---- 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.

---- 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:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • 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.

  • 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.

---- 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:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • 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.

  • 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.

---- Part 4: Sun Microsystems, Inc. copyright notice (BSD) -----

Copyright © 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:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • 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.

  • 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.

---- 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:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • 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.

  • 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.

---- 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:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • 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.

  • 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.

---- 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:

  • Redistributions of source code must retain the above copyright notice, this list of conditions and the following disclaimer.

  • 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.

  • 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.

MarshallSoft

fce32.dll

Copyright (C) MarshallSoft Computing Inc.

Last Modified April, 2010

AppManager for Nortel Communication Server 1000, v7.4

8.0 Contact Information

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.