AppManager for Network Devices monitors a wide array of devices, such as switches, routers, and gateways, by using SNMP to poll Management Information Bases (MIBs). The module includes Knowledge Scripts for creating jobs that monitor the health, availability, and performance of key devices.
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 website 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 website.
This release of AppManager for Network Devices provides the following enhancement:
Support for Transport Layer Security 1.2 (TLS): This release of AppManager for Network Devices provides support for TLS 1.2.
This release of AppManager for Network Devices resolves the following issue:
Avaya G450 Media Gateway discovered as Call Server: Since Avaya G450 Media Gateway is not supported, it is discovered as Call Server. With this release of AppManager for Network Devices, a new device, Avaya G450 Media Gateway, is supported for monitoring. (ENG345239)
Error discovering VMware-vCenter-Server-Appliance: While discovering VMware-vCenter-Server-Appliance, the module crashes because of buffer overrun or string conversions or unhandled exceptions. With this release of AppManager for Network Devices, VMware-vCenter-Server-Appliance is discovered without any errors. (ENG345486)
NetworkDevice_Host_ProcessDown KS crashing agent service: NetworkDevice_Host_ProcessDown KS crashes the agent service when it is run on the device, which does not respond to the SNMP requests. With this release of AppManager for Network Devices, NetworkDevice_Host_ProcessDown KS does not affect the agent service. (ENG348178)
To get the updates provided in this release, you must install the module to the AppManager repository (QDB) and on the agent cozmputer, 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 Network Devices replaces all Previous Releases.
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 Network Devices has the following system requirements:
|
Software/Hardware |
Version |
|---|---|
|
NetIQ AppManager installed on the AppManager repository (QDB) computers, on the proxy computers you want to monitor (agents), and on all console computers |
8.0.3, 8.2, 9.1, 9.2, 9.5, or later One of the following AppManager agents are required:
|
|
Microsoft Windows operating system on the agent computers |
One of the following:
|
|
AppManager for Microsoft Windows module installed on the AppManager repository (QDB) computer, on the proxy computers you want to monitor (agents), and on all console computers |
7.6.170.0 or later |
|
Microsoft SQL Server Native Client 11.0 (for TLS 1.2 support) |
11.3.6538.0 or later NOTE:The SQL Server Native client can be installed from this Microsoft download link. |
For more information on hardware requirements and supported operating systems and browsers, see the AppManager for Network Devices Management Guide, included in the download package.
NOTE:If you want TLS 1.2 support and are running AppManager 9.1 or 9.2, then you are required to perform some additional steps. To know about the steps, see the article.
AppManager for Network Devices includes a managed object, qNetworkDevicea4.dll, and Knowledge Scripts to discover and monitor Network Devices resources. The download package includes a release notes, a management guide, Help for Knowledge Scripts, and several files that are used during installation:
AM70-NetworkDevice-7.6.106.0.msi, the module installer.
AM70-NetworkDevice-7.6.106.0.ini, a configuration file used with the AppManager setup program.
AM70-NetworkDevice-7.6.106.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-NetworkDevice-7.6.106.0-RepositoryFiles.exe, a compressed file that contains the QDB and console files. You do not need to run this file during installation.
ckNetworkDevice.exe, the pre-installation check used with the AppManager setup program.
DefaultRule_NetworkDevice.xml, a configuration file used for deploying the module with Control Center.
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 the proxy computers you want to monitor (agents) 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 and, where relevant, the Analysis Center reports. You can install these components into local or remote QDBs. When installing to the primary 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:Microsoft .NET Framework 3.5 is required on the computer where you run the installation program for the QDB portion of the module. For computers running more recent versions of Windows operating systems that use a newer version of .NET, install .NET 3.5 with the Add Roles and Features wizard in Windows Server Manager, as described in this Microsoft article.
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 and Analysis Center reports 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 Network Devices 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.
Unable to use CISCO-POP-MGMT-MIB for channels that have three identifiers: Because of a limitation with the ISDN MIB implementation in some Cisco Integrated Services Routers, some of the data about ISDN channels is not available. As a result, this module cannot monitor the channel utilization for channels with three identifiers. Cisco is aware of this limitation, but they do not have a timeline for when they will make a fix available. (ENG299909)
SNMP v3 discovery requires additional processing overhead: It takes about three times longer to discover network devices running SNMP v3 than devices running SNMP v1 or v2, especially if you configured SNMP v3 for authentication and privacy.
Incompatibility between recent AppManager for Network Devices releases and trap receiver functionality in other modules: Modules that use the Async managed object for trap reception, based on the Windows SNMP Trap Service, will encounter a conflict with the NetIQ SNMP Trap Receiver functionality included in AppManager for Network Devices, versions 7.2.50.0 and later. The conflict inhibits trap reception because both trap receivers use UDP port 162.
Affected applications include the AppManager for NortelCS, NortelBCMx, NortelCC, and CiscoICM modules, and the SNMP trap functionality in the AppManager for Windows module for versions earlier than 7.6.170.0. If you are using any of these modules, you must manually ensure reception and processing of traps by the Async managed object by following the instructions given below.
NOTE:AppManager for Microsoft Windows module versions 7.6.170 and later support the NetIQ SNMP Trap Receiver functionality.
The following instructions apply whether you are upgrading the AppManager for Network Devices module or installing it for the first time. Perform the steps after installing the AppManager for Network Devices module and the Windows SNMP Trap Service.
To receive and process traps using the Async managed object:
From the Control Panel on the proxy agent computer, double-click Administrative Tools > Services.
Stop the NetIQ AppManager Client Resource Monitor service.
Stop the NetIQ Trap Receiver service.
In the Properties dialog box for the NetIQ Trap Receiver service, change the Startup type field to Manual, and then click OK.
NOTE:Do not start the service.
Restart the SNMP Trap Service.
IMPORTANT:Ensure you restart the Windows SNMP Trap Service, not the NetIQ Trap Receiver service.
Start the NetIQ AppManager Client Resource Monitor service. You can now receive and process traps with modules that use the Async managed object and the Windows SNMP Trap Service. Restarting the computer will not affect the changes you made.
This release of Network Devices includes enhancements added in previous releases.
This release of AppManager for Network Devices resolved an internal issue.
This release also includes the following enhancement that was provided in the Release 7.6.0.2:
Introduces the Network Devices reports for Reporting Center: The Network Devices reports for Reporting Center allow you to generate consolidate report from the CCDB. This release adds the following Network Devices reports templates:
Chassis Usage: Displays the Good-Acceptable-Poor (GAP) and average usage for CPU, memory pool, and backplane for a network device.
Device Availability: Displays the availability of the selected network devices.
ISDN Call Volume: Displays the average ISDN channel call volume for the links on the selected network devices.
ISDN Time Detail: Displays the average ISDN statistics on the selected trunks.
ISDN Utilization: Displays the average ISDN channel utilization for the selected network devices over a time range.
Link Utilization: Displays the average link usage for the selected network devices.
QoS Utilization: Displays the average traffic class statistics for the links on the selected network devices.
QoS Volume: Displays the overall QoS volume usage on hourly or daily basis for the selected network devices.
Total Volume: Displays the total link usage for the selected network devices.
This release also includes the following issue that was resolved in the Release 7.6.0.2:
Discovery_NetworkDevice fails to discover the Hirschmann network switches: The Discovery_NetworkDevice Knowledge Script failed to get the MAC addresses of the Hirschmann network switches in few scenarios and therefore the switches were not discovered. In this release, the issue is resolved. (ENG343601)
This release of AppManager for Network Devices resolved the following issue:
Discovery_NetworkDevice fails to discover Hirschmann network switches: The Discovery_NetworkDevice Knowledge Script failed to get the MAC addresses of the Hirschmann network switches and therefore the switches were not discovered. In this release, the issue is resolved. (ENG343601)
This release provided the following enhancements:
Support for Microsoft Windows Server 2016, Windows 10, Windows Server 2012 R2, and Windows Server 2012: This release supports Microsoft Windows Server 2016, Windows 10, Windows Server 2012 R2, and Windows Server 2012. For more information, see the System Requirements.
Added new Knowledge Scripts for fiber channel: Following Knowledge Scripts are added for fiber channel:
FCFXPort_Health: Monitors the operational status of a FCFE module and FCFX port on a fiber channel switch. This Knowledge Script also creates data streams for the number of operational FCFX ports and the total FCFX ports for a FCFE module.
FCFXPort_Util: Monitors the FCFX port usage on a fiber channel switch and creates data streams for a FCFX port usage.
Chassis_Usage monitors foundry device chassis objects: In this release, you can use the Chassis_Usage Knowledge Script to monitor the fan and the power supply for foundry device chassis objects.
Host_CPULoaded monitors the average CPU load across all processors: In this release, you can use the Host_CPULoaded Knowledge Script to monitor the average CPU load across all processors and raises an event when the average CPU utilization crosses the specified threshold.
Device_Ping raises an event when monitoring fails: In this release, the Device_Ping Knowledge Script raises an event when monitoring fails.
Improved performance for Host_ProcessDown jobs: In this release, you can enable the caching mechanism for PIDs in the Host_ProcessDown Knowledge Script. Caching the PIDs improves the performance of jobs.
This release resolved the following issues:
CompVal() function is missing in Action_RunDiscovery: In this release, the CompVal() function is added in the Action_RunDiscovery Knowledge Script. (ENG341942)
Devices with same object name are not discovered. This release resolves an issue in which the network devices with same object name but with different IP addresses were not getting discovered. In this release, all network devices with same object name are discovered successfully. (ENG342878)
This release provided the following enhancement:
NetworkDevice_Host_ProcessDown job includes new parameters to collect data for specific processes. This release inlcudes few new parameters where you can specify if you want to collect data for all the processes that are being monitored or collect data for specific processes. You can specify one or more processes separated by commas for which you want to limit the data collection.
For example, if you are monitoring proc1, proc2, and proc3 but has not specified any process for data collection, then the data will be collected for all the processes that are being monitored. Also, events will be generated if any of these processes are down. On the other hand, if you are monitoring proc1, proc2, and proc3 and specify the data collection for proc3, proc4, and proc5, then event will be generated for proc1, proc2 and proc3 if any of these processes are down. But, data will be collected only for proc3, proc4, and proc5. (ENG337580)
This release resolved the following issue:
NetworkDevice_Host_ProcessDown job hangs if SNMP process goes down when the requests queue up. This release resolves an issue in which the NetworkDevice_HostProcessDown job hanged if SNMP process took longer time to respond if the requests queued up. This release includes a parameter to enable SNMP GETBulk operation so that the responses are returned as a single packet than issuing multiple requests thus optimizing the bandwidth. The NetworkDevice_Host_ProcessUp Knowledge Script also includes this option now. (ENG337094)
This release provided the following enhancements:
Support for Advanced Encryption Standard (AES) encryption algorithm. This release now supports the AES encryption algorithm in addition to the Data Encryption Standard (DES) encryption algorithm. (ENG312717)
Link partner field displays the details for Hirschmann devices. This release displays the details in the Link Partner field for the devices that are linked to Hirschmann devices. If you select a device, the Details tab of the selected device contains a Link Partner field that displays the IP Address and the MAC address or Device ID of the partner that the device is linked to. (ENG333932)
Event messages include the device IP address to avoid confusion of events raised from devices with same name. When AppManager raises an event, it displays the device name for which the event is raised. If you have configured two devices with the same name, then it is difficult to identify the device for which the event is raised. With this release, AppManager displays the IP Address of the device along with the device name in the event message. (ENG299203)
Configurable SNMP timeout and SNMP retries. This release now supports configurable SNMP timeout and SNMP retries for advanced users. For SNMP timeout, you can specify the length of time in milliseconds for the job to wait for the SNMP response from the monitored network device before timing out and raising a failure event. For SNMP retries, you can specify the number of times the job should attempt to get the SNMP response from the monitored network device. (ENG245914)
Configurable event severity for job failure notifications. This release now lets you specify the event severity in the user interface when the job fails, the job returns warnings, or the monitoring fails. (ENG270225 and ENG294147)
Improved echo settings in the Device_Ping Knowledge Script. This release now supports enhanced echo settings in the Device_Ping Knowledge Script. You can specify the number of echo requests to send and maximum number of timeouts that can occur before raising an event. You can now specify if timeouts and job iterations must be consecutive before raising an event. (ENG335321 and ENG331427)
Option to specify units to collect datastreams. This release now lets you specify the units for link and traffic utilization datastream collection. The available unit options include bytes per second, kilobytes per second, and megabytes per second. Irrespective of the unit you select in different Knowledge Scritps, the report script displays the datastream values on charts in megabytes per second. (ENG262445, ENG335288, and ENG335276)
This release also resolved the following issues:
Discovery_NetworkDevice Knowledge Script fails to discover Avaya Application Enablement Service. This release resolves an issue where the Discovery_NetworkDevice Knowledge Script failed to discover the Avaya Application Enablement Service because of a IP Address and subnet mask size mismatch. With this release, the Discovery_NetworkDevice Knowledge Script now discovers Avaya Application Enablement Service. (ENG325075)
NetworkDevice_Device_Ping Knowledge Script creates continuous state change events. This release resolves an issue in which AppManager raised events incorrectly, if you specified the consecutive job iteration to be more than 1. In the Consecutive job iterations before raising event parameter of the NetworkDevice_Device_Ping Knowledge Script, if you specified a value other than the default value of 1 and selected the Generate a new event when original event condition no longer exists option in the Advanced tab of the Knowledge Script, AppManager incorrectly raised state change event even when the specified event condition was met. With this release, this script generates a state change event only when there is a state change for a device. (ENG323642)
SNMP timeout error displays as job failure error. This release resolves an issue where the SNMP timeout error when a device was down or not connectable displayed as a job failure error and AppManager raised an excessive amount of events. With this release, SNMP timeout error is properly handled and does not generate events as job failure error. (ENG333647)
Network Device module could not calculate the non-unicast packet information. This release resolves an issue where the module could not calculate the non-unicast packet information when ifInNUCastPkts and ifOutNUcastPkts OID were not present. With this release, the module uses the ifInMulticastPkts, ifInBroadcastPkts and ifOutMulticastPkts, ifOutBroadcastPkts respectively, to calculate the non-unicast packet information when ifInNUcastPkts and ifOutNUcastPkts OIDs are not present. (ENG331189)
NetworkDevice_Device_Syslog Knowledge Script raises an event without any detail. This release resolves an issue where the NetworkDevice_Device_Syslog Knowledge Script raised an event that did not show the Syslog message if the message received from the Syslog devices did not have a header or message text. With this release, the script displays the raw Syslog message even if the message received from the Syslog devices does not have the header or message text. (ENG329427)
Trap receiver disconnects sporadically. This release resolves an issue where the trap receiver disconnected because of DISMAN-EVENT-MIB::sys ODE to OID conversion was not handled properly. With this release, the DISMAN-EVENT-MIB::sys ODE to OID conversion is handled properly. (ENG274804)
Trap receiver disconnects randomly and the Listener is out of sync. This release resolves an issue where the trap receiver disconnected randomly because of 1.3.6.1.4.1.9.9.41.1.2.3.1.2.0 OID to ODE conversion. With this release the OID to ODE conversion is handled properly. (ENG330070)
This release resolved the following issue:
NetworkDevice_ISDNChannel_Util charts sometimes display inaccurate data. This release addresses an issue in which the data points for some of the NetworkDevice_ISDNChannel_Util jobs showed the same ISDN channel usage for different channels with 3-tuple indexes (slot/sub-slot/port). With this release, changes to the code of the managed object allow the NetworkDevice_ISDNChannel_Util job to collect accurate information about ISDN channel usage. However, due to a limitation with some Cisco hardware, not all ISDN interfaces share information about the number of active channels available with this job.For more information, see the Known Issues. (ENG299909)
This release resolved the following issues:
A NetworkDevice job failed due to a timeout. This release addresses an issue in which a NetworkDevice job timed out when the number of object identifiers (OIDs) it attempted to query was any number that was one less than the specified maximum number of OIDs in a batch. With this release, all NetworkDevice jobs properly calculate the data when querying OIDs. (ENG308608)
Network Device trap receiver discovery fails when TCP is not initialized. This release addresses an issue in which TCP was not initialized, which caused the trap client to not initialize properly, and the trap receiver discovery failed. Trap receiver discovery also failed if the discovery process could not find the computer name on a Windows XP computer. With this release, the trap client initializes properly, and the discovery job locates the computer name on Windows XP computers. As a result, the trap receiver discovery succeeds. (ENG305767)
The TreeView for Network Devices lists WAN multilinks under the wrong interface. This release resolves an issue in which, after you ran the Discovery_NetworkDevice Knowledge Script, the WAN multilinks of type “PPP multilink bundle” displayed in the TreeView under individual interfaces instead of under the WAN object. With this release, the addition of PPP multilink bundle type 108 as a WAN link type to the Discovery_NetworkDevice script ensures that the WAN multilinks display properly under the WAN object in the TreeView. (ENG305358)
The NetworkDevice_LANLink_Util Knowledge Script does not accurately reflect changes in bandwidth capacity. This release resolves an issue in which the NetworkDevice_LANLink_Util job did not account for the upgraded capacity of a network device. With this release, changes to the script enable the NetworkDevice_LANLink_Util job to recognize the newly updated capacity of an existing network device. (ENG304544)
The NetworkDevice_LanLink_Util Knowledge Script does not collect data. This release resolves an issue in which the NetworkDevice_LanLink_Util job did not properly insert data points for data collection when monitoring 64-bit counters. With this release, a change to the NetworkDevice_LanLink_Util script ensures that the script collects data correctly. (ENG308233)
This release also provided the following enhancement:
Support for Windows 7. This release now supports 32-bit and 64-bit Windows 7.
This release resolved the following issues:
Cisco Nexus 5000 series devices are shown as unknown device type. This release resolves an issue where, after discovery, AppManager displayed a Cisco Nexus 5000 series device as an unknown type in the TreeView. (ENG296385)
Interface_Health Knowledge Script fails to report an event for protocol down state. This release resolves an issue where the Interface_Health Knowledge Script did not raise an event for an interface in the down state, even if you set the job parameters to detect that condition. (ENG298896)
Ping Knowledge Script does not properly handle the Maximum Number of Consecutive timeouts parameter. This release resolves an issue where the NetworkDevice_Ping Knowledge Script ignored any value for the Threshold - Maximum Number of Consecutive timeouts parameter that was not 1. The script would not raise an event if the threshold was not set to 1. This release also provided the following enhancement:(ENG301967)
This release also provided the following enhancement:
Receives SNMPv2 traps without TrapOID and sysUpTime values. This release allows the Async_SNMPTrap Knowledge Script to report events related to SNMPv2 traps that are incorrectly formatted due to lack of TrapOID and sysUpTime values. (ENG299516)
This release resolved the following issue:
Devices with multiple IP addresses are discovered more than once. This release resolves an issue in which the Discovery_NetworkDevice Knowledge Script job discovers the same device several times when the device has multiple IP addresses. The device appears in the TreeView multiple times, once for each different IP address. Because licensing of the module is based on the number of discovered devices, multiple discoveries of the same device may use many licenses. This release provides a new parameter in Discovery_NetworkDevice that allows you to select whether to discover only the device or the device and all associated IP addresses. For more information, see the Help for Discovery_NetworkDevice. The new parameter is Discover IP addresses that belong to the same device? (ENG294204)
This release resolved the following issues:
Discovery fails on devices with numerous IP addresses. This release resolves an issue in which the Discovery_NetworkDevice Knowledge Script job fails when attempting to discover devices that have a large number of IP addresses. With this release, a code change in the SNMP polling process resolves the problem. (ENG279144)
Cisco switches do not respond to SNMP requests. This release resolves an issue in which some Cisco switches do not respond to SNMP GET or GETNext requests. The SNMP requests fail because they use MIBs that the Cisco switches no longer support: ifInNUcastPkts and ifOutNUcastPkts. With this release, SNMP requests use newer MIBs that Cisco does support: ifInMulticastPkts, ifInBroadcastPkts, ifOutMulticastPkts, and ifOutBroadcastPkts. (ENG283123)
ATMLink_Util jobs do not collect data or raise events. This release resolves an issue in which the SingleATMLink_Util and ATMLink_Util Knowledge Script jobs do not collect data or raise events. With this release, a code change allows the scripts to collect data and raise events when those options are enabled on the Values tab in the scripts' Properties dialog boxes. (ENG292934)
This release provided the following enhancement:
Finer control over link and channel monitoring. With this release, several Knowledge Scripts provide a new parameter that allows you to precisely define the links and channels you monitor: Include or exclude name filter. For more information, see the Help for the following Knowledge Scripts. (ENG270243)
ATMLink_QoS
ATMLink_Util
FrameRelayLink_QoS
FrameRelayLink_Util
ISDNChannel_CallVolume
ISDNChannel_Health
ISDNChannel_Util
LANLink_QoS
LANLink_Util
WANLink_QoS
WANLink_Util
This release resolved the following issue:
Device_Ping script stalls on proxy agent computer. This release resolves an issue in which the NetworkDevice_Device_Ping Knowledge Script job stalls, preventing other Knowledge Script jobs from starting or completing. With this release, the Device_Ping script, originally written in BasicScript, is rewritten in VBScript, which resolves the stalling problem. (ENG280472)
This release resolved the following issues:
Discovery fails on devices using UCD-SNMP-MIB as sysObjectID. This release resolves an issue in which the Discovery_NetworkDevice Knowledge Script job fails to discover devices with the UCD-SNMP-MIB as the sysObjectID. With this release, a code change allows the Discovery job to discover devices that use the UCD-SNMP-MIB as their sysObjectID. (ENG287018)
Discovery fails with a SQL Server error. This release resolves an issue in which the Discovery_NetworkDevice Knowledge Script job fails with the following error message: SQLSTATE=01000, native error=0; msg='[Microsoft][ODBC SQL Server Driver];Ongoing transaction has been committed. The failure is caused by invalid XML characters in the Host MIB. With this release, invalid XML characters are replaced with *_*, which allows the Discovery job to proceed successfully. (ENG287569)
Scripts report link errors when device reports none. This release resolves an issue in which the four Link_Util Knowledge Scripts report link errors, but the monitored devices report no link errors. The discrepancy occurs because the calculation the scripts use for determining link errors includes discarded packets. With this release, a new parameter allows you to choose whether to include discarded packets in the calculation. The new parameter, Include discards in link errors?, is available in the following Knowledge Scripts. For more information, see the Help for each script: (ENG287970)
LANLink_Util
SingleLANLink_Util
SingleWANLink_Util
WANLink_Util
This release resolved the following issues:
Discovery fails on some switches. This release resolves an issue in which the Discovery_NetworkDevice Knowledge Script job fails on some vendor’s switches due to vendor differences in the SNMP encoding of ipv6Address objects. With this release, a code change allows the Discovery_NetworkDevice job to discover devices that encode the SNMP indexes of ipv6Address objects as either fixed-length and variable-length octet strings. (ENG286193)
WANLink_Utilization job returns counter value of zero. This release resolves an issue in which the NetworkDevice_WANLink_Utilization Knowledge Script job returns a value of zero for some monitored counters, when the actual counter value should be other than zero. Cisco IOS® software does not support 64-bit (high capacity) counters for interface speeds of less than 20 Mbps, so values for these counters are set to zero, which the script uses in its calculations. A code change allows the WANLink_Utilization script to verify interface speed and then use the values of 32-bit counters for speeds less than 20 Mbps and use 64-bit counters for high-speed interfaces. (ENG286213)
This release resolved the following issue:
Discovery fails for Cisco ASA devices. Before you install this release, attempts to discover some types of Cisco ASA devices return the following error message: CHR0403: The request for Discover Device Vendor and Type from device [IP address] failed. The Discovery_NetworkDevice Knowledge Script relies on the information in the sysServices.0 SNMP object, which should be populated by the devices you want to discover. Some types of Cisco ASA devices do not populate the sysServices.0 SNMP object. After you install this release, Discovery succeeds even if the sysServices.0 SNMP object is not populated by the device. In this case, the devices are discovered as “Unknown” types. (ENG282614)
This release resolved the following issues:
DeviceUptime job raises event when management portion of device is restarted. Before you install this release, the NetworkDevice_DeviceUptime Knowledge Script job raises an event when the management portion of a monitored device is restarted, even if the device itself has not rebooted. After you install this release, a new parameter lets you choose when to raise an event. With the new parameter, Monitor host uptime or uptime of the network management portion of the system, you can select Host uptime to monitor the uptime of a host device, or Management component uptime to monitor the uptime of the management component of a device, independent of the uptime of the host device. (ENG274408)
The LinkUtilization and ISDNCallVolume reports contain no data. Before you install this release, the LinkUtilization and ISDNCallVolume reports return an error message saying No data for report. The error is caused by code limiting the size of retrieved Knowledge Script names to 40 characters. After you install this release, the limit is increased to 256 characters and the reports runs successfully. (ENG274841) (ENG275785)
Discovery fails when the object identifier (OID) is missing. Before you install this release, the Discovery Knowledge Script fails when the IP-MIB::ipForwarding.0 OID cannot be retrieved. After you install this release, a code change allows the IP-MIB::ipForwarding.0 OID to be successfully discovered, and shown in the TreeView as an Unknown device. (ENG277760)
This release resolved the following issues:
Device_Syslog job fails even though syslog managed object is installed. Before you install this release, the NetworkDevice_Device_Syslog Knowledge Script job fails with the following error message: Could not create object: NetIQAgent.Syslog. Please verify that the Syslog MO is installed. The installation program for AppManager for NetworkDevices installed the syslog managed object, qSysloga4.dll, but did not register it. After you install this release, the syslog managed object is installed and registered. (ENG253489)
Report_LinkUtilization job does not create graphs for packet errors. Before you install this release, the NetworkDevice_Report_LinkUtilization Knowledge Script job does not create graphs for packet errors even though packet error data was collected. This problem occurs when interfaces return large values for incoming and outgoing octet counters. After you install this release, a change to a stored procedure allows the job to handle large and small amounts of data. (ENG254610)
Interface_Health cannot exclude interfaces from monitoring. Before you install this release, the NetworkDevice_Interface_Health Knowledge Script job does not provide a way to exclude certain interfaces from monitoring. After you install this release, the Filter details parameters allow you to include or exclude a selected device interface when monitoring. For more information, see the Help for the script. (ENG267767)
Interface name filter. Using regular expression, provide the name of the interface for the devices that you want to monitor or the devices you do not want to monitor. For example:
To monitor only ethernet interfaces, enter (?=Ethernet) and select Include in the Include or exclude interface name filter? parameter.
To monitor all interfaces EXCEPT ethernet interfaces, enter (?=Ethernet) and select Exclude in the Include or exclude interface name filter? parameter.
Include or exclude interface name filter? Select Include to monitor only the devices for the interface you specified in Interface name filter. Select Exclude to monitor all devices except for those associated with the interface you specified in Interface name filter.
LANLink_QoS and WANLink_QoS jobs do not return data. Before you install this release, the NetworkDevice_LANLink_QoS and NetworkDevice_WANLink_QoS Knowledge Script jobs do not return data if some of the monitored links do not have Quality of Service (QoS) configured. After you install this release, a change in the logic for both scripts allows them to collect data even when some monitored links are not configured for QoS. (ENG268141)
This release resolved the following issues:
Discovery_NetworkDevice job causes failure of netiqmc service for some Cisco devices. Before you install this release, an invalid SNMP object type provided by the Cisco device causes an unhandled exception, which results in the failure of the NetIQ Client Resource Monitor (netiqmc) service. After you install this release, a change in the code for Discovery_NetworkDevice prevents the unhandled exception and the subsequent failure of the netiqmc service. (ENG263703)
Device_Ping job returns inaccurate error message. Before you install this release, the NetworkDevice_Device_Ping Knowledge Script job returns the following error message, Ping failed to recognize the IP address of device, when the ping test fails for any reason, such as when the device is down, the device name cannot be resolved, or the ping times out. After you install this release, the error message more precisely identifies the problem that occurred during the ping test. (ENG266615)
This release resolved the following issues:
The SNMPTrap_Async Knowledge Script fails for Trap Receiver SNMP permissions. Before you install this hotfix, the NetworkDevice_SNMPTrap_Async Knowledge Script job fails when SNMP permissions/community strings differ between the Trap Receiver and the proxy computer. After you install this hotfix, a new Security Manager label allows you to identify the SNMP permissions for the Trap Receiver, which allows the SNMPTrap_Async Knowledge Script to work properly. For more information, see the Help for the SNMPTrap_Async Knowledge Script. (ENG254349)
This release provided support for 64-bit Microsoft Windows operating systems installed on the proxy agent computer. (ENG252786)
This release also resolved an issue in which discovery of the NetIQ Trap Receiver fails. After you install this release, you can successfully discover the NetIQ Trap Receiver. (ENG253577)
This release resolved the following enhancements:
Updates to NetworkDevice_SNMPTrap_Async. With this release, the SNMPTrap_Async Knowledge Script properly invokes Action Knowledge Scripts. (ENG246819)
UDP forwarding with NetIQ SNMP Trap Receiver. With this release, the NetIQ SNMP Trap Receiver, which ships with the AppManager for Network Device module, supports UDP forwarding, which allows you to forward incoming SNMP traps to another trap receiver using a different port number. For more information, see the AppManager for Network Device Management Guide, included in the module download package. (ENG247136)
This release resolved the following enhancements:
NetworkDevice_SNMPTrap_AddMIB. This new Knowledge Script lets you add MIB files to the MIB tree that is monitored by the NetworkDevice_SNMPTrap_Async Knowledge Script.
NetworkDevice_SNMPTrap_Async. This new Knowledge Script is a renamed version of the NetworkDevice_AsyncSNMPTrap Knowledge Script, which was released in January 2008. The new script provides the same functionality and the same parameters as the old script. It was renamed so that all SNMP-related scripts appear together on the NetworkDevice tab of the Operator Console.
You can continue using the AsyncSNMPTrap script with no break in service. However, no new functionality will be added to this script. Customer support issues will be handled within the new SNMPTrap_Async script. You are encouraged to switch to the new script.
There is no planned migration path between the scripts. You should configure and start new jobs within the SNMPTrap_Async script, while stopping all jobs related to the AsyncSNMPTrap script.
Support for IPv6. This release adds support for Internet Protocol version 6 (IPv6). AppManager for Network Device recognizes and displays IPv6 addresses in the Operator Console and Control Center.
This release provided the following enhancements:
Support for NetIQ SNMP Trap Receiver, which receives SNMP traps, filters them, and forwards them to AppManager. Trap Receiver is included in the AppManager for Network Device download package and is installed by default on the computers on which you install the module.
A new Knowledge Script, NetworkDevice_AsyncSNMPTrap, lets you filter SNMP trap messages by OID. The script raises events and generates data streams for Trap Receiver availability.
Three new parameters in the Discovery_NetworkDevice Knowledge Script let you discover Trap Receiver.
The AppManager for Network Devices 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.
Apache License: Distributions of log4j, log4net, log4cxx Apache License Version 2.0, January 2004 http://www.apache.org/licenses/ TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
Definitions. “License” shall mean the terms and conditions for use, reproduction, and distribution as defined by Sections 1 through 9 of this document. “Licensor” shall mean the copyright owner or entity authorized by the copyright owner that is granting the License. “Legal Entity” shall mean the union of the acting entity and all other entities that control, are controlled by, or are under common control with that entity. For the purposes of this definition, “control” means (i) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (ii) ownership of fifty percent (50%) or more of the outstanding shares, or (iii) beneficial ownership of such entity. “You” (or “Your”) shall mean an individual or Legal Entity exercising permissions granted by this License. “Source” form shall mean the preferred form for making modifications, including but not limited to software source code, documentation source, and configuration files. “Object” form shall mean any form resulting from mechanical transformation or translation of a Source form, including but not limited to compiled object code, generated documentation, and conversions to other media types. “Work” shall mean the work of authorship, whether in Source or Object form, made available under the License, as indicated by a copyright notice that is included in or attached to the work (an example is provided in the Appendix below). “Derivative Works” shall mean any work, whether in Source or Object form, that is based on (or derived from) the Work and for which the editorial revisions, annotations, elaborations, or other modifications represent, as a whole, an original work of authorship. For the purposes of this License, Derivative Works shall not include works that remain separable from, or merely link (or bind by name) to the interfaces of, the Work and Derivative Works thereof. “Contribution” shall mean any work of authorship, including the original version of the Work and any modifications or additions to that Work or Derivative Works thereof, that is intentionally submitted to Licensor for inclusion in the Work by the copyright owner or by an individual or Legal Entity authorized to submit on behalf of the copyright owner. For the purposes of this definition, “submitted” means any form of electronic, verbal, or written communication sent to the Licensor or its representatives, including but not limited to communication on electronic mailing lists, source code control systems, and issue tracking systems that are managed by, or on behalf of, the Licensor for the purpose of discussing and improving the Work, but excluding communication that is conspicuously marked or otherwise designated in writing by the copyright owner as “Not a Contribution.” “Contributor” shall mean Licensor and any individual or Legal Entity on behalf of whom a Contribution has been received by Licensor and subsequently incorporated within the Work.
Grant of Copyright License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable copyright license to reproduce, prepare Derivative Works of, publicly display, publicly perform, sublicense, and distribute the Work and such Derivative Works in Source or Object form.
Grant of Patent License. Subject to the terms and conditions of this License, each Contributor hereby grants to You a perpetual, worldwide, non-exclusive, no-charge, royalty-free, irrevocable (except as stated in this section) patent license to make, have made, use, offer to sell, sell, import, and otherwise transfer the Work, where such license applies only to those patent claims licensable by such Contributor that are necessarily infringed by their Contribution(s) alone or by combination of their Contribution(s) with the Work to which such Contribution(s) was submitted. If You institute patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Work or a Contribution incorporated within the Work constitutes direct or contributory patent infringement, then any patent licenses granted to You under this License for that Work shall terminate as of the date such litigation is filed.
Redistribution. You may reproduce and distribute copies of the Work or Derivative Works thereof in any medium, with or without modifications, and in Source or Object form, provided that you meet the following conditions:
You must give any other recipients of the Work or Derivative Works a copy of this License; and
You must cause any modified files to carry prominent notices stating that You changed the files; and
You must retain, in the Source form of any Derivative Works that You distribute, all copyright, patent, trademark, and attribution notices from the Source form of the Work, excluding those notices that do not pertain to any part of the Derivative Works; and
If the Work includes a "NOTICE" text file as part of its distribution, then any Derivative Works that You distribute must include a readable copy of the attribution notices contained within such NOTICE file, excluding those notices that do not pertain to any part of the Derivative Works, in at least one of the following places: within a NOTICE text file distributed as part of the Derivative Works; within the Source form or documentation, if provided along with the Derivative Works; or, within a display generated by the Derivative Works, if and wherever such third-party notices normally appear. The contents of the NOTICE file are for informational purposes only and do not modify the License. You may add Your own attribution notices within Derivative Works that You distribute, alongside or as an addendum to the NOTICE text from the Work, provided that such additional attribution notices cannot be construed as modifying the License. You may add Your own copyright statement to Your modifications and may provide additional or different license terms and conditions for use, reproduction, or distribution of Your modifications, or for any such Derivative Works as a whole, provided Your use, reproduction, and distribution of the Work otherwise complies with the conditions stated in this License.
Submission of Contributions. Unless You explicitly state otherwise, any Contribution intentionally submitted for inclusion in the Work by You to the Licensor shall be under the terms and conditions of this License, without any additional terms or conditions. Notwithstanding the above, nothing herein shall supersede or modify the terms of any separate license agreement you may have executed with Licensor regarding such Contributions.
Trademarks. This License does not grant permission to use the trade names, trademarks, service marks, or product names of the Licensor, except as required for reasonable and customary use in describing the origin of the Work and reproducing the content of the NOTICE file.
Disclaimer of Warranty. Unless required by applicable law or agreed to in writing, Licensor provides the Work (and each Contributor provides its Contributions) on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied, including, without limitation, any warranties or conditions of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A PARTICULAR PURPOSE. You are solely responsible for determining the appropriateness of using or redistributing the Work and aLimitation of Liability. In no event and under no legal theory, whether in tort (including negligence), contract, or otherwise, unless required by applicable law (such as deliberate and grossly negligent acts) or agreed to in writing, shall any Contributor be liable to You for damages, including any direct, indirect, special, incidental, or consequential damages of any character arising as a result of this License or out of the use or inability to use the Work (including but not limited to damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses), even if such Contributor has been advised of the possibility of such damages. ssume any risks associated with Your exercise of permissions under this License.
Accepting Warranty or Additional Liability. While redistributing the Work or Derivative Works thereof, You may choose to offer, and charge a fee for, acceptance of support, warranty, indemnity, or other liability obligations and/or rights consistent with this License. However, in accepting such obligations, You may act only on Your own behalf and on Your sole responsibility, not on behalf of any other Contributor, and only if You agree to indemnify, defend, and hold each Contributor harmless for any liability incurred by, or claims asserted against, such Contributor by reason of your accepting any such warranty or additional liability.
Net-SNMP License Various copyrights apply to this package, listed in various separate parts below. Please make sure that you read all the parts.
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. 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-2009, 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.
Part 8: Apple Inc. copyright notice (BSD) Copyright (c) 2007 Apple 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 Apple Inc. (“Apple”) 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 APPLE AND ITS 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 APPLE 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.
Part 9: ScienceLogic, LLC copyright notice (BSD) Copyright (c) 2009, ScienceLogic, LLC 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 ScienceLogic, LLC 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.
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. Actually both licenses are BSD-style Open Source licenses. In case of any license issues related to OpenSSL please contact openssl-core@openssl.org. Copyright (c) 1998-2008 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.
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.
Redistributions of any form whatsoever must retain the following acknowledgment: “This product includes software developed by the OpenSSL Project for use in the OpenSSL 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).Toolkit (http://www.openssl.org/)”
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 website.
For general corporate and product information, see the NetIQ Corporate website.
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) 2018 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.