Guest

Cisco Application Networking Manager

Release Note for the Cisco Application Network Manager (Software Version 3.x)

  • Viewing Options

  • PDF (657.2 KB)
  • Feedback
Release Note for the Cisco Application Networking Manager

Table Of Contents

Release Note for the Cisco Application Networking Manager

New Features in ANM 3.0

Home Page

Guided Setup

Network Monitoring Enhancements

ACE Module A2 (3.0) Feature Support

Simplification and Rework of ANM GUI Windows

New Features in ANM 3.1

Integration of ANM with VMware Virtual Data Center Environment

Enhanced User Role Configurations

Supported Devices and Software

ANM Product Documentation Set

Installing the ANM 3.x Software

ANM Operating Considerations

Assigning Names to ACE Objects

Using Homepage

Using the Firefox Web Browser to Access ANM 3.x

Software Version ANM 3.2 Resolved and Open Caveats

Software Version 3.2 Resolved Caveats

Software Version 3.2 Open Caveats

Software Version ANM 3.1 Resolved and Open Caveats

Software Version 3.1 Resolved Caveats

Software Version 3.1 Open Caveats

Software Version ANM 3.0 Resolved and Open Caveats

Software Version 3.0 Resolved Caveats

Software Version 3.0 Open Caveats

Copyright Notices

Apache 2.0 License, Version 2.0

Bouncy Castle Copyright Notice

Castor

Common Public License Version 1.0

GNU GENERAL PUBLIC LICENSE

GNU LESSER GENERAL PUBLIC LICENSE

Copyright Statement for JasperReports

Mozilla Public License Version 1.1

Obtaining Documentation and Submitting a Service Request


Release Note for the Cisco Application Networking Manager


July 21, 2010


Note The most current documentation for released products is available on cisco.com.


This release note applies to software version 3.0, 3.1, and 3.2 for Cisco Application Networking Manager (ANM). It contains the following sections:

New Features in ANM 3.0

New Features in ANM 3.1

Supported Devices and Software

ANM Product Documentation Set

Installing the ANM 3.x Software

ANM Operating Considerations

Software Version ANM 3.2 Resolved and Open Caveats

Software Version ANM 3.1 Resolved and Open Caveats

Software Version ANM 3.0 Resolved and Open Caveats

Copyright Notices

Obtaining Documentation and Submitting a Service Request


Caution The ANM 3.x images do not support upgrading from beta or pre-FCS ANM versions. Upgrading from a beta or pre-FCS version may cause ANM to remove data when you install the ANM image. If any data loss occurs, you will need to reimport all devices and modules that you previously imported.

New Features in ANM 3.0

This section describes the new and updated features of ANM 3.0 and includes the following topics:

Home Page

Guided Setup

Network Monitoring Enhancements

ACE Module A2 (3.0) Feature Support

Simplification and Rework of ANM GUI Windows

Home Page

Homepage is a launching point to selected areas within ANM. It appears under the Home option menu. Homepage includes quick access to a series of operational tasks, monitoring functions, Guided Setup tasks, configuration functions, critical alarms and events, and quick links to the associated user documentation. By default, the ANM Homepage is the first page that appears after you log in. From the ANM Homepage, you can specify a different page that appears as the default page after you log in.

Guided Setup

ANM 3.0 includes Guided Setup, which provides a series of setup sequences that offers screen guidance and networking diagrams to simplify the configuration of ANM and its associated ACE modules or appliances.

Guided Setup steps you through the following tasks:

Establish communication between ANM and ACE devices.

Configure ACE devices that are new to the network by establishing network connectivity in either standalone or high-availability (HA) deployments.

Create and connect to an ACE virtual context.

Set up a load-balancing application from an ACE to a group of backend servers.

To access Guided Setup in the ANM GUI, choose Config > Guided Setup.

Network Monitoring Enhancements

ANM 3.0 includes the following network monitoring enhancements:

Dashboards—Allows faster and more accurate assessment and analysis of device and virtual context health and usage, as well as performance. Corresponding monitoring views allow for quick access to details for further investigation into potential problems highlighted in the dashboards. Graphs, as well as monitoring screens, allow you to view historical data and compare the performance with the peer objects.

To access the dashboard feature in the ANM GUI, do the following:

For an ACE-specific dashboard, choose Monitor > Devices > ACE > Dashboard.

For a context-specific dashboard, choose Monitor > Devices > virtual_context > Dashboard.

For the all devices dashboard, choose Monitor > Devices > Groups > All Devices > Dashboard.

Historical Graphs—Displays data recorded during the last hour, 2-hour, 4-hour, 8-hour, 24-hour interval, or 30-day (last month) interval.

To access the historical graphs in the ANM GUI, choose Monitor > Devices, click on any view, and click the Graph button that is located at the bottom of the table.

Dedicated Real Server and Probe Views—Displays load-balancing information that is related to real servers and the probes that monitor the health and availability of a real server.

To access the dedicated real server and probe views in the ANM GUI, do the following:

Choose Monitor > Devices > device > Load Balancing > Real Servers.

Choose Monitor > Devices > ACE > Load Balancing > Probes.

New Polling and Monitoring Features—Enables polling and monitoring through thresholds and alarm generation for newly supported ACE MIB attributes, such as virtual server statistics and some specific probe statistics.

To access the new polling and monitoring features in the ANM GUI, choose Monitor > Alarm Notifications > Threshold Groups and Alarms.

ACE Module A2 (3.0) Feature Support

ANM 3.0 allows you to configure the following new features associated with the ACE module A2 (3.0) release:

SSL HTTP Header Insertion—Enables the ACE module to provide the server with the following SSL session information by inserting HTTP headers into the HTTP requests that it receives over the connection:

Session Parameters—SSL session parameters that the ACE module and client negotiate during the SSL handshake.

Server Certificate Fields—Information regarding the SSL server certificate that resides on the ACE module.

Client Certificate Fields—Information regarding the SSL client certificate that the ACE module retrieves from the client when you configure the ACE module to perform client authentication.

To access the SSL HTTP header insertion feature in the ANM GUI, choose Config > Devices > virtual_context > Expert > HTTP Header Modify Action Lists, click Add, and then click the SSL Header Insert tab.

Secondary IP Addresses—Allows you to create up to four secondary IP groups per VLAN or BVI (in addition to the primary IP address) for accepting client, server, or remote access traffic.

To access the configuration areas of the ANM GUI where the secondary IP addresses feature is located, do the following:

For VLAN interfaces, choose Config > Devices > virtual_context > Network > Vlan Interfaces.

For BVI interfaces, choose Config > Devices > virtual_context > Network > BVI Interfaces.

Fail Action Reassign Across VLANs—Instructs the ACE module to reassign the existing server connections to the backup real server on a different VLAN interface (commonly referred to as a bypass VLAN) if the real server fails.

To access the fail action reassign feature in the ANM GUI, do either of the following:

Choose Config > Devices > virtual_context > Load Balancing > Server Farms.

Choose Config > Devices > virtual_context > Load Balancing > Virtual Servers (located under Server Farm Attributes).

Redirect Upon SSL Session Setup Failure—Instructs the ACE module to redirect client certificate validation failures to either a redirect server farm or a redirect URL.

To access the redirect feature in the ANM GUI, choose Config > Devices > virtual_context > SSL > Parameter Maps and click the Redirect Authentication Failure tab.

Secure Backup & Restore—Allows you to back up or restore the configuration and dependencies of an entire ACE module or of a particular virtual context.

To access the backup and restore features in the ANM GUI, do either of the following:

For multiple ACEs, choose Config > Global > All Backups.

For specific contexts, choose Config > Devices > virtual_context > System > Backup/ Restore.

Sample SSL Certificate and Key Pair—Enables demonstration of the SSL functions (the certificate does not have a valid domain).

To display the sample SSL certificate or key pair in the ANM GUI, do either of the following:

For the sample certificate, choose Config > Devices > virtual_context > SSL > Certificates.

For the sample key pair, choose Config > Devices > virtual_context > SSL > Keys.

Simplification and Rework of ANM GUI Windows

For ANM 3.0, several of the GUI windows have been modified to enhance functionality and improve ease of use of the following functions:

Configuration tasks—Improves access to the most commonly performed tasks and advanced tasks in frequently used configuration windows. The windows with the most significant modifications are the VLAN Interfaces and Primary Attributes windows.

To access these windows in the ANM GUI, do the following:

For the VLAN configuration window, choose Config > Devices > virtual_context > Network > VLAN Interfaces.

For the Primary attributes window, choose Config > Devices > virtual_context > System > Primary Attributes.

Configuration details displays—Allows you to easily troubleshoot device configurations. Many configuration screens now have a Details button at the bottom of the page that shows the status of the configuration. There is an option in the Details popup window that allows you to do a side-by-side comparison of status from two consecutive polls.

To access the windows in the ANM GUI that now contain the Details button, do the following:

For virtual server configurations, choose Config > Devices > virtual_context > Load Balancing > Virtual Servers.

For VLAN configurations, choose Config > Devices > virtual_context > Network > VLAN Interfaces.

For real server configurations, choose Config > Devices > virtual_context > Load Balancing > Real Servers.

For server farm configurations, choose Config > Devices > virtual_context > Load Balancing > Server Farms.

Operational status displays of ACE entities—Allows you to display the operational status of ACE VLANs, virtual servers, real servers, and server farms. The status information is polled using SNMP and is displayed with the configuration data in the corresponding window.

To access the operational status displays in the ANM GUI, do the following:

For VLANs, choose Config > Devices > virtual_context > Network > VLAN Interfaces.

For virtual servers, choose Config > Devices > virtual_context > Load Balancing > Virtual Servers.

For real servers, choose Config > Devices > virtual_context > Load Balancing > Real Servers.

For server farms, choose Config > Devices > virtual_context > Load Balancing > Server Farms.

New Features in ANM 3.1

This section describes the new and updated features of ANM 3.1 and includes the following topics:

Integration of ANM with VMware Virtual Data Center Environment

Enhanced User Role Configurations

Integration of ANM with VMware Virtual Data Center Environment

ANM 3.1 includes a plug-in that allows you to integrate ANM with VMware vCenter Server, which is a third-party product for creating and managing virtual data centers. Using VMware vSphere Client, you can access ANM functionality and manage the ACE real servers that provide load-balancing services for the virtual machines in your virtual data center.

For more information, see Appendix B, "Using ANM With Virtual Data Centers," in the User Guide for the Cisco Application Networking Manager 3.1 at:

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/application_networking_manager/3.1/user/guide/UG_vdatacenter.html

Enhanced User Role Configurations

ANM 3.1 allows greater flexibility when creating user roles. Before ANM 3.1, the operating privilege that you assigned to a parent task was assigned to the subordinates and could not be changed. Using ANM3.1, you can assign a different operating privilege to the subordinates if needed; however, you can only assign an operating privilege that is greater than or equal to the operating privilege assigned to the parent task.

For more information, see the "Creating User Roles" section in the User Guide for the Cisco Application Networking Manager 3.1 at:

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/application_networking_manager/3.1/user/guide/UG_admin.html#wp1053865

Supported Devices and Software

For information on Cisco devices supported by ANM, see the Supported Devices Table for the Cisco Application Networking Manager 3.x located at:

http://www.cisco.com/en/US/products/ps6904/products_device_support_tables_list.html

ANM Product Documentation Set

In addition to this release note, the ANM documentation set includes the following publications. You can access the ANM documentation on www.cisco.com at

http://www.cisco.com/en/US/products/ps6904/tsd_products_support_series_home.html

Installation Guide for the Cisco Application Networking Manager 3.x—Includes complete installation and configuration information for the ANM 3.x software.

User Guide for the Cisco Application Networking Manager 3.x—Includes complete information about ANM functionality and detailed procedures for its use. Contains all of the information found in online help. Available either on cisco.com or from the ANM online help.

Context-sensitive online help—Includes help topics for all pages in the UI (also provides access to PDFs of the user guide). Select an option from the ANM GUI, and click Help.

Supported Devices Table for the Cisco Application Networking Manager 3.x—Includes complete supported device and firmware versions for ANM 3.x.

Supplemental License Agreement for the Cisco Application Networking Manager—Describes licensing limitations and restrictions.

Installing the ANM 3.x Software

For complete instructions on how to install your ANM 3.x software, see the Installation Guide for the Cisco Application Networking Manager 3.x. It provides step-by-step directions for installing and for upgrading the ANM software.


Note Your ANM server must be running Red Hat Enterprise Linux (RHEL) 5 to support ANM 3.x. If your server is currently running Red Hat Enterprise Linux (RHEL) 4 and an earlier version of ANM, you must upgrade to RHEL 5 before you upgrade to ANM 3.x. The ANM installation process prevents you from installing ANM 3.x on a server running RHEL 4.


Depending on the version of ANM software that you are installing (3.0, 3.1, or 3.2), click one of the links below to access the appropriate ANM installation guide:

Installation Guide for Cisco Application Networking Manager 3.0:

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/application_networking_manager/3.0/installation/guide/InstallGuide.html

Installation Guide for Cisco Application Networking Manager 3.2/3.1:

http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/application_networking_manager/3.1/installation/guide/InstallGuide.html

ANM Operating Considerations

Assigning Names to ACE Objects

When naming ACE objects (such as a real server, virtual server, parameter map, class map, health probe, and so on), use a string of typical length 1- 64 characters, with no spaces. ANM supports strings that include alphanumeric characters (a-z, A-Z, 0-9) and the special characters underscore (_), hyphen (-), dot (.), and asterisk (*) only.

If you are using ANM with an ACE module or ACE appliance and you configure a named object at the ACE CLI, keep in mind that ANM does not support all special characters that the ACE CLI allows you to use when configuring a named object. If you use special characters that ANM does not support, you may not be able to import or manage the ACE using ANM.

Using Homepage

When upgrading from a release that is earlier than ANM 3.0, if you had previously configured the First menu option from Admin > RBAC > Users, after you complete your upgrade to ANM 3.x, the First menu default Login page will be automatically reset to Homepage. Beginning with ANM 3.0, the First menu option has been replaced by the Default login page drop-down list in Homepage.

Homepage is a launching point for quick access to selected areas within ANM. It appears under the Home option menu (Home > Welcome). See Chapter 2, Using Homepage, in the User Guide for Cisco Application Networking Manager 3.x for details.

Using the Firefox Web Browser to Access ANM 3.x

The ANM 3.x client supports use with Firefox 3.5 on Windows XP or Windows Vista. When you use Firefox 3.x to access ANM for the first time, the Firefox web browser displays a warning that the site is untrusted (see Figure 1-1).

Figure 1-1 Firefox 3.5 Untrusted Connection Warning

When Firefox displays this warning, follow the prompts to add a security exception and download the self-signed certificate from the ANM server. After you complete this procedure, Firefox accepts the ANM server as a trusted site both now and during all future login attempts.

Procedure


Step 1 In the This Connection Is Untrusted window, click I Understand the Risks.

Step 2 Click Add Exception to add a security exception to the Firefox web browser.

The Add Security Exception popup window appears identifying the location of the ANM server.

Step 3 In the Add Security Exception popup window, click Get Certificate.

Firefox retrieves the ANM self-signed certificate and the window's Confirm Security Exception button becomes active.

Step 4 Click Confirm Security Exception.

Firefox recognizes the ANM server as a trusted site and the ANM Login window appears.


Software Version ANM 3.2 Resolved and Open Caveats

The following sections contain the resolved and open caveats in ANM software version 3.2:

Software Version 3.2 Resolved Caveats

Software Version 3.2 Open Caveats

Software Version 3.2 Resolved Caveats

Table 1 lists the resolved caveats that apply to ANM software version 3.2.

Table 1 Resolved Caveats in Software Version 3.2 

Bug ID
Summary
Explanation

CSCta74908

Admin VC is not listed in the available items list of building block tag.

Admin VC is not listed in the available items list of the building block tag.

CSCtf57213

Activate/suspend rserver might trigger auth CLI sync.

Whenever you activate or suspend a large number of real or virtual servers from the Operations screens belonging to different devices. It takes a long time for the screen to respond as the CLI syncs are triggered.

Workaround: None.

CSCtf79254

Monitoring Dashboard displays Operational status as unavailable.

Monitoring Dashboard reports the Operational stats for all entities (real server, virtual server, probes and so on) as unavailable, even though these statistics are available when queried at the context level in the corresponding monitoring views.

Workaround: Delete the cat6k chassis and re-add a new one, the previously unused name/sequence of strings and re-import the corresponding ACE modules and the issue should be resolved.

CSCtf94141

ANM does not display any error messages when it fails to activate or suspend a server on the ACE.

ANM does not display any error messages when it fails to activate or suspend a server on the ACE, because of the missing user- defined Admin privileges on the ACE.

CSCtf79806

SSL cert expiration alarms not generated on non-admin contexts.

ANM does not generate certificate expiration alarms for certificates that belong to non-admin contexts.

Workaround: Manual on-demand polling could trigger the certificate expiration evaluation and trigger an alarm generation, but otherwise no real workaround is available.

CSCtg09285

ANM overall discovery timeout and individual CLI timeout is not configurable.

ANM cannot discover a cat6k chassis, because the show run response was slow. Hence ANM reports a discovery timeout exception. Cat6k has very slow response for a show run request using Telnet or SSH.

Workaround: None.

CSCtg12246

ANM does not apply management settings from the building blocks to ACE in some cases.

If you deploy a building block from the Virtual Context Configuration window using existing settings on the window and if you try to deploy some of the same settings from a building block, the settings will not be applied because the same settings from the Virtual Context Configuration windows will be re-applied after the building block is deployed.

Workaround:

1. Deploy the building block configurations from the Global > Building Blocks > Primary Attributes window instead. This workaround is only valid for contexts other than the Admin context.

2. Apply the configuration manually or deploy the config from the ANM from the regular configuration window and not from the building blocks.

CSCtg12787

SSL Key import does not show the imported key in ANM GUI.

Key imported through ANM GUI does not show up on the ANM GUI. Although the key is imported successfully into the ACE, it does not show up the ANM GUI keys listing. This condition occurs only when the number of certs in the context is greater than 50.

Workaround: Perform a manual synchronization of the context after the key is imported. The missing key will show up fine in the ANM GUI.

CSCtg20203

Password change for a chassis deletes the username in ANM.

If you change the password for a chassis using Config > Devices > Device Management - Update Password button deletes the username in ANM. ANM can no longer access the chassis.

Workaround: Delete and reimport the chassis with the same name.

CSCtg30437

Any probe with a '/' or '\' in the probe name is not displayed under the ANM monitoring page for probes.

Any probe with a '/' or '\' in the probe name is not displayed under the ANM Monitoring page for probes. The same probe is correctly displayed in the ANM configuration page under 'Health Monitoring'.

Workaround: Do not use '/' or '\' in the probe name.

CSCtg35841

Some real servers may not be activated or suspended if a large number of real servers are selected on CSM using SSH.

The real server will not be activated or suspended if a large number of real servers are selected on a CSM using SSH.

Workaround: Use telnet or activate or suspend with the smaller set of unfinished real server.

CSCtg38174

ANM cannot import the catalyst switch if VRF instance name contains "/".

ANM will not import a catalyst chassis if a VRF instance has a name that contains a forward slash (/).

Workaround: Use the VRF instance without a forward slash (/).

CSCtg50788

The maximum size of the Syslog X_LOG database should be trimmed.

After login, ANM becomes very slow to display the initial user page, while all other pages come up fast. ANM receives a large number of syslog messages (more than 1,000,000 per day) and the mysqld process runs at 100% during login.

Workaround: None.

CSCtg74097

ANM allows a duplicate mechanism to create a role with a space in it.

When a role is duplicated, using the Clone button, if the original name had spaces, the new name is allowed to have spaces with no validation. But trying to delete the role gives an exception and the system does not delete the role. A new role with a valid name needs to be created first, so that the 'Clone' button shows up. Workaround: None.

CSCtg78906

Monitoring fails when device is re-added with same name but a different IP.

ANM monitoring appears to fail and the operational state does not show up on the Operations page, even though SNMP polling is successful. This could occur if a device was deleted from ANM and re-added with a new IP address and same name. The backend monitoring cache still pulls the old IP address and hence all the data for this new name is now incorrect.

Workaround: If you ever re-add a different IP address of a device with the same name in ANM, you need to restart ANM for the monitoring cache to be cleared.

ANM can be restarted as follows:

/opt/CSCOanm/bin/anm-tool restart

CSCtg91302

Historical Data Purging does not clean up the raw data in some instances.

Historical Data Purging does not clean up the raw data and hence the MYSQL file is turning up very large.

Workaround: Perform a backup of the ANM system.

CSCth02416

Cannot find the redirect rule after the memory upgrade and reboot.

You cannot log in to the ANM on https/443 after memory upgrade, while 10443 is listening.

Workaround: Manually adding the redirect rules on CLI as shown below:

iptables -t nat -A PREROUTING -p tcp --dport 80 -j REDIRECT --to-port 8980

iptables -t nat -A PREROUTING -p tcp --dport 443 -j REDIRECT --to-port 10443

iptables -t nat -A PREROUTING -p udp --dport 162 -j REDIRECT --to-port 6120

CSCth25682

Operations activates only ACE active HA peer when autosync disabled.

Only Active ACE is updated when an activate/suspend is performed on the operations pages, autosync is disabled, and the context is in Stby_Hot.

Workaround: The Configuration page can be used to update the state.

CSCth29225

Domain Edit: Search does not return results in IE for large inventory.

When you use Internet Explorer, the search in Domain Edit window seems to hang for a large inventory and no results are returned. For example, ~18K servers in CSS devices.

Workaround: Use Firefox browser.

CSCth29362

Domain Edit screen does not handle large data sets gracefully.

When you create a domain with many domain objects in RBAC > Domain table, the GUI response time to create a domain or edit a domain with large number of domain objects is very slow.

Workaround: None.

CSCth63366

CSS CLI sync failure causes config data loss.

When performing CLI Sync for CSS device and if the operation fails for some reason, ANM will lose the old CSS configuration. ANM fails to import new CSS configuration during the CLI Sync operation, for example, authentication error and connectivity problem.

Workaround: Find out the reason for the CLI Sync failure (like authentication error or connectivity error), fix the problem and do another CLI Sync or remove the CSS device and reimport into ANM again.

CSCth63401

(duplicate bug: CSCth68600)

CSM CLI sync causes erroneous config data

When a VIP or Port is changed on the Vserver and the CSM CLI is synced up to ANM, duplicate CSM Virtual Server entries show up in ANM UI.

Workaround: Delete and re-add the CSM within ANM.

CSCth81192

GSS CLI sync failure impacts the management of other GSS devices.

Whenever ANM has a CLI synchronization failure to a GSS, operational access to all GSS are affected. Both GSS VIP Answers and GSS DNS Rules on the Operations page become empty. Also it displays a JAVA error when you try to view the answers/rules assigned in a domain.

Workaround: Delete the GSS which has CLI synchronization problem.


Software Version 3.2 Open Caveats

Table 2 lists the open caveats that apply to ANM software version 3.2.

Table 2 Open Caveats in Software Version 3.2 

Bug ID
Summary
Explanation and Workarounds

CSCsr75526 (device bug: CSCsu51832)

Config: Cannot edit Expect Status code for health probe.

If you edit a health probe and change the Expect Status Code to a new value or a new range, ANM instructs you that the new values overlap the existing ones and does not remove the old values before adding the new values. Workaround: Delete the existing Min. Expect Status Code and Max. Expect Status Code values before adding the new values.

CSCsu22694 (device bug: CSCsv35266)

Editing a Layer 4 Payload sticky configuration reports exceptions.

When a Layer 4 Payload sticky configuration is edited within ANM, if the "response sticky" option is removed from that sticky configuration, then removing some other sticky options such as offset, length, or timeout, may report exceptions. This condition should not occur. If it does occur, ANM becomes out-of-sync with the CLI and you will need to do a manual synchronization to recover.

Workaround: Synchronize the context in which this exception occurs so that ANM has the updated CLI from the device context, and then proceed with the edits.

CSCsu46598
CSCsx51244
(device bug: CSCsu67729

Modifying a port for a backup server adds new instances of the backup server.

Each time that you modify the port for the backup server under the server farm, ANM creates a new instance of the backup server instead of updating the existing one. These instances do not show up in the Real Server table under the server farm. This condition causes ANM to go out of synchronization with the device configuration. In addition, if you delete the primary server from the server farm, the backup servers do not get deleted. This condition is caused by the ACE known problem CSCsu67729.

Workaround: Do a CLI synchronization on the virtual context. Before editing the port for the backup server, delete the backup server under the server farm.

CSCsu51106

The real server and backup server port for the server farm should have a default value.

The real server and backup server port fields under the server farm should be initialized with default values for the correct server farm type. Currently, only the primary real server port is initialized with a default value of 0. According to the CLI, the minimum is 1. In addition, if the server farm type is Redirect, both the primary and backup server ports must be 0.

Workaround: None. However, Port 0 on ANM indicates that the real server is configured to take "any" port, and ANM will not send data port 0 while generating the CLI.

CSCsu76450

The action list name field allows special characters.

The Action list name field on the ACE allows special characters, for example, "(!,@,$,%,&)" but ANM does not allow them. If special characters have been used in the CLI, ANM will discover them, but you cannot create them within ANM.

Workaround: Do not use the special characters in the Action list name.

CSCsu85936

The UI does not refresh to display a new class map from the reference table.

When you do the following: add a Virtual Server with HTTP as its protocol, select L7 Load Balancing, add a new rule with the match condition type "class-map", click on the "+" icon to add a new class map, and click the Close button in the Class Map window, the virtual server screen does not refresh to display the new class map. Workaround: Exit out of the Edit screen and return.

CSCsv40714

CSS/CSM: The operations state column of the VIP on the CSS and CSM should be N/A.

The CSS and CSM Virtual Server Operational state should appear as "N/A" because this column does not apply for these devices. Instead it is empty. This condition happens each time. Workaround: None.

CSCsv40734

The message should be refined so that it does not look like an exception.

Errors on the Operations pages have the string "Exception" even when errors from the device are being presented to the user. This might give the user the impression that the issue is more severe than it is. This problem occurs whenever an error occurs. For example, this problem occurs when a device is unreachable, or active CSS Content Rules are being activated. Workaround: None.

CSCsv99351

If a mount point has a space in its name, the disk usage reporting code fails to deal with it correctly.

If a mount point has a space in its name, the disk usage reporting code fails to deal with it correctly and throws an exception. Workaround: Change the mount point to ensure that there are no spaces in it. This may not be possible in all circumstances; however, if the server is used as a dedicated ANM server as intended, it should be possible.

CSCsx61268

The netmask field of the stickiness page is showing incorrect values.

The Netmask field of the Stickiness page is showing values of the cookie name, sticky type, or header name for sticky types where this netmask field is not applicable. Workaround: None.

CSCsy87577

ANM GUI—Redundant CSS pair—HA VRRP status does not show up correctly.

When you manage CSS redundant pairs, high availability information is missing. When you pair two CSS devices together using the redundant device feature, the System View page (Monitor > Devices > System View) displays high availability information that does not include the VRRP states. In this case, the page displays "INIT" and other default information. Workaround: None.

CSCsz94062

Expanded drawer/device tree cannot be closed when using Firefox 3.

When you use the Firefox 3 browser and expand a drawer/device, you cannot close it. Workaround: Use Internet Explorer 6 or 7 for a browser.

CSCtd26323

Perf: A "Transform error=cuesXpath is not defined" error message displays on ANM.

When the ANM GUI is transitioning between some pages, a popup window sometimes appears that contains the error message "Transform error=cuesXpath is not defined" or some other "cuesXpath" error message. This error message, which is triggered by the backend GUI model code, is harmless and is to be ignored. Workaround: Click OK to close the popup window and continue using the ANM GUI.

CSCtd61405

Mismatch between the numbers that display in the monitor dashboard and the launched views.

When you go from the dashboard window and to a monitor view that the dashboard launches, the number of entities (real servers, VLANs, and so on) shown in the launched monitor view can be less than the number shown in the dashboard. The reason for this discrepancy is that the dashboard obtains its entity counts from the configuration information of an imported virtual context; however, the launched monitor view shows only the SNMP-based data of the polled entities. If polling is disabled or fails for a virtual context, the dashboard count and the count shown in the launched monitor view will not match. Workaround: None.

CSCtf20628

ANM plugin: SLB Tab: property of tab: that request tunneled through local proxy

In some rare cases, in webplugin for vsphere, the requests to ANM are tunneled through a local proxy on the client machine. This can cause problems with timely refresh of the plugin screens. This appears to be an erratic and uncommon intermittent issue with no clear cause. Workaround: None


Software Version ANM 3.1 Resolved and Open Caveats

The following sections contain the resolved and open caveats in ANM software version 3.1:

Software Version 3.1 Resolved Caveats

Software Version 3.1 Open Caveats

Software Version 3.1 Resolved Caveats

Table 3 lists the resolved caveats that apply to ANM software version 3.1.

Table 3 Resolved Caveats in Software Version 3.1 

Bug ID
Summary
Explanation

CSCtc85284

ANM issues java error device: java.net.SocketTimeoutException: Readtimed.

When you configure ANM for SSH when communicating with a CSS, ANM may issue the following java error when you attempt to suspend the service on the CSS:

Device: java.net.SocketTimeoutException: Readtimed out

Workaround: Reconfigure ANM to use Telnet to communicate with the CSS instead of SSH.

CSCtd70830

Guided Setup tab does not respect RBAC setting.

When a user without configuration privileges logs in to ANM, the Config > Guided Setup tab, which should be hidden from them, appears. Workaround: None.

CSCtd94658

Need to discover Cat6k switchport interface with subinterface defined.

When a sub-interface is defined on a switchport, ANM discovery of the Cat6k chassis fails and issues the following error message:

Device discovery failed: Exception occured for model:VlanModel

Exception occured for model:InterfaceModel

com.cisco.nm.dice.pkgs.features.interfaces.dmL2Trunk cannot be cast to com.cisco.nm.dice.pkgs.features.interfaces.dm.RoutedPort

All parent interfaces of sub-interfaces are assumed to be routed and because this requirement is not true in newer SUP releases, ANM reports an error message and cannot import. Workaround: Remove the offending lines of sub-interface configuration from the Cat6k chassis, import the chassis into ANM, and then add these sub-interface configurations once again to the Cat6k chassis. Because ANM does not perform any periodic automatic synchronizations with the Cat6k configuration, no future discovery errors occur unless you perform a manual synchronization with a Cat6k configuration that contains the sub-interface definition for a switchport.

CSCte08994

Unable to import IOS device with "type tunnel" interface configured.

When you attempt to import an IOS device into ANM that has the following type of configuration:

interface Virtual-Template10 type tunnel

no ip-address

ANM issues the following error message:

Device discovery failed: Exception occured for model:VlanModel

Exception occured for model:InterfaceModel

java.lang.NullPointerException

Workaround: Remove the two configuration lines shown above, import the IOS device into ANM, and then add the "type tunnel" interface configuration to the IOS device. The error will not occur again unless you manually perform a CLI synchronization on the IOS device. ANM does not perform automatic CLI synchronization on an IOS device.

CSCte25910

After upgrading to ANM 3.0, some threshold group settings report an error.

After upgrading to ANM 3.0, ANM cannot create threshold groups that contain the following attributes: Virtual Server Current Connections, Virtual Server Operational State, and Probe Health. When a threshold group contains these attributes, ANM issues the following error message:

Cannot find the referenced entry for the entered data


Note This issue occurs for ANM 3.0 upgrades only. It does not occur after a fresh install of ANM 3.0.


Workaround: If the ANM 2.x backup contains threshold groups, restarting ANM resolves the issue. To restart ANM, see the following URL: http://www.cisco.com/en/US/docs/app_ntwk_services/data_center_app_services/application_networking_manager/3.0/installation/guide/InstallGuide.pdf

If the ANM 2.x backup does not contain any threshold groups, we recommend that you create at least one threshold group on the ANM 2.x system and generate a new backup to be used for the ANM 3.0 upgrade. Also, after the upgrade, we recommend that you perform a restart of ANM as referenced above.

CSCte39384

ANM - Audit logs record incorrect User and Client IP.

When more than one user is logged in to ANM and making changes to any of the devices, the ANM audit logs may record incorrect values in the User and Client IP columns for some of the log entries.

Workaround: Allow only one user to be logged in at a time.

CSCte68130

Suspend and Clear connection generates an error.

When you suspend and clear a connection for a real server, ANM issues the following error message:

Failed to send request to device: CLI Command: configure terminal, reason: Configuration mode is currently disabled


Note This issue does not occur in ANM 2.1(0).


Workaround: None.

CSCte84274

Error in VC sync up, error in Virtual transactions in ANM.

When you create a new context using the ACE CLI and ANM does a context-level CLI synchronization, ANM issues the following error message:

Error in VC syncup,Error in Virtual transactions

This issue occurs with every context-level CLI synchronization.

Workaround: Perform the CLI synchronization from the ACE module/appliance level.

CSCte98520

Real server view page loading very slow and has missing data.

When ANM has to monitor over 2000 real servers, the Real Servers monitoring view at the All Devices, Group, and device levels take a long time to load. Also, some data might be missing on the launched page.

Workaround: Use the context level listing of the Real Servers monitoring view because this level shows the correct information and does not take as long to load.


Software Version 3.1 Open Caveats

Table 4 lists the open caveats that apply to ANM software version 3.1.

Table 4 Open Caveats in Software Version 3.1 

Bug ID
Summary
Explanation and Workarounds

CSCsr75526 (device bug: CSCsu51832)

Config: Cannot edit Expect Status code for health probe.

If you edit a health probe and change the Expect Status Code to a new value or a new range, ANM instructs you that the new values overlap the existing ones and does not remove the old values before adding the new values. Workaround: Delete the existing Min. Expect Status Code and Max. Expect Status Code values before adding the new values.

CSCsu22694

Editing a Layer 4 Payload sticky configuration reports exceptions.

When a Layer 4 Payload sticky configuration is edited within ANM, if the "response sticky" option is removed from that sticky configuration, then removing some other sticky options such as offset, length, or timeout, may report exceptions. This condition should not occur. If it does occur, ANM becomes out-of-sync with the CLI and you will need to do a manual synchronization to recover.

Workaround: Synchronize the context in which this exception occurs so that ANM has the updated CLI from the device context, and then proceed with the edits.

CSCsu46598
CSCsx51244
(device bug: CSCsu67729)

Modifying a port for a backup server adds new instances of the backup server.

Each time that you modify the port for the backup server under the server farm, ANM creates a new instance of the backup server instead of updating the existing one. These instances do not show up in the Real Server table under the server farm. This condition causes ANM to go out of synchronization with the device configuration. In addition, if you delete the primary server from the server farm, the backup servers do not get deleted. This condition is caused by the ACE known problem CSCsu67729.

Workaround: Do a CLI synchronization on the virtual context. Before editing the port for the backup server, delete the backup server under the server farm.

CSCsu51106

The real server and backup server port for the server farm should have a default value.

The real server and backup server port fields under the server farm should be initialized with default values for the correct server farm type. Currently, only the primary real server port is initialized with a default value of 0. According to the CLI, the minimum is 1. In addition, if the server farm type is Redirect, both the primary and backup server ports must be 0.

Workaround: None. However, Port 0 on ANM indicates that the real server is configured to take "any" port, and ANM will not send data port 0 while generating the CLI.

CSCsu76450

The action list name field allows special characters.

The Action list name field on the ACE allows special characters, for example, "(!!!, @@@@)" but ANM does not allow them. If special characters have been used in the CLI, ANM will discover them, but you cannot create them within ANM.

Workaround: Do not use the special characters in the Action list name.

CSCsu85936

The UI does not refresh to display a new class map from the reference table.

When you do the following: add a Virtual Server with HTTP as its protocol, select L7 Load Balancing, add a new rule with the match condition type "class-map", click on the "+" icon to add a new class map, and click the Close button in the Class Map window, the virtual server screen does not refresh to display the new class map. Workaround: Exit out of the Edit screen and return.

CSCsv40714

CSS/CSM: The operations state column of the VIP on the CSS and CSM should be N/A.

The CSS and CSM Virtual Server Operational state should appear as "N/A" because this column does not apply for these devices. Instead it is empty. This condition happens each time. Workaround: None.

CSCsv40734

The message should be refined so that it does not look like an exception.

Errors on the Operations pages have the string "Exception" even when errors from the device are being presented to the user. This might give the user the impression that the issue is more severe than it is. This problem occurs whenever an error occurs. For example, this problem occurs when a device is unreachable, or active CSS Content Rules are being activated. Workaround: None.

CSCsv43603

ANM cannot import GSS if a user with a different password is in the GSS GUI and the GSS CLI.

ANM will not be able to import a GSS if a GSS user configured with different password is in both the GSS GUI and the GSS CLI. Workaround: The GSS user should be configured with the same password in both the GSS GUI and GSS CLI.

CSCsv99351

If a mount point has a space in its name, the disk usage reporting code fails to deal with it correctly.

If a mount point has a space in its name, the disk usage reporting code fails to deal with it correctly and throws an exception. Workaround: Change the mount point to ensure that there are no spaces in it. This may not be possible in all circumstances; however, if the server is used as a dedicated ANM server as intended, it should be possible.

CSCsx61268

The netmask field of the stickiness page is showing incorrect values.

The Netmask field of the Stickiness page is showing values of the cookie name, sticky type, or header name for sticky types where this netmask field is not applicable. Workaround: None.

CSCsy87577

ANM GUI—Redundant CSS pair—HA VRRP status does not show up correctly.

When you manage CSS redundant pairs, high availability information is missing. When you pair two CSS devices together using the redundant device feature, the System View page (Monitor > Devices > System View) displays high availability information that does not include the VRRP states. In this case, the page displays "INIT" and other default information. Workaround: None.

CSCsz94062

Expanded drawer/device tree cannot be closed when using Firefox 3.

When you use the Firefox 3 browser and expand a drawer/device, you cannot close it. Workaround: Use Internet Explorer 6 or 7 for a browser.

CSCtd26323

Perf: A "Transform error=cuesXpath is not defined" error message displays on ANM.

When the ANM GUI is transitioning between some pages, a popup window sometimes appears that contains the error message "Transform error=cuesXpath is not defined" or some other "cuesXpath" error message. This error message, which is triggered by the backend GUI model code, is harmless and is to be ignored. Workaround: Click OK to close the popup window and continue using the ANM GUI.

CSCtd61405

Mismatch between the numbers that display in the monitor dashboard and the launched views.

When you go from the dashboard window and to a monitor view that the dashboard launches, the number of entities (real servers, VLANs, and so on) shown in the launched monitor view can be less than the number shown in the dashboard. The reason for this discrepancy is that the dashboard obtains its entity counts from the configuration information of an imported virtual context; however, the launched monitor view shows only the SNMP-based data of the polled entities. If polling is disabled or fails for a virtual context, the dashboard count and the count shown in the launched monitor view will not match. Workaround: None.

CSCtf20628

ANM plugin: SLB Tab: property of tab: that request tunneled through local proxy

When accessing ANM from a VMware vSphere Client and you right-click the Cisco ACE SLB tab to choose the Properties menu options, the Properties pop-up window displays the following incorrect path to the ANM server:

http://127.0.0.1:[someport number}/index.vm?.

This issue may lead to refresh issues with the ANM plug-in. Workaround: None

CSCtf79806

SSL cert expiration alarms not generated on non-admin contexts.

ANM does not generate certificate expiration alarms for certificates that belong to non-admin contexts.

Workaround: Manual on-demand polling could trigger the certificate expiration evaluation and trigger an alarm generation, but otherwise no real workaround is available.


Software Version ANM 3.0 Resolved and Open Caveats

The following sections contain the resolved and open caveats in ANM software version 3.0:

Software Version 3.0 Resolved Caveats

Software Version 3.0 Open Caveats

Software Version 3.0 Resolved Caveats

Table 5 lists the resolved caveats that apply to ANM software version 3.0.

Table 5 Resolved Caveats in Software Version 3.0 

Bug ID
Summary
Explanation

CSCsv40484

Restore: Restoring data on ANM 2.0 shows the operations state column as blank.

The CSM and CSS Polling is not automatically restarting after an ANM stop/start. This problem occurs after an ANM restart.

Workaround: Synchronize from the CLI for each device that is not polling.

CSCsw15103

Chassis: Cannot delete the chassis from ANM after an automation run.

After you attempt to delete a chassis from ANM, the following error appears on every load of a page:

Internal Error: cannot find 
/device/<chassis-name>/module/trinity-<ace module serial 
number> 

For example:

Internal Error: cannot find 
/device/spiff/module/trinity-SAD094701MV" 

Workaround: Restart the ANM services to clear this condition. See the User Guide for the Cisco Application Networking Manager 2.2, Chapter 10, Configuring High Availability, the "CLI Commands for High Availability Processes" section for information about restarting ANM services.

CSCsz82871

ANM: Config > Operations Saved filters cannot be deleted.

Filters created and saved using the Filter button on a Config > Operations screen cannot be deleted from ANM.

CSCta85637

ANM: vserver IDs are not generated consistently with multiple match entries.

When virtual servers do not quite fall into the classic ANM definition of a virtual server, ANM is unable to manage them. When a configuration contains many virtual servers that contain two virtual-address match lines, ANM is inconsistent about which match line to use for the generation of the key that is placed into the domain. This condition results in virtual servers disappearing from the Domain edit window over time.

CSCtb13423

When a context name begins with a digit, it does not work as expected in the Primary Attributes page.

When there are user context names configured on the ACE that are alphabetically less than the Admin context (for example 1AHouse), then all of the context names are assigned with the same resource class name and the Resource Class combo box has only one Resource name. This issue is seen in the Primary Attributes window.

CSCtb20971

CSM: CLI synchronization of out of band removal of objects not working.

When you use the CLI for out of band removal of real and virtual servers, ANM still shows the real and virtual servers after they have been removed and a CLI synchronization has been performed.

CSCtb75318

ANM showing alarm source ID (srcid) as null.

When you try to set up a threshold group on a CSM device, ANM shows the Source ID column in the Monitor > Alarm Notifications > Alarms window as a null value.

CSCtb79608

ACL edits of an object group do not show up on the ACE.

When you edit the Protocol/Source Network/Destination Network Object Groups of an existing ACL entry after you import and synchronize the context to ANM, the ACL edits to the object group made in ANM do not show up in the ACE after synchronization; however, ANM shows the changes.

CSCtb89475

SSH key and certificates are not matched due to an unavailable ACE SSH session.

When all the SSL certs/keys in a context match up with each other and are defined in SSL proxies, then the SSH session that was set up between ANM and the ACE to validate the cert/key matching does not close. Because the validation sessions do not close, eventually the session limit is reached and no more SSH connections for cert/key verification can be made.

SSL certs/key matching is not displayed on the ANM GUI.

CSCtc36967

The agent_ip address populated in ANM alarms maybe incorrect.

When ANM is configured in HA and threshold alarms are generated from the ANM HA peer, the agent_ip in the alarm generated by ANM for threshold crossing has the ANM heartbeat IP address rather than the ANM host IP address.

CSCtc81222

The hacluster/haclient user/group name remains after ANM is uninstalled.

After you uninstall ANM, the hacluster/haclient user/group name remains.

CSCtc85284

ANM experiences a java error device: java.net.SocketTimeoutException: Readtimed.

When ANM is configured to SSH to a CSS, ANM occasionally experiences the following java error when the user attempts to suspend the service on CSS:

Device: java.net.SocketTimeoutException: Readtimed out

CSCtc88060

ANM does not update its displayed version for the ACE-4710 or the CSS1150X.

After you either upgrade or downgrade an ACE-4710 or CSS1150X device, ANM does not update the version displayed in the Monitor > Devices > Device Management window.

CSCtd07249

ANM cannot import all modules in the VSS device.

When the exec prompt timestamp command is used on line vty configuration in VSS device, ANM cannot import all of the modules in the VSS device.

CSCtd10741

Class/Rule in loadbalance policy deployed out of order from ANM to CLI.

When you edit a virtual server configuration and modify the sequence of the rules in the L7 Load Balancing section using the up/down arrows, the change to the order of the rules displays correctly in the GUI but the CLI is not updated. This issue occurs only while editing an existing virtual server configuration; it does not occur when creating a new virtual server configuration.

This issue can also be seen in the advanced Expert mode on the DM for the L7 loadbalance policy map.


Software Version 3.0 Open Caveats

Table 6 lists the open caveats that apply to ANM software version 3.0.

Table 6 Open Caveats in Software Version 3.0 

Bug ID
Summary
Explanation and Workarounds

CSCsr75526 (device bug: CSCsu51832)

Config: Cannot edit Expect Status code for health probe.

If you edit a health probe and change the Expect Status Code to a new value or a new range, ANM instructs you that the new values overlap the existing ones and does not remove the old values before adding the new values. Workaround: Delete the existing Min. Expect Status Code and Max. Expect Status Code values before adding the new values.

CSCsu22694

Editing a Layer 4 Payload sticky configuration reports exceptions.

When a Layer 4 Payload sticky configuration is edited within ANM, if the "response sticky" option is removed from that sticky configuration, then removing some other sticky options such as offset, length, or timeout, may report exceptions. This condition should not occur. If it does occur, ANM becomes out-of-sync with the CLI and you will need to do a manual synchronization to recover.

Workaround: Synchronize the context in which this exception occurs so that ANM has the updated CLI from the device context, and then proceed with the edits.

CSCsu46598
CSCsx51244
(device bug: CSCsu67729

Modifying a port for a backup server adds new instances of the backup server.

Each time that you modify the port for the backup server under the server farm, ANM creates a new instance of the backup server instead of updating the existing one. These instances do not show up in the Real Server table under the server farm. This condition causes ANM to go out of synchronization with the device configuration. In addition, if you delete the primary server from the server farm, the backup servers do not get deleted. This condition is caused by the ACE known problem CSCsu67729.

Workaround: Do a CLI synchronization on the virtual context. Before editing the port for the backup server, delete the backup server under the server farm.

CSCsu51106

The real server and backup server port for the server farm should have a default value.

The real server and backup server port fields under the server farm should be initialized with default values for the correct server farm type. Currently, only the primary real server port is initialized with a default value of 0. According to the CLI, the minimum is 1. In addition, if the server farm type is Redirect, both the primary and backup server ports must be 0.

Workaround: None. However, Port 0 on ANM indicates that the real server is configured to take "any" port, and ANM will not send data port 0 while generating the CLI.

CSCsu76450

The action list name field allows special characters.

The Action list name field on the ACE allows special characters, for example, "(!!!, @@@@)" but ANM does not allow them. If special characters have been used in the CLI, ANM will discover them, but you cannot create them within ANM.

Workaround: Do not use the special characters in the Action list name.

CSCsu85936

The UI does not refresh to display a new class map from the reference table.

When you do the following: add a Virtual Server with HTTP as its protocol, select L7 Load Balancing, add a new rule with the match condition type "class-map", click on the "+" icon to add a new class map, and click the Close button in the Class Map window, the virtual server screen does not refresh to display the new class map. Workaround: Exit out of the Edit screen and return.

CSCsv40714

CSS/CSM: The operations state column of the VIP on the CSS and CSM should be N/A.

The CSS and CSM Virtual Server Operational state should appear as "N/A" because this column does not apply for these devices. Instead it is empty. This condition happens each time. Workaround: None.

CSCsv40734

The message should be refined so that it does not look like an exception.

Errors on the Operations pages have the string "Exception" even when errors from the device are being presented to the user. This might give the user the impression that the issue is more severe than it is. This problem occurs whenever an error occurs. For example, this problem occurs when a device is unreachable, or active CSS Content Rules are being activated. Workaround: None.

CSCsv43603

ANM cannot import GSS if a user with a different password is in the GSS GUI and the GSS CLI.

ANM will not be able to import a GSS if a GSS user configured with different password is in both the GSS GUI and the GSS CLI. Workaround: The GSS user should be configured with the same password in both the GSS GUI and GSS CLI.

CSCsv99351

If a mount point has a space in its name, the disk usage reporting code fails to deal with it correctly.

If a mount point has a space in its name, the disk usage reporting code fails to deal with it correctly and throws an exception. Workaround: Change the mount point to ensure that there are no spaces in it. This may not be possible in all circumstances; however, if the server is used as a dedicated ANM server as intended, it should be possible.

CSCsx61268

The netmask field of the stickiness page is showing incorrect values.

The Netmask field of the Stickiness page is showing values of the cookie name, sticky type, or header name for sticky types where this netmask field is not applicable. Workaround: None.

CSCsy87577

ANM GUI—Redundant CSS pair—HA VRRP status does not show up correctly.

When you manage CSS redundant pairs, high availability information is missing. When you pair two CSS devices together using the redundant device feature, the System View page (Monitor > Devices > System View) displays high availability information that does not include the VRRP states. In this case, the page displays "INIT" and other default information. Workaround: None.

CSCsz94062

Expanded drawer/device tree cannot be closed when using Firefox 3.

When you use the Firefox 3 browser and expand a drawer/device, you cannot close it. Workaround: Use Internet Explorer 6 or 7 for a browser.

CSCtd26323

Perf: A "Transform error=cuesXpath is not defined" error message displays on ANM.

When the ANM GUI is transitioning between some pages, a popup window sometimes appears that contains the error message "Transform error=cuesXpath is not defined" or some other "cuesXpath" error message. This error message, which is triggered by the backend GUI model code, is harmless and is to be ignored. Workaround: Click OK to close the popup window and continue using the ANM GUI.

CSCtd61405

Mismatch between the numbers that display in the monitor dashboard and the launched views.

When you go from the dashboard window and to a monitor view that the dashboard launches, the number of entities (real servers, VLANs, and so on) shown in the launched monitor view can be less than the number shown in the dashboard. The reason for this discrepancy is that the dashboard obtains its entity counts from the configuration information of an imported virtual context; however, the launched monitor view shows only the SNMP-based data of the polled entities. If polling is disabled or fails for a virtual context, the dashboard count and the count shown in the launched monitor view will not match. Workaround: None.


Copyright Notices

Third-party software used under license accompanies the Cisco Application Networking Manager Software, release 3.x. One or more of the following notices may apply in connection with the license and use of such third-party software.

The copyright notices in this document are as follows:

Apache 2.0 License, Version 2.0

Bouncy Castle Copyright Notice

Castor

Common Public License Version 1.0

GNU GENERAL PUBLIC LICENSE

GNU LESSER GENERAL PUBLIC LICENSE

Copyright Statement for JasperReports

Mozilla Public License Version 1.1

Apache 2.0 License, Version 2.0

Apache License
Version 2.0, January 2004
http://www.apache.org/licenses/

TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

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

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

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

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

a. You must give any other recipients of the Work or Derivative Works a copy of this License; and

b. You must cause any modified files to carry prominent notices stating that You changed the files; and

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

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

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

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

7. 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 assume any risks associated with Your exercise of permissions under this License.

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

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

END OF TERMS AND CONDITIONS

APPENDIX: How to apply the Apache License to your work

To apply the Apache License to your work, attach the following boilerplate notice, with the fields enclosed by brackets "[]" replaced with your own identifying information. (Don't include the brackets!) The text should be enclosed in the appropriate comment syntax for the file format. We also recommend that a file or class name and description of purpose be included on the same "printed page" as the copyright notice for easier identification within third-party archives.

Copyright [yyyy] [name of copyright owner] Licensed under the Apache License, Version 2.0 
(the "License"); you may not use this file except in compliance with the License. You may 
obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required 
by applicable law or agreed to in writing, software distributed under the License is 
distributed on an "AS IS" BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either 
express or implied. See the License for the specific language governing permissions and 
limitations under the License. 

Bouncy Castle Copyright Notice

Copyright (c) 2000 The Legion Of The Bouncy Castle (http://www.bouncycastle.org)

Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.

Castor

exolab.org

The code of this project is released under a BSD-like license [license.txt]:

Copyright 2000-2002 (C) Intalio Inc. All Rights Reserved.

Redistribution and use of this software and associated documentation ("Software"), with or without modification, are permitted provided that the following conditions are met:

1. Redistributions of source code must retain copyright statements and notices. Redistributions must also contain a copy of this document.

2. Redistributions in binary form must reproduce the above copyright notice, this list of conditions and the following disclaimer in the documentation and/or other materials provided with the distribution.

3. The name "ExoLab" must not be used to endorse or promote products derived from this Software without prior written permission of Intalio Inc. For written permission, please contact info@exolab.org.

4. Products derived from this Software may not be called "Castor" nor may "Castor" appear in their names without prior written permission of Intalio Inc. Exolab, Castor and Intalio are trademarks of Intalio Inc.

5. Due credit should be given to the ExoLab Project (http://www.exolab.org/).

THIS SOFTWARE IS PROVIDED BY INTALIO AND CONTRIBUTORS ``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 INTALIO 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.

Common Public License Version 1.0

(text)

THE ACCOMPANYING PROGRAM IS PROVIDED UNDER THE TERMS OF THIS COMMON PUBLIC LICENSE ("AGREEMENT"). ANY USE, REPRODUCTION OR DISTRIBUTION OF THE PROGRAM CONSTITUTES RECIPIENT'S ACCEPTANCE OF THIS AGREEMENT.

1. DEFINITIONS

"Contribution" means:

a) in the case of the initial Contributor, the initial code and documentation distributed under this Agreement, and

b) in the case of each subsequent Contributor:

i) changes to the Program, and

ii) additions to the Program;

where such changes and/or additions to the Program originate from and are distributed by that particular Contributor. A Contribution 'originates' from a Contributor if it was added to the Program by such Contributor itself or anyone acting on such Contributor's behalf. Contributions do not include additions to the Program which: (i) are separate modules of software distributed in conjunction with the Program under their own license agreement, and (ii) are not derivative works of the Program.

"Contributor" means any person or entity that distributes the Program.

"Licensed Patents" mean patent claims licensable by a Contributor which are necessarily infringed by the use or sale of its Contribution alone or when combined with the Program.

"Program" means the Contributions distributed in accordance with this Agreement.

"Recipient" means anyone who receives the Program under this Agreement, including all Contributors.

2. GRANT OF RIGHTS

a) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free copyright license to reproduce, prepare derivative works of, publicly display, publicly perform, distribute and sublicense the Contribution of such Contributor, if any, and such derivative works, in source code and object code form.

b) Subject to the terms of this Agreement, each Contributor hereby grants Recipient a non-exclusive, worldwide, royalty-free patent license under Licensed Patents to make, use, sell, offer to sell, import and otherwise transfer the Contribution of such Contributor, if any, in source code and object code form. This patent license shall apply to the combination of the Contribution and the Program if, at the time the Contribution is added by the Contributor, such addition of the Contribution causes such combination to be covered by the Licensed Patents. The patent license shall not apply to any other combinations which include the Contribution. No hardware per se is licensed hereunder.

c) Recipient understands that although each Contributor grants the licenses to its Contributions set forth herein, no assurances are provided by any Contributor that the Program does not infringe the patent or other intellectual property rights of any other entity. Each Contributor disclaims any liability to Recipient for claims brought by any other entity based on infringement of intellectual property rights or otherwise. As a condition to exercising the rights and licenses granted hereunder, each Recipient hereby assumes sole responsibility to secure any other intellectual property rights needed, if any. For example, if a third party patent license is required to allow Recipient to distribute the Program, it is Recipient's responsibility to acquire that license before distributing the Program.

d) Each Contributor represents that to its knowledge it has sufficient copyright rights in its Contribution, if any, to grant the copyright license set forth in this Agreement.

3. REQUIREMENTS

A Contributor may choose to distribute the Program in object code form under its own license agreement, provided that:

a) it complies with the terms and conditions of this Agreement; and

b) its license agreement:

i) effectively disclaims on behalf of all Contributors all warranties and conditions, express and implied, including warranties or conditions of title and non-infringement, and implied warranties or conditions of merchantability and fitness for a particular purpose;

ii) effectively excludes on behalf of all Contributors all liability for damages, including direct, indirect, special, incidental and consequential damages, such as lost profits;

iii) states that any provisions which differ from this Agreement are offered by that Contributor alone and not by any other party; and

iv) states that source code for the Program is available from such Contributor, and informs licensees how to obtain it in a reasonable manner on or through a medium customarily used for software exchange.

When the Program is made available in source code form:

a) it must be made available under this Agreement; and

b) a copy of this Agreement must be included with each copy of the Program.

Contributors may not remove or alter any copyright notices contained within the Program.

Each Contributor must identify itself as the originator of its Contribution, if any, in a manner that reasonably allows subsequent Recipients to identify the originator of the Contribution.

4. COMMERCIAL DISTRIBUTION

Commercial distributors of software may accept certain responsibilities with respect to end users, business partners and the like. While this license is intended to facilitate the commercial use of the Program, the Contributor who includes the Program in a commercial product offering should do so in a manner which does not create potential liability for other Contributors. Therefore, if a Contributor includes the Program in a commercial product offering, such Contributor ("Commercial Contributor") hereby agrees to defend and indemnify every other Contributor ("Indemnified Contributor") against any losses, damages and costs (collectively "Losses") arising from claims, lawsuits and other legal actions brought by a third party against the Indemnified Contributor to the extent caused by the acts or omissions of such Commercial Contributor in connection with its distribution of the Program in a commercial product offering. The obligations in this section do not apply to any claims or Losses relating to any actual or alleged intellectual property infringement. In order to qualify, an Indemnified Contributor must: a) promptly notify the Commercial Contributor in writing of such claim, and b) allow the Commercial Contributor to control, and cooperate with the Commercial Contributor in, the defense and any related settlement negotiations. The Indemnified Contributor may participate in any such claim at its own expense.

For example, a Contributor might include the Program in a commercial product offering, Product X. That Contributor is then a Commercial Contributor. If that Commercial Contributor then makes performance claims, or offers warranties related to Product X, those performance claims and warranties are such Commercial Contributor's responsibility alone. Under this section, the Commercial Contributor would have to defend claims against the other Contributors related to those performance claims and warranties, and if a court requires any other Contributor to pay any damages as a result, the Commercial Contributor must pay those damages.

5. NO WARRANTY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, THE PROGRAM IS PROVIDED 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. Each Recipient is solely responsible for determining the appropriateness of using and distributing the Program and assumes all risks associated with its exercise of rights under this Agreement, including but not limited to the risks and costs of program errors, compliance with applicable laws, damage to or loss of data, programs or equipment, and unavailability or interruption of operations.

6. DISCLAIMER OF LIABILITY

EXCEPT AS EXPRESSLY SET FORTH IN THIS AGREEMENT, NEITHER RECIPIENT NOR ANY CONTRIBUTORS SHALL HAVE ANY LIABILITY FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL DAMAGES (INCLUDING WITHOUT LIMITATION LOST PROFITS), 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 OR DISTRIBUTION OF THE PROGRAM OR THE EXERCISE OF ANY RIGHTS GRANTED HEREUNDER, EVEN IF ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

7. GENERAL

If any provision of this Agreement is invalid or unenforceable under applicable law, it shall not affect the validity or enforceability of the remainder of the terms of this Agreement, and without further action by the parties hereto, such provision shall be reformed to the minimum extent necessary to make such provision valid and enforceable.

If Recipient institutes patent litigation against a Contributor with respect to a patent applicable to software (including a cross-claim or counterclaim in a lawsuit), then any patent licenses granted by that Contributor to such Recipient under this Agreement shall terminate as of the date such litigation is filed. In addition, if Recipient institutes patent litigation against any entity (including a cross-claim or counterclaim in a lawsuit) alleging that the Program itself (excluding combinations of the Program with other software or hardware) infringes such Recipient's patent(s), then such Recipient's rights granted under Section 2(b) shall terminate as of the date such litigation is filed.

All Recipient's rights under this Agreement shall terminate if it fails to comply with any of the material terms or conditions of this Agreement and does not cure such failure in a reasonable period of time after becoming aware of such noncompliance. If all Recipient's rights under this Agreement terminate, Recipient agrees to cease use and distribution of the Program as soon as reasonably practicable. However, Recipient's obligations under this Agreement and any licenses granted by Recipient relating to the Program shall continue and survive.

Everyone is permitted to copy and distribute copies of this Agreement, but in order to avoid inconsistency the Agreement is copyrighted and may only be modified in the following manner. The Agreement Steward reserves the right to publish new versions (including revisions) of this Agreement from time to time. No one other than the Agreement Steward has the right to modify this Agreement. IBM is the initial Agreement Steward. IBM may assign the responsibility to serve as the Agreement Steward to a suitable separate entity. Each new version of the Agreement will be given a distinguishing version number. The Program (including Contributions) may always be distributed subject to the version of the Agreement under which it was received. In addition, after a new version of the Agreement is published, Contributor may elect to distribute the Program (including its Contributions) under the new version. Except as expressly stated in Sections 2(a) and 2(b) above, Recipient receives no rights or licenses to the intellectual property of any Contributor under this Agreement, whether expressly, by implication, estoppel or otherwise. All rights in the Program not expressly granted under this Agreement are reserved.

This Agreement is governed by the laws of the State of New York and the intellectual property laws of the United States of America. No party to this Agreement will bring a legal action under this Agreement more than one year after the cause of action arose. Each party waives its rights to a jury trial in any resulting litigation.

Copyright © 2006 by the Open Source Initiative

Technical questions about the website go to Steve M.: webmaster at opensource.org

Policy questions about open source go to the Board of Directors.

The contents of this website are licensed under the Open Software License 2.1 or Academic Free License 2.1

OSI is a registered non-profit with 501(c)(3) status. Donating to OSI is one way to show your support.

GNU GENERAL PUBLIC LICENSE

Version 2, June 1991

Copyright (C) 1989, 1991 Free Software Foundation, Inc.,

51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public License is intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users. This General Public License applies to most of the Free Software Foundation's software and to any other program whose authors commit to using it. (Some other Free Software Foundation software is covered by the GNU Lesser General Public License instead.) You can apply it to
your programs, too.

When we speak of free software, we are referring to freedom, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish), that you receive source code or can get it
if you want it, that you can change the software or use pieces of it in new free programs; and that you know you can do these things.

To protect your rights, we need to make restrictions that forbid anyone to deny you these rights or to ask you to surrender the rights. These restrictions translate to certain responsibilities for you if you distribute copies of the software, or if you modify it.

For example, if you distribute copies of such a program, whether gratis or for a fee, you must give the recipients all the rights that you have. You must make sure that they, too, receive or can get the source code. And you must show them these terms so they know their
rights.

We protect your rights with two steps: (1) copyright the software, and (2) offer you this license which gives you legal permission to copy, distribute and/or modify the software.

Also, for each author's protection and ours, we want to make certain that everyone understands that there is no warranty for this free software. If the software is modified by someone else and passed on, we want its recipients to know that what they have is not the original, so that any problems introduced by others will not reflect on the original authors' reputations.

Finally, any free program is threatened constantly by software patents. We wish to avoid the danger that redistributors of a free program will individually obtain patent licenses, in effect making the program proprietary. To prevent this, we have made it clear that any patent must be licensed for everyone's free use or not licensed at all.

The precise terms and conditions for copying, distribution and modification follow.

GNU GENERAL PUBLIC LICENSE

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License applies to any program or other work which contains a notice placed by the copyright holder saying it may be distributed under the terms of this General Public License. The "Program", below, refers to any such program or work, and a "work based on the Program" means either the Program or any derivative work under copyright law: that is to say, a work containing the Program or a portion of it, either verbatim or with modifications and/or translated into another language. (Hereinafter, translation is included without limitation in the term "modification".) Each licensee is addressed as "you".

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running the Program is not restricted, and the output from the Program is covered only if its contents constitute a work based on the Program (independent of having been made by running the Program). Whether that is true depends on what the Program does.

1. You may copy and distribute verbatim copies of the Program's source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and give any other recipients of the Program a copy of this License along with the Program.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Program or any portion of it, thus forming a work based on the Program, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a) You must cause the modified files to carry prominent notices stating that you changed the files and the date of any change.

b) You must cause any work that you distribute or publish, that in whole or in part contains or is derived from the Program or any part thereof, to be licensed as a whole at no charge to all third parties under the terms of this License.

c) If the modified program normally reads commands interactively when run, you interactive use in the most ordinary way, to print or display an announcement including an appropriate copyright notice and a notice that there is no warranty (or else, saying that you provide a warranty) and that users may redistribute the program under these conditions, and telling the user how to view a copy of this License. (Exception: if the Program itself is interactive but does not normally print such an announcement, your work based on the Program is not required to print an announcement.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Program, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Program, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Program.

In addition, mere aggregation of another work not based on the Program with the Program (or with a work based on the Program) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may copy and distribute the Program (or a work based on it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you also do one of the following:

a) Accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

b) Accompany it with a written offer, valid for at least three years, to give any third party, for a charge no more than your cost of physically performing source distribution, a complete machine-readable copy of the corresponding source code, to be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange; or,

c) Accompany it with the information you received as to the offer to distribute corresponding source code. (This alternative is allowed only for noncommercial distribution and only if you
received the program in object code or executable form with such an offer, in accord with Subsection b above.)

The source code for a work means the preferred form of the work for making modifications to it. For an executable work, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the executable. However, as a special exception, the source code distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

If distribution of executable or object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place counts as distribution of the source code, even though third parties are not compelled to copy the source along with the object code.

4. You may not copy, modify, sublicense, or distribute the Program except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense or distribute the Program is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

5. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Program or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Program (or any work based on the Program), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Program or works based on it.

6. Each time you redistribute the Program (or any work based on the Program), the recipient automatically receives a license from the original licensor to copy, distribute or modify the Program subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties to this License.

7. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Program at all. For example, if a patent license would not permit royalty-free redistribution of the Program by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Program.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system, which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

8. If the distribution and/or use of the Program is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Program under this License
may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

9. The Free Software Foundation may publish revised and/or new versions of the General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Program specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Program does not specify a version number of this License, you may choose any version ever published by the Free Software Foundation.

10. If you wish to incorporate parts of the Program into other free programs whose distribution conditions are different, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

11. BECAUSE THE PROGRAM IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE PROGRAM, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE PROGRAM "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE PROGRAM IS WITH YOU. SHOULD THE PROGRAM PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

12. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR EDISTRIBUTE THE PROGRAM AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE PROGRAM (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE PROGRAM TO OPERATE WITH ANY OTHER PROGRAMS), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

How to Apply These Terms to Your New Programs

If you develop a new program, and you want it to be of the greatest possible use to the public, the best way to achieve this is to make it free software which everyone can redistribute and change under these terms.

To do so, attach the following notices to the program. It is safest to attach them to the start of each source file to most effectively convey the exclusion of warranty; and each file should have at least
the "copyright" line and a pointer to where the full notice is found.

<one line to give the program's name and a brief idea of what it does.>
Copyright (C) <year> <name of author>

This program is free software; you can redistribute it and/or modify it under the terms of the GNU General Public License as published by the Free Software Foundation; either version 2 of the License, or (at your option) any later version.

This program is distributed in the hope that it will be useful, but WITHOUT ANY WARRANTY; without even the implied warranty of MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU General Public License for more details.

You should have received a copy of the GNU General Public License along with this program; if not, write to the Free Software Foundation, Inc., 51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA.

Also add information on how to contact you by electronic and paper mail.

If the program is interactive, make it output a short notice like this when it starts in an interactive mode:

Gnomovision version 69, Copyright (C) year name of author Gnomovision comes with ABSOLUTELY NO WARRANTY; for details type `show w'. This is free software, and you are welcome to redistribute it under certain conditions; type `show c' for details.

The hypothetical commands `show w' and `show c' should show the appropriate parts of the General Public License. Of course, the commands you use may be called something other than `show w' and `show c'; they could even be mouse-clicks or menu items--whatever suits your program.

You should also get your employer (if you work as a programmer) or your school, if any, to sign a "copyright disclaimer" for the program, if necessary. Here is a sample; alter the names:

Yoyodyne, Inc., hereby disclaims all copyright interest in the program `Gnomovision' (which makes passes at compilers) written by James Hacker.

<signature of Ty Coon>, 1 April 1989
Ty Coon, President of Vice

This General Public License does not permit incorporating your program into proprietary programs. If your program is a subroutine library, you may consider it more useful to permit linking proprietary applications with the library. If this is what you want to do, use the GNU Lesser General Public License instead of this License.

GNU LESSER GENERAL PUBLIC LICENSE

Version 2.1, February 1999

Copyright (C) 1991, 1999 Free Software Foundation, Inc.

51 Franklin Street, Fifth Floor, Boston, MA 02110-1301 USA

Everyone is permitted to copy and distribute verbatim copies of this license document, but changing it is not allowed.

[This is the first released version of the Lesser GPL. It also counts as the successor of the GNU Library Public License, version 2, hence the version number 2.1.]

Preamble

The licenses for most software are designed to take away your freedom to share and change it. By contrast, the GNU General Public Licenses are intended to guarantee your freedom to share and change free software--to make sure the software is free for all its users.

This license, the Lesser General Public License, applies to some specially designated software packages--typically libraries--of the Free Software Foundation and other authors who decide to use it. You can use it too, but we suggest you first think carefully about whether this license or the ordinary General Public License is the better strategy to use in any particular case, based on the explanations below.

When we speak of free software, we are referring to freedom of use, not price. Our General Public Licenses are designed to make sure that you have the freedom to distribute copies of free software (and charge for this service if you wish); that you receive source code or can get it if you want it; that you can change the software and use pieces of it in new free programs; and that you are informed that you can do these things.

To protect your rights, we need to make restrictions that forbid distributors to deny you these rights or to ask you to surrender these rights. These restrictions translate to certain responsibilities for you if you distribute copies of the library or if you modify it.

For example, if you distribute copies of the library, whether gratis or for a fee, you must give the recipients all the rights that we gave you. You must make sure that they, too, receive or can get the source code. If you link other code with the library, you must provide complete object files to the recipients, so that they can relink them with the library after making changes to the library and recompiling it. And you must show them these terms so they know their rights.

We protect your rights with a two-step method: (1) we copyright the library, and (2) we offer you this license, which gives you legal permission to copy, distribute and/or modify the library.

To protect each distributor, we want to make it very clear that there is no warranty for the free library. Also, if the library is modified by someone else and passed on, the recipients should know that what they have is not the original version, so that the original author's reputation will not be affected by problems that might be introduced by others.

Finally, software patents pose a constant threat to the existence of any free program. We wish to make sure that a company cannot effectively restrict the users of a free program by obtaining a restrictive license from a patent holder. Therefore, we insist that any patent license obtained for a version of the library must be consistent with the full freedom of use specified in this license.

Most GNU software, including some libraries, is covered by the ordinary GNU General Public License. This license, the GNU Lesser General Public License, applies to certain designated libraries, and is quite different from the ordinary General Public License. We use this license for certain libraries in order to permit linking those libraries into non-free programs.

When a program is linked with a library, whether statically or using a shared library, the combination of the two is legally speaking a combined work, a derivative of the original library. The ordinary General Public License therefore permits such linking only if the entire combination fits its criteria of freedom. The Lesser General Public License permits more lax criteria for linking other code with the library.

We call this license the "Lesser" General Public License because it does Less to protect the user's freedom than the ordinary General Public License. It also provides other free software developers Less of an advantage over competing non-free programs. These disadvantages are the reason we use the ordinary General Public License for many libraries. However, the Lesser license provides advantages in certain special circumstances.

For example, on rare occasions, there may be a special need to encourage the widest possible use of a certain library, so that it becomes a de-facto standard. To achieve this, non-free programs must be allowed to use the library. A more frequent case is that a free library does the same job as widely used non-free libraries. In this case, there is little to gain by limiting the free library to free software only, so we use the Lesser General Public License.

In other cases, permission to use a particular library in non-free programs enables a greater number of people to use a large body of free software. For example, permission to use the GNU C Library in non-free programs enables many more people to use the whole GNU operating system, as well as its variant, the GNU/Linux operating system.

Although the Lesser General Public License is Less protective of the users' freedom, it does ensure that the user of a program that is linked with the Library has the freedom and the wherewithal to run that program using a modified version of the Library.

The precise terms and conditions for copying, distribution and modification follow. Pay close attention to the difference between a "work based on the library" and a "work that uses the library". The former contains code derived from the library, whereas the latter must be combined with the library in order to run.

TERMS AND CONDITIONS FOR COPYING, DISTRIBUTION AND MODIFICATION

0. This License Agreement applies to any software library or other program which contains a notice placed by the copyright holder or other authorized party saying it may be distributed under the terms of this Lesser General Public License (also called "this License"). Each licensee is addressed as "you."

A "library" means a collection of software functions and/or data prepared so as to be conveniently linked with application programs (which use some of those functions and data) to form executables.

The "Library", below, refers to any such software library or work which has been distributed under these terms. A "work based on the Library" means either the Library or any derivative work under copyright law: that is to say, a work containing the Library or a portion of it, either verbatim or with modifications and/or translated straightforwardly into another language. (Hereinafter, translation is included without limitation in the term "modification".)

"Source code" for a work means the preferred form of the work for making modifications to it. For a library, complete source code means all the source code for all modules it contains, plus any associated interface definition files, plus the scripts used to control compilation and installation of the library.

Activities other than copying, distribution and modification are not covered by this License; they are outside its scope. The act of running a program using the Library is not restricted, and output from such a program is covered only if its contents constitute a work based on the Library (independent of the use of the Library in a tool for writing it). Whether that is true depends on what the Library does and what the program that uses the Library does.

1. You may copy and distribute verbatim copies of the Library's complete source code as you receive it, in any medium, provided that you conspicuously and appropriately publish on each copy an appropriate copyright notice and disclaimer of warranty; keep intact all the notices that refer to this License and to the absence of any warranty; and distribute a copy of this License along with the Library.

You may charge a fee for the physical act of transferring a copy, and you may at your option offer warranty protection in exchange for a fee.

2. You may modify your copy or copies of the Library or any portion of it, thus forming a work based on the Library, and copy and distribute such modifications or work under the terms of Section 1 above, provided that you also meet all of these conditions:

a. The modified work must itself be a software library.

b. You must cause the files modified to carry prominent notices stating that you changed the files and the date of any change.

c. You must cause the whole of the work to be licensed at no charge to all third parties under the terms of this License.

d. If a facility in the modified Library refers to a function or a table of data to be supplied by an application program that uses the facility, other than as an argument passed when the facility is invoked, then you must make a good faith effort to ensure that, in the event an application does not supply such function or table, the facility still operates, and performs whatever part of its purpose remains meaningful.

(For example, a function in a library to compute square roots has a purpose that is entirely well-defined independent of the application. Therefore, Subsection 2d requires that any application-supplied function or table used by this function must be optional: if the application does not supply it, the square root function must still compute square roots.)

These requirements apply to the modified work as a whole. If identifiable sections of that work are not derived from the Library, and can be reasonably considered independent and separate works in themselves, then this License, and its terms, do not apply to those sections when you distribute them as separate works. But when you distribute the same sections as part of a whole which is a work based on the Library, the distribution of the whole must be on the terms of this License, whose permissions for other licensees extend to the entire whole, and thus to each and every part regardless of who wrote it.

Thus, it is not the intent of this section to claim rights or contest your rights to work written entirely by you; rather, the intent is to exercise the right to control the distribution of derivative or collective works based on the Library.

In addition, mere aggregation of another work not based on the Library with the Library (or with a work based on the Library) on a volume of a storage or distribution medium does not bring the other work under the scope of this License.

3. You may opt to apply the terms of the ordinary GNU General Public License instead of this License to a given copy of the Library. To do this, you must alter all the notices that refer to this License, so that they refer to the ordinary GNU General Public License, version 2, instead of to this License. (If a newer version than version 2 of the ordinary GNU General Public License has appeared, then you can specify that version instead if you wish.) Do not make any other change in these notices.

Once this change is made in a given copy, it is irreversible for that copy, so the ordinary GNU General Public License applies to all subsequent copies and derivative works made from that copy.

This option is useful when you wish to copy part of the code of the Library into a program that is not a library.

4. You may copy and distribute the Library (or a portion or derivative of it, under Section 2) in object code or executable form under the terms of Sections 1 and 2 above provided that you accompany it with the complete corresponding machine-readable source code, which must be distributed under the terms of Sections 1 and 2 above on a medium customarily used for software interchange.

If distribution of object code is made by offering access to copy from a designated place, then offering equivalent access to copy the source code from the same place satisfies the requirement to distribute the source code, even though third parties are not compelled to copy the source along with the object code.

5. A program that contains no derivative of any portion of the Library, but is designed to work with the Library by being compiled or linked with it, is called a "work that uses the Library". Such a work, in isolation, is not a derivative work of the Library, and therefore falls outside the scope of this License.

However, linking a "work that uses the Library" with the Library creates an executable that is a derivative of the Library (because it contains portions of the Library), rather than a "work that uses the library". The executable is therefore covered by this License. Section 6 states terms for distribution of such executables.

When a "work that uses the Library" uses material from a header file that is part of the Library, the object code for the work may be a derivative work of the Library even though the source code is not. Whether this is true is especially significant if the work can be linked without the Library, or if the work is itself a library. The threshold for this to be true is not precisely defined by law.

If such an object file uses only numerical parameters, data structure layouts and accessors, and small macros and small inline functions (ten lines or less in length), then the use of the object file is unrestricted, regardless of whether it is legally a derivative work. (Executables containing this object code plus portions of the Library will still fall under Section 6.)

Otherwise, if the work is a derivative of the Library, you may distribute the object code for the work under the terms of Section 6. Any executables containing that work also fall under Section 6, whether or not they are linked directly with the Library itself.

6. As an exception to the Sections above, you may also combine or link a "work that uses the Library" with the Library to produce a work containing portions of the Library, and distribute that work under terms of your choice, provided that the terms permit modification of the work for the customer's own use and reverse engineering for debugging such modifications.

You must give prominent notice with each copy of the work that the Library is used in it and that the Library and its use are covered by this License. You must supply a copy of this License. If the work during execution displays copyright notices, you must include the copyright notice for the Library among them, as well as a reference directing the user to the copy of this License. Also, you must do one of these things:

a. Accompany the work with the complete corresponding machine-readable source code for the Library including whatever changes were used in the work (which must be distributed under Sections 1 and 2 above); and, if the work is an executable linked with the Library, with the complete machine-readable "work that uses the Library", as object code and/or source code, so that the user can modify the Library and then relink to produce a modified executable containing the modified Library. (It is understood that the user who changes the contents of definitions files in the Library will not necessarily be able to recompile the application to use the modified definitions.)

b. Use a suitable shared library mechanism for linking with the Library. A suitable mechanism is one that (1) uses at run time a copy of the library already present on the user's computer system, rather than copying library functions into the executable, and (2) will operate properly with a modified version of the library, if the user installs one, as long as the modified version is interface-compatible with the version that the work was made with.

c. Accompany the work with a written offer, valid for at least three years, to give the same user the materials specified in Subsection 6a, above, for a charge no more than the cost of performing this distribution.

d. If distribution of the work is made by offering access to copy from a designated place, offer equivalent access to copy the above specified materials from the same place.

e. Verify that the user has already received a copy of these materials or that you have already sent this user a copy.

For an executable, the required form of the "work that uses the Library" must include any data and utility programs needed for reproducing the executable from it. However, as a special exception, the materials to be distributed need not include anything that is normally distributed (in either source or binary form) with the major components (compiler, kernel, and so on) of the operating system on which the executable runs, unless that component itself accompanies the executable.

It may happen that this requirement contradicts the license restrictions of other proprietary libraries that do not normally accompany the operating system. Such a contradiction means you cannot use both them and the Library together in an executable that you distribute.

7. You may place library facilities that are a work based on the Library side-by-side in a single library together with other library facilities not covered by this License, and distribute such a combined library, provided that the separate distribution of the work based on the Library and of the other library facilities is otherwise permitted, and provided that you do these two things:

a. Accompany the combined library with a copy of the same work based on the Library, uncombined with any other library facilities. This must be distributed under the terms of the Sections above.

b. Give prominent notice with the combined library of the fact that part of it is a work based on the Library, and explaining where to find the accompanying uncombined form of the same work.

8. You may not copy, modify, sublicense, link with, or distribute the Library except as expressly provided under this License. Any attempt otherwise to copy, modify, sublicense, link with, or distribute the Library is void, and will automatically terminate your rights under this License. However, parties who have received copies, or rights, from you under this License will not have their licenses terminated so long as such parties remain in full compliance.

9. You are not required to accept this License, since you have not signed it. However, nothing else grants you permission to modify or distribute the Library or its derivative works. These actions are prohibited by law if you do not accept this License. Therefore, by modifying or distributing the Library (or any work based on the Library), you indicate your acceptance of this License to do so, and all its terms and conditions for copying, distributing or modifying the Library or works based on it.

10. Each time you redistribute the Library (or any work based on the Library), the recipient automatically receives a license from the original licensor to copy, distribute, link with or modify the Library subject to these terms and conditions. You may not impose any further restrictions on the recipients' exercise of the rights granted herein. You are not responsible for enforcing compliance by third parties with this License.

11. If, as a consequence of a court judgment or allegation of patent infringement or for any other reason (not limited to patent issues), conditions are imposed on you (whether by court order, agreement or otherwise) that contradict the conditions of this License, they do not excuse you from the conditions of this License. If you cannot distribute so as to satisfy simultaneously your obligations under this License and any other pertinent obligations, then as a consequence you may not distribute the Library at all. For example, if a patent license would not permit royalty-free redistribution of the Library by all those who receive copies directly or indirectly through you, then the only way you could satisfy both it and this License would be to refrain entirely from distribution of the Library.

If any portion of this section is held invalid or unenforceable under any particular circumstance, the balance of the section is intended to apply, and the section as a whole is intended to apply in other circumstances.

It is not the purpose of this section to induce you to infringe any patents or other property right claims or to contest validity of any such claims; this section has the sole purpose of protecting the integrity of the free software distribution system which is implemented by public license practices. Many people have made generous contributions to the wide range of software distributed through that system in reliance on consistent application of that system; it is up to the author/donor to decide if he or she is willing to distribute software through any other system and a licensee cannot impose that choice.

This section is intended to make thoroughly clear what is believed to be a consequence of the rest of this License.

12. If the distribution and/or use of the Library is restricted in certain countries either by patents or by copyrighted interfaces, the original copyright holder who places the Library under this License may add an explicit geographical distribution limitation excluding those countries, so that distribution is permitted only in or among countries not thus excluded. In such case, this License incorporates the limitation as if written in the body of this License.

13. The Free Software Foundation may publish revised and/or new versions of the Lesser General Public License from time to time. Such new versions will be similar in spirit to the present version, but may differ in detail to address new problems or concerns.

Each version is given a distinguishing version number. If the Library specifies a version number of this License which applies to it and "any later version", you have the option of following the terms and conditions either of that version or of any later version published by the Free Software Foundation. If the Library does not specify a license version number, you may choose any version ever published by the Free Software Foundation.

14. If you wish to incorporate parts of the Library into other free programs whose distribution conditions are incompatible with these, write to the author to ask for permission. For software which is copyrighted by the Free Software Foundation, write to the Free Software Foundation; we sometimes make exceptions for this. Our decision will be guided by the two goals of preserving the free status of all derivatives of our free software and of promoting the sharing and reuse of software generally.

NO WARRANTY

15. BECAUSE THE LIBRARY IS LICENSED FREE OF CHARGE, THERE IS NO WARRANTY FOR THE LIBRARY, TO THE EXTENT PERMITTED BY APPLICABLE LAW. EXCEPT WHEN OTHERWISE STATED IN WRITING THE COPYRIGHT HOLDERS AND/OR OTHER PARTIES PROVIDE THE LIBRARY "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESSED OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE. THE ENTIRE RISK AS TO THE QUALITY AND PERFORMANCE OF THE LIBRARY IS WITH YOU. SHOULD THE LIBRARY PROVE DEFECTIVE, YOU ASSUME THE COST OF ALL NECESSARY SERVICING, REPAIR OR CORRECTION.

16. IN NO EVENT UNLESS REQUIRED BY APPLICABLE LAW OR AGREED TO IN WRITING WILL ANY COPYRIGHT HOLDER, OR ANY OTHER PARTY WHO MAY MODIFY AND/OR REDISTRIBUTE THE LIBRARY AS PERMITTED ABOVE, BE LIABLE TO YOU FOR DAMAGES, INCLUDING ANY GENERAL, SPECIAL, INCIDENTAL OR CONSEQUENTIAL DAMAGES ARISING OUT OF THE USE OR INABILITY TO USE THE LIBRARY (INCLUDING BUT NOT LIMITED TO LOSS OF DATA OR DATA BEING RENDERED INACCURATE OR LOSSES SUSTAINED BY YOU OR THIRD PARTIES OR A FAILURE OF THE LIBRARY TO OPERATE WITH ANY OTHER SOFTWARE), EVEN IF SUCH HOLDER OR OTHER PARTY HAS BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.

END OF TERMS AND CONDITIONS

Copyright Statement for JasperReports

* * JasperReports - Free Java report-generating library. * Copyright (C) 2001-2006 JasperSoft Corporation http://www.jaspersoft.com * * This library is free software; you can redistribute it and/or * modify it under the terms of the GNU Lesser General Public * License as published by the Free Software Foundation; either * version 2.1 of the License, or (at your option) any later version. * * This library is distributed in the hope that it will be useful, * but WITHOUT ANY WARRANTY; without even the implied warranty of * MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE. See the GNU * Lesser General Public License for more details. * * You should have received a copy of the GNU Lesser General Public * License along with this library; if not, write to the Free Software * Foundation, Inc., 59 Temple Place, Suite 330, Boston, MA 02111-1307, USA.

Mozilla Public License Version 1.1

1. Definitions.

1.0.1. "Commercial Use"

means distribution or otherwise making the Covered Code available to a third party.

1.1. "Contributor"

means each entity that creates or contributes to the creation of Modifications.

1.2. "Contributor Version"

means the combination of the Original Code, prior Modifications used by a Contributor, and the Modifications made by that particular Contributor.

1.3. "Covered Code"

means the Original Code or Modifications or the combination of the Original Code and Modifications, in each case including portions thereof.

1.4. "Electronic Distribution Mechanism"

means a mechanism generally accepted in the software development community for the electronic transfer of data.

1.5. "Executable"

means Covered Code in any form other than Source Code.

1.6. "Initial Developer"

means the individual or entity identified as the Initial Developer in the Source Code notice required by Exhibit A.

1.7. "Larger Work"

means a work which combines Covered Code or portions thereof with code not governed by the terms of this License.

1.8. "License"

means this document.

1.8.1. "Licensable"

means having the right to grant, to the maximum extent possible, whether at the time of the initial grant or subsequently acquired, any and all of the rights conveyed herein.

1.9. "Modifications"

means any addition to or deletion from the substance or structure of either the Original Code or any previous Modifications. When Covered Code is released as a series of files, a Modification is:

a. Any addition to or deletion from the contents of a file containing Original Code or previous Modifications.

b. Any new file that contains any part of the Original Code or previous Modifications.

1.10. "Original Code"

means Source Code of computer software code which is described in the Source Code notice required by Exhibit A as Original Code, and which, at the time of its release under this License is not already Covered Code governed by this License.

1.10.1. "Patent Claims"

means any patent claim(s), now owned or hereafter acquired, including without limitation, method, process, and apparatus claims, in any patent Licensable by grantor.

1.11. "Source Code"

means the preferred form of the Covered Code for making modifications to it, including all modules it contains, plus any associated interface definition files, scripts used to control compilation and installation of an Executable, or source code differential comparisons against either the Original Code or another well known, available Covered Code of the Contributor's choice. The Source Code can be in a compressed or archival form, provided the appropriate decompression or de-archiving software is widely available for no charge.

1.12. "You" (or "Your")

means an individual or a legal entity exercising rights under, and complying with all of the terms of, this License or a future version of this License issued under Section 6.1. For legal entities, "You" includes any entity which controls, is controlled by, or is under common control with You. For purposes of this definition, "control" means (a) the power, direct or indirect, to cause the direction or management of such entity, whether by contract or otherwise, or (b) ownership of more than fifty percent (50%) of the outstanding shares or beneficial ownership of such entity.

2. Source Code License.

2.1. The Initial Developer Grant.

The Initial Developer hereby grants You a world-wide, royalty-free, non-exclusive license, subject to third party intellectual property claims:

a. under intellectual property rights (other than patent or trademark) Licensable by Initial Developer to use, reproduce, modify, display, perform, sublicense and distribute the Original Code (or portions thereof) with or without Modifications, and/or as part of a Larger Work; and

b. under Patents Claims infringed by the making, using or selling of Original Code, to make, have made, use, practice, sell, and offer for sale, and/or otherwise dispose of the Original Code (or portions thereof).

c. the licenses granted in this Section 2.1 (a) and (b) are effective on the date Initial Developer first distributes Original Code under the terms of this License.

d. Notwithstanding Section 2.1 (b) above, no patent license is granted: 1) for code that You delete from the Original Code; 2) separate from the Original Code; or 3) for infringements caused by: i) the modification of the Original Code or ii) the combination of the Original Code with other software or devices.

2.2. Contributor Grant.

Subject to third party intellectual property claims, each Contributor hereby grants You a world-wide, royalty-free, non-exclusive license

a. under intellectual property rights (other than patent or trademark) Licensable by Contributor, to use, reproduce, modify, display, perform, sublicense and distribute the Modifications created by such Contributor (or portions thereof) either on an unmodified basis, with other Modifications, as Covered Code and/or as part of a Larger Work; and

b. under Patent Claims infringed by the making, using, or selling of Modifications made by that Contributor either alone and/or in combination with its Contributor Version (or portions of such combination), to make, use, sell, offer for sale, have made, and/or otherwise dispose of: 1) Modifications made by that Contributor (or portions thereof); and 2) the combination of Modifications made by that Contributor with its Contributor Version (or portions of such combination).

c. the licenses granted in Sections 2.2 (a) and 2.2 (b) are effective on the date Contributor first makes Commercial Use of the Covered Code.

d. Notwithstanding Section 2.2 (b) above, no patent license is granted: 1) for any code that Contributor has deleted from the Contributor Version; 2) separate from the Contributor Version; 3) for infringements caused by: i) third party modifications of Contributor Version or ii) the combination of Modifications made by that Contributor with other software (except as part of the Contributor Version) or other devices; or 4) under Patent Claims infringed by Covered Code in the absence of Modifications made by that Contributor.

3. Distribution Obligations.

3.1. Application of License.

The Modifications which You create or to which You contribute are governed by the terms of this License, including without limitation Section 2.2. The Source Code version of Covered Code may be distributed only under the terms of this License or a future version of this License released under Section 6.1, and You must include a copy of this License with every copy of the Source Code You distribute. You may not offer or impose any terms on any Source Code version that alters or restricts the applicable version of this License or the recipients' rights hereunder. However, You may include an additional document offering the additional rights described in Section 3.5.

3.2. Availability of Source Code.

Any Modification which You create or to which You contribute must be made available in Source Code form under the terms of this License either on the same media as an Executable version or through an accepted Electronic Distribution Mechanism to anyone to whom you made an Executable version available; and if made available through Electronic Distribution Mechanism, must remain available for at least twelve (12) months after the date it initially became available, or at least six (6) months after a subsequent version of that particular Modification has been made available to such recipients. You are responsible for ensuring that the Source Code version remains available even if the Electronic Distribution Mechanism is maintained by a third party.

3.3. Description of Modifications.

You must cause all Covered Code to which You contribute to contain a file documenting the changes You made to create that Covered Code and the date of any change. You must include a prominent statement that the Modification is derived, directly or indirectly, from Original Code provided by the Initial Developer and including the name of the Initial Developer in (a) the Source Code, and (b) in any notice in an Executable version or related documentation in which You describe the origin or ownership of the Covered Code.

3.4. Intellectual Property Matters

(a) Third Party Claims

If Contributor has knowledge that a license under a third party's intellectual property rights is required to exercise the rights granted by such Contributor under Sections 2.1 or 2.2, Contributor must include a text file with the Source Code distribution titled "LEGAL" which describes the claim and the party making the claim in sufficient detail that a recipient will know whom to contact. If Contributor obtains such knowledge after the Modification is made available as described in Section 3.2, Contributor shall promptly modify the LEGAL file in all copies Contributor makes available thereafter and shall take other steps (such as notifying appropriate mailing lists or newsgroups) reasonably calculated to inform those who received the Covered Code that new knowledge has been obtained.

(b) Contributor APIs

If Contributor's Modifications include an application programming interface and Contributor has knowledge of patent licenses which are reasonably necessary to implement that API, Contributor must also include this information in the legal file.

(c) Representations.

Contributor represents that, except as disclosed pursuant to Section 3.4 (a) above, Contributor believes that Contributor's Modifications are Contributor's original creation(s) and/or Contributor has sufficient rights to grant the rights conveyed by this License.

3.5. Required Notices.

You must duplicate the notice in Exhibit A in each file of the Source Code. If it is not possible to put such notice in a particular Source Code file due to its structure, then You must include such notice in a location (such as a relevant directory) where a user would be likely to look for such a notice. If You created one or more Modification(s) You may add your name as a Contributor to the notice described in Exhibit A. You must also duplicate this License in any documentation for the Source Code where You describe recipients' rights or ownership rights relating to Covered Code. You may choose to offer, and to charge a fee for, warranty, support, indemnity or liability obligations to one or more recipients of Covered Code. However, You may do so only on Your own behalf, and not on behalf of the Initial Developer or any Contributor. You must make it absolutely clear than any such warranty, support, indemnity or liability obligation is offered by You alone, and You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of warranty, support, indemnity or liability terms You offer.

3.6. Distribution of Executable Versions.

You may distribute Covered Code in Executable form only if the requirements of Sections 3.1, 3.2, 3.3, 3.4 and 3.5 have been met for that Covered Code, and if You include a notice stating that the Source Code version of the Covered Code is available under the terms of this License, including a description of how and where You have fulfilled the obligations of Section 3.2. The notice must be conspicuously included in any notice in an Executable version, related documentation or collateral in which You describe recipients' rights relating to the Covered Code. You may distribute the Executable version of Covered Code or ownership rights under a license of Your choice, which may contain terms different from this License, provided that You are in compliance with the terms of this License and that the license for the Executable version does not attempt to limit or alter the recipient's rights in the Source Code version from the rights set forth in this License. If You distribute the Executable version under a different license You must make it absolutely clear that any terms which differ from this License are offered by You alone, not by the Initial Developer or any Contributor. You hereby agree to indemnify the Initial Developer and every Contributor for any liability incurred by the Initial Developer or such Contributor as a result of any such terms You offer.

3.7. Larger Works.

You may create a Larger Work by combining Covered Code with other code not governed by the terms of this License and distribute the Larger Work as a single product. In such a case, You must make sure the requirements of this License are fulfilled for the Covered Code.

4. Inability to Comply Due to Statute or Regulation.

If it is impossible for You to comply with any of the terms of this License with respect to some or all of the Covered Code due to statute, judicial order, or regulation then You must: (a) comply with the terms of this License to the maximum extent possible; and (b) describe the limitations and the code they affect. Such description must be included in the legal file described in Section 3.4 and must be included with all distributions of the Source Code. Except to the extent prohibited by statute or regulation, such description must be sufficiently detailed for a recipient of ordinary skill to be able to understand it.

5. Application of this License.

This License applies to code to which the Initial Developer has attached the notice in Exhibit A and to related Covered Code.

6. Versions of the License.

6.1. New Versions

Netscape Communications Corporation ("Netscape") may publish revised and/or new versions of the License from time to time. Each version will be given a distinguishing version number.

6.2. Effect of New Versions

Once Covered Code has been published under a particular version of the License, You may always continue to use it under the terms of that version. You may also choose to use such Covered Code under the terms of any subsequent version of the License published by Netscape. No one other than Netscape has the right to modify the terms applicable to Covered Code created under this License.

6.3. Derivative Works

If You create or use a modified version of this License (which you may only do in order to apply it to code which is not already Covered Code governed by this License), You must (a) rename Your license so that the phrases "Mozilla", "MOZILLAPL", "MOZPL", "Netscape", "MPL", "NPL" or any confusingly similar phrase do not appear in your license (except to note that your license differs from this License) and (b) otherwise make it clear that Your version of the license contains terms which differ from the Mozilla Public License and Netscape Public License. (Filling in the name of the Initial Developer, Original Code or Contributor in the notice described in Exhibit A shall not of themselves be deemed to be modifications of this License.)

7. Disclaimer of warranty

Covered code is provided under this license on an "as is" basis, without warranty of any kind, either expressed or implied, including, without limitation, warranties that the covered code is free of defects, merchantable, fit for a particular purpose or non-infringing. The entire risk as to the quality and performance of the covered code is with you. Should any covered code prove defective in any respect, you (not the initial developer or any other contributor) assume the cost of any necessary servicing, repair or correction. This disclaimer of warranty constitutes an essential part of this license. No use of any covered code is authorized hereunder except under this disclaimer.

8. Termination

8.1. This License and the rights granted hereunder will terminate automatically if You fail to comply with terms herein and fail to cure such breach within 30 days of becoming aware of the breach. All sublicenses to the Covered Code which are properly granted shall survive any termination of this License. Provisions which, by their nature, must remain in effect beyond the termination of this License shall survive.

8.2. If You initiate litigation by asserting a patent infringement claim (excluding declatory judgment actions) against Initial Developer or a Contributor (the Initial Developer or Contributor against whom You file such action is referred to as "Participant") alleging that:

a. such Participant's Contributor Version directly or indirectly infringes any patent, then any and all rights granted by such Participant to You under Sections 2.1 and/or 2.2 of this License shall, upon 60 days notice from Participant terminate prospectively, unless if within 60 days after receipt of notice You either: (i) agree in writing to pay Participant a mutually agreeable reasonable royalty for Your past and future use of Modifications made by such Participant, or (ii) withdraw Your litigation claim with respect to the Contributor Version against such Participant. If within 60 days of notice, a reasonable royalty and payment arrangement are not mutually agreed upon in writing by the parties or the litigation claim is not withdrawn, the rights granted by Participant to You under Sections 2.1 and/or 2.2 automatically terminate at the expiration of the 60 day notice period specified above.

b. any software, hardware, or device, other than such Participant's Contributor Version, directly or indirectly infringes any patent, then any rights granted to You by such Participant under Sections 2.1(b) and 2.2(b) are revoked effective as of the date You first made, used, sold, distributed, or had made, Modifications made by that Participant.

8.3. If You assert a patent infringement claim against Participant alleging that such Participant's Contributor Version directly or indirectly infringes any patent where such claim is resolved (such as by license or settlement) prior to the initiation of patent infringement litigation, then the reasonable value of the licenses granted by such Participant under Sections 2.1 or 2.2 shall be taken into account in determining the amount or value of any payment or license.

8.4. In the event of termination under Sections 8.1 or 8.2 above, all end user license agreements (excluding distributors and resellers) which have been validly granted by You or any distributor hereunder prior to termination shall survive termination.

9. Limitation of liability

Under no circumstances and under no legal theory, whether tort (including negligence), contract, or otherwise, shall you, the initial developer, any other contributor, or any distributor of covered code, or any supplier of any of such parties, be liable to any person for any indirect, special, incidental, or consequential damages of any character including, without limitation, damages for loss of goodwill, work stoppage, computer failure or malfunction, or any and all other commercial damages or losses, even if such party shall have been informed of the possibility of such damages. This limitation of liability shall not apply to liability for death or personal injury resulting from such party's negligence to the extent applicable law prohibits such limitation. Some jurisdictions do not allow the exclusion or limitation of incidental or consequential damages, so this exclusion and limitation may not apply to you.

10. U.S. government end users

The Covered Code is a "commercial item," as that term is defined in 48 C.F.R. 2.101 (Oct. 1995), consisting of "commercial computer software" and "commercial computer software documentation," as such terms are used in 48 C.F.R. 12.212 (Sept. 1995). Consistent with 48 C.F.R. 12.212 and 48 C.F.R. 227.7202-1 through 227.7202-4 (June 1995), all U.S. Government End Users acquire Covered Code with only those rights set forth herein.

11. Miscellaneous

This License represents the complete agreement concerning subject matter hereof. If any provision of this License is held to be unenforceable, such provision shall be reformed only to the extent necessary to make it enforceable. This License shall be governed by California law provisions (except to the extent applicable law, if any, provides otherwise), excluding its conflict-of-law provisions. With respect to disputes in which at least one party is a citizen of, or an entity chartered or registered to do business in the United States of America, any litigation relating to this License shall be subject to the jurisdiction of the Federal Courts of the Northern District of California, with venue lying in Santa Clara County, California, with the losing party responsible for costs, including without limitation, court costs and reasonable attorneys' fees and expenses. The application of the United Nations Convention on Contracts for the International Sale of Goods is expressly excluded. Any law or regulation which provides that the language of a contract shall be construed against the drafter shall not apply to this License.

12. Responsibility for claims

As between Initial Developer and the Contributors, each party is responsible for claims and damages arising, directly or indirectly, out of its utilization of rights under this License and You agree to work with Initial Developer and Contributors to distribute such responsibility on an equitable basis. Nothing herein is intended or shall be deemed to constitute any admission of liability.

13. Multiple-licensed code

Initial Developer may designate portions of the Covered Code as "Multiple-Licensed". "Multiple-Licensed" means that the Initial Developer permits you to utilize portions of the Covered Code under Your choice of the MPL or the alternative licenses, if any, specified by the Initial Developer in the file described in Exhibit A.

Exhibit A - Mozilla Public License.

"The contents of this file are subject to the Mozilla Public License 
Version 1.1 (the "License"); you may not use this file except in
compliance with the License. You may obtain a copy of the License at
http://www.mozilla.org/MPL/

Software distributed under the License is distributed on an "AS IS"
basis, WITHOUT WARRANTY OF ANY KIND, either express or implied. See the
License for the specific language governing rights and limitations
under the License.

The Original Code is ______________________________________.

The Initial Developer of the Original Code is ________________________.
Portions created by ______________________ are Copyright (C) ______
_______________________. All Rights Reserved.

Contributor(s): ______________________________________.

Alternatively, the contents of this file may be used under the terms
of the _____ license (the  "[___] License"), in which case the
provisions of [______] License are applicable instead of those
above. If you wish to allow use of your version of this file only
under the terms of the [____] License and not to allow others to use
your version of this file under the MPL, indicate your decision by
deleting the provisions above and replace them with the notice and
other provisions required by the [___] License. If you do not delete
the provisions above, a recipient may use your version of this file
under either the MPL or the [___] License."

NOTE: The text of this Exhibit A may differ slightly from the text of the notices in the Source Code files of the Original Code. You should use the text of this Exhibit A rather than the text found in the Original Code Source Code for Your Modifications.

Obtaining Documentation and Submitting a Service Request

For information on obtaining documentation, submitting a service request, and gathering additional information, see the monthly What's New in Cisco Product Documentation, which also lists all new and revised Cisco technical documentation, at:

http://www.cisco.com/en/US/docs/general/whatsnew/whatsnew.html

Subscribe to the What's New in Cisco Product Documentation as a Really Simple Syndication (RSS) feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service and Cisco currently supports RSS Version 2.0.