Guest

Cisco Application Networking Manager

Release Notes for the Cisco Application Networking Manager 1.1

Table Of Contents

Release Notes for the Cisco Application Networking Manager, Release 1.1

New Features

Supported Devices and Software

ANM Product Documentation Set

Documentation Updates

Open Caveats in Software Version 1.1

Obtaining Documentation and Submitting a Service Request


Release Notes for the Cisco Application Networking Manager, Release 1.1


March 18, 2009

This release note applies to the Cisco Application Networking Manager (ANM) 1.1 release.

This release note contains the following sections:

New Features

Supported Devices and Software

ANM Product Documentation Set

Documentation Updates

Open Caveats in Software Version 1.1

Obtaining Documentation and Submitting a Service Request

New Features

The Cisco ANM is a networking management application that manages Cisco Application Control Engine (Cisco ACE) modules in your networking environment. It includes:

The Cisco ANM provides the following features:

Device Discovery and Import

Cisco ANM allows you to select the Cisco Catalyst 6500 series chassis and their corresponding ACE modules that you want to import. The method you use to identify and select the chassis and its modules is up to you:

You can specify the individual Cisco Catalyst 6500 series chassis and modules you want to import and then import any resident ACE modules with their configurations.

You can run device discovery to identify the Cisco Catalyst 6500 series chassis on your network and select the chassis and ACE modules you want to import.

Regardless of the method you use, if the ACE modules have not been configured before, ANM can provide a configuration file that allows you to import them and then configure them using the ANM interface.

Module and Server Management

ACE module management allows you to import the ACE modules you want to manage using ANM, establish static routes, and install, update, or remove ACE module licenses. In addition, you can configure ACE module for high availability to ensure a reliable, fault-tolerant environment.

ACE module management also allows you to extract, modify, and tag configuration templates for auditable, retrievable working configurations and to synchronize configurations between Cisco ANM-maintained configuration files or templates and ACE modules or chassis.

Server management enables you to activate and suspend servers, establish server weight, and set limits on the number of connections for each server.

Provisioning

Cisco ANM allows you to configure such items as VLANs, SNMP, syslog, ACLs, and SSL on ACE modules. In addition, you can establish traffic policies, load-balancing services with activation and suspension, and fault tolerance to ensure that network services are available to your customers in a reliable manner.

In addition to service load balancing, traffic policies, and configuration templates, you can use virtual contexts to partition an Cisco ACE module into multiple virtual devices. Each virtual context contains its own set of policies, interfaces, and resources, allowing you to more efficiently manage system resources and services. Users can create their own logical groups for ease of management and reference.

You can also create virtual servers, which allow you to further manage system resources. When you add and configure virtual servers, you define their specific properties, load balancing attributes, resources, and policies. In addition to Layer 3/Layer 4 traffic policies, Cisco ANM allows you to configure Layer 7 protocol-specific classes that perform server load balancing based on HTTP traffic, deep inspection of HTTP traffic, or the inspection of FTP commands by the ACE module.

After configuring virtual servers, you can deploy them when appropriate for your environment.

Cisco ANM also allows you to establish resource classes which are sets of resources and allocations available for use by virtual contexts. Resource classes ensure that no single context uses all available resources, and allows you to configure resources in a manner that best meets your customers' needs.

Monitoring

Monitoring provides real-time device health, performance information, event reporting, and resource utilization via syslog, Trap, and SNMP polling.

User and system administration

Cisco ANM provides secure, granular, role-based access control that ensures that a user or user group can view only the devices or services or perform the actions that are included in the domains to which they have been given access.

If you encounter a problem with Cisco ANM, you can use the Lifeline feature to report the problem to Cisco Technical Support. Lifeline takes a snapshot of the running system configuration, status, buffers, logs, thread dumps, and messages and allows you to submit a diagnostic package to Cisco to aid in problem resolution.

Supported Devices and Software

For information on Cisco devices supported by ANM 1.1, refer to the Supported Devices Table for the Cisco Application Networking Manager 1.1 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 Cisco Application Networking Manager (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 1.1—Includes complete installation and configuration information for the ANM 2.0 software.

User Guide for the Cisco Application Networking Manager 1.1—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—Help topics for all pages in the UI (also provides access to PDFs of the user guide). Select an option from the ANM GUI, then click Help.

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

Documentation Updates

Config > Tools > IP Discovery is an optional feature that discovers your Cisco Catalyst 6500 series chassis and ACE modules by using Telnet credentials (in clear text) combined with a credentials pool that you provide under Config > Tools > Credential Pool. If you want a more secure method of adding your Catalyst 6500 series chassis and ACE modules, you can add the devices in Config > Devices rather than having ANM discover the devices. ANM uses SSH and HTTPS for all configuration activity. For more information, see the "Configuring ACE Modules" chapter of the User Guide for the Cisco Application Networking Manager 1.1.

Open Caveats in Software Version 1.1

Table 1 describes the open caveats in software version 1.1.

Table 1 Open Caveats in Software Version 1.1 

Bug ID
Summary
Explanation

CSCsg63335

Real Server statistics are not easy to read when displayed with default statistics.

Real Server statistics might be hard to read because the graph space is too small to display the information clearly.

Workaround: Increase the graph size by maximizing the browser window, removing less-frequently used toolbars, or clicking on the ANM Full Screen Mode button. To avoid round-off curves, use Multigraph mode to view individual graphs.

CSCsg72242

Compare Configuration feature needs more clear instructions.

When you select Config > Devices > device > Expert > Compare Configuration, the Compare Configuration screen shows "Add row" and "Delete row" options when one device's configuration has a configuration row that the other device does not. When you select Add Row for a certain column or virtual context, the selected row or attribute is added to the other virtual context to which it is being compared. When you select Delete Row for a certain column or virtual context, the selected row is deleted from the other virtual context to which it is being compared. If you are unclear about the function of these options, consult the online help.

Workaround: None.

CSCsg88679

Spaces are replaced with underscores in templates.

When you click Config > Global > Template Management and add a template name with a space in it, ignore the yellow warning color, and click OK.The space is replaced by an underscore.

Click Template Management again to see a list of all templates. The new template name is different from the name you entered.

Workaround: Do not use a space in template names.

CSCsg88747

Cannot remove a template containing a management VLAN interface.

When you create a template that contains a management VLAN configuration that is deployed to a virtual context, if the system admin removes the template configuration from the virtual context, you need to check the virtual context under System > SNMP to make sure the SNMP interface name is not referencing the VLAN that gets configured through the template.

Workaround: None.

CSCsg90474

Redeploying the virtual server form disables Layer 7 FTP command inspection service momentarily.

The Layer 7 FTP command inspection service might be momentarily disabled and then immediately re enabled whenever you redeploy the virtual server form. This issue only affects users who have configured a Layer 7 FTP command inspection in a virtual server, and then chose to edit the virtual server's configuration while it is live in production.


Caution If you have a virtual server on which FTP Inspect is configured, and then you select that virtual server to make changes, if you press OK on the Virtual Server configuration screen, even if you made no changes, there will be a service interruption on the ACE.

Workaround: As with any service-impacting configuration changes, we recommend you perform such operations during a defined service downtime period if possible. If you are not making any changes, click Cancel instead of OK on the virtual server configuration screen to prevent any service interruption. To make changes to the FTP command inspection, use the Expert mode instead of the virtual server screen to prevent any service interruption.

CSCsg93505

You cannot create a VLAN in a virtual context if does not exist in the VLAN group on the Cat6K.

If you deploy a virtual context with one or more VLANs allocated to it, and if one of the VLANs is not allocated on the Cat6K, you will get an error when you try to update the VLAN range. The ANM tries to validate the current VLAN range with what is defined on the Cat6K, and ANM generates an error because the VLANs are not found on the Cat6K.

Workaround: Allocate the VLANs on the Cat6K before allocating them to an ACE module.

CSCsg95356

Cannot use newly created server farm in other places.

When creating a virtual server, items created inline can not be used in a secondary location. For example, you create a Layer 7 Load Balancing Rule on a URL match and in that rule you create two server farms (primary and backup), a sticky group, and a backend SSL proxy. You want to add an HTTP header for this traffic. You configure the default action and keep everything the same except you don't configure the HTTP header. The server farms, SSL proxy, and the sticky group do not appear in the list for the default action.

Workaround: Create the server farm or SSL Proxy Service before creating the virtual server. You can deploy the virtual server with the default action set to drop. Then you can edit the virtual server and change the default action. All of the objects you created appear correctly.

CSCsg95618

Should not allow VLAN ID to be deployed if it is not allocated.

When you create a template that contains a VLAN that is not allocated on a chassis, you can successfully deploy the template to a virtual context because ACE accepts VLANs that are not allocated on a chassis. However, when you try to remove the template from the virtual context, ANM is not able to remove the template because the VLAN was not previously allocated.

Workaround: Use VLANs that are already allocated on a chassis.

CSCsh13330

Vertical units become illegible when you select all statistics.

If you select Monitor > Device > virtual_context> Real Servers, select all statistics, then click Graph, the resulting data is hard to read because of the large amount of information that is displayed on the graph.

Workaround: Do not specify more than two statistics to display in graphical mode. You can also increase the graph size by maximizing the browser window, removing less-frequently used toolbars, or clicking on the ANM Full Screen Mode button. In addition, you can use Multigraph mode.

CSCsh19459

There are no new events after user changed to daylight time.

When day light saving time ends, the ANM server clock is set back 1 hour.

Workaround: Reboot the ANM server.

CSCsh19866

Cannot associate deny action to a rule in a Layer 7 FTP Inspect policy map.

When using Expert mode, you cannot associate a deny action to a rule in a Layer 7 FTP Inspection policy map.

Workaround: Delete the policy map and use the virtual server form to enable Layer 7 FTP Command Inspection.


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.