Release Notes for Cisco 2700 and 2710 Location Appliances for Software Release 2.1.42.0

Table Of Contents

Release Notes for Cisco 2700 and 2710 Location Appliances for Software Release 2.1.42.0

Contents

Introduction

System Requirements

Compatibility Matrix

Upgrading to this Software Release

Backup of Release 2.0.x or Later Cannot be Restored on Earlier Releases

Location Appliance Image is Compressed

Secure Shell V1.0 is No Longer Supported

Updated Location Appliance Software Version Shown in WCS After Polling

Important Notes

Operational Notes

Mandatory Upgrade of Location Software Required to Reflect New 2007 Daylight Saving Time Dates

Automatic Installation Script for Initial Install

Location History Timestamps Match Browser's Locale

Assign a Controller/Network Design/Event Group to a Location Appliance Before Using Auto-Synch

Controller Name Must be Unique Before Synchronization

Verify WCS and Location Server Software Compatibility Before Synchronization

Recommended Wireless Adapter Clients for Calibration

Recommended Settings for Absolute and Relative Discard RSSI Times (Location Parameters)

Software Restart Button Removed

Enhanced Maintenance Backup Operation

Mandatory Default Root Password Change

Recovering Lost Root Password

New Feature Support

Smooth Location Positions (NEW Location Parameter)

Location Changes (NEW Event Notification)

Battery Level (NEW Event Notification)

Number of Tracked Elements and Tracked Elements Limit (NEW Advanced Parameters)

Cisco UDI (NEW Advanced Parameter)

Import and Export of Asset Information (NEW Administration Parameters)

Display Contributing Access Points for Client and Tag Locations (NEW Monitor Parameters)

Display Last Detected Information for Clients and Tags with Filtering Option (NEW Monitor Parameters)

Inspecting Location Readiness and Location Quality (NEW Monitor Parameters)

Deployment Planning for Data, Voice, and Location (NEW Monitor Parameter)

Analyzing Element Location Accuracy Using Testpoints (NEW Location and Monitor Parameter)

Caveats

Open Caveats

Resolved Caveats

If You Need More Information

Troubleshooting

Documentation Updates

Software Documentation

Related Documentation

Obtaining Documentation and Submitting a Service Request

Copyright © 2007 Cisco Systems, Inc. All rights reserved.

Release Notes for Cisco 2700 and 2710 Location Appliances for Software Release 2.1.42.0

---

November 6, 2007

These release notes describe features, enhancements, and caveats for software release 2.1.42.0 for Cisco Location Appliances. This release of location appliance software supports both Cisco 2700 and 2710 location appliances and operates with Cisco Wireless LAN Solution versions 4.0, 3.2, 3.1, and 3.0.

Contents

These release notes contain the following sections:

•Introduction

•System Requirements

•Important Notes

•Caveats

•Troubleshooting

•Documentation Updates

•Related Documentation

•Obtaining Documentation and Submitting a Service Request

Introduction

Location appliance software release 2.1.42.0 supports Cisco 2700 and 2710 location appliances that operate with Cisco Wireless LAN Solution versions 4.0, 3.2, 3.1, and 3.0. Location appliances compute, collect, and store historical location data using Cisco wireless LAN controllers and access points to track the physical location of wireless devices. The collected location data can be viewed in GUI format in the Cisco Wireless Control System (WCS), the centralized WLAN management platform.

System Requirements

You can install this software release on any 2700 or 2710 location appliance.

Compatibility Matrix

Table 1 describes compatibility between WCS and location server versions.

Table 1

WCS \ Location Server	LOC 1.1	LOC 1.2	LOC 2.0	LOC 2.1
WCS 3.0	Supported	Supported1	Not supported	Not supported
WCS 3.1	Supported2	Supported	Supported from WCS 3.1.35.0 onward3	Supported from WCS 3.1.35.0 onward3
WCS 3.2	Supported2, 3, 4 , 5	Supported3, 4, 5	Supported	Supported6
WCS 4.07	Supported2, 3, 4, 5, 7	Supported3, 4, 5, 7	Supported7	Supported

1 Certain antenna attributes are ignored by WCS. 2 Certain antenna attributes are ignored by the location server. 3 Asynchronous notification features are ignored by the location server. 4 Backup and restore operations for the location server may time out. 5 Searching for elements by a specific MAC address or asset name will not work until the location server SW is upgraded. 6 Battery level and location update notification update features are ignored by WCS. Location smoothing parameters and contributing access point debug options are ignored by WCS. 7 Battery level and location update notification update features are ignored by the location server. Location smoothing parameters and contributing access point debug options are ignored by the location server.

WCS and Location Server Compatibility Matrix

Upgrading to this Software Release

For instructions on using either Cisco WCS or a console port to install this software on location appliances, refer to the "Updating Location Appliance Software" section in the "Installation and Configuration" chapter of the Cisco 2700 Series Installation and Configuration Guide (78-17180-02 and later).

Click this link to browse to that document:

http://www.cisco.com/en/US/products/ps6386/prod_installation_guides_list.html

Backup of Release 2.0.x or Later Cannot be Restored on Earlier Releases

A backup of location appliance software releases 2.0.x and later cannot be restored on any location appliance running an earlier software release. Before you upgrade a location appliance to 2.0.x release or later, Cisco recommends that you create a backup of the earlier release and archive it. This will enable you to convert an upgraded system to an earlier release, if necessary.

Location Appliance Image is Compressed

If you download the server image *.gz file, the location appliance automatically decompresses (unzips) it, and you can proceed with the installation as before. If you manually download the compressed *.gz file using FTP, you must first decompress the files before running the installer. These files have been compressed under the LINUX operating system and must be decompressed using the gunzip utility program. The unzip method you use is defined by the filename you are trying to unzip. To make the bin file executable, use the following command:

chmod +x filename.bin

Secure Shell V1.0 is No Longer Supported

Support for secure shell (SSH) version 1 (v1) is not supported in releases 2.1.x and later due to known security issues; however, SSH v2 is supported.

---

Note After installing release 2.1.x, you must reboot the location appliance to remove support of SSH v1.

---

---

Note To remove SSH v1 support for releases 2.0.x and earlier, you must manually edit the sshd_config file to remove support for SSH v1 by adding Protocol 2 to the end of the script as noted below.

#override default of no subsystems

Subsystem sftp /usr/libexec/openssh/sftp-server

Protocol 2

•With this addition, the script will match that of releases 2.1.x and later.

•A restart is required to reread the config file after the edit is made.

---

Updated Location Appliance Software Version Shown in WCS After Polling

After a software update, the new location appliance software version does not immediately appear in location server queries on WCS. Up to five minutes is required for the new version to appear. WCS, by default, queries the location appliance every five minutes for status.

Important Notes

This section describes important information about new features or operational notes for software release 2.1.42.0 for location appliances.

Operational Notes

The following operational enhancements and updates are associated with this release.

Mandatory Upgrade of Location Software Required to Reflect New 2007 Daylight Saving Time Dates

The United States has changed the start and end dates of Daylight Saving Time (DST) for 2007. In 2007, DST within the US will begin on the second Sunday in March and end on the first Sunday in November. A mandatory upgrade to release 2.1.42.0 which incorporates support for this new DST period is required to prevent incorrect time reporting during certain periods of DST. Specifically, not upgrading your location appliance to version 2.1.42.0 will result in incorrect time reporting from March 11, 2007 through April 2, 2007 and from October 29, 2007 through November 4, 2007.

Automatic Installation Script for Initial Install

Beginning with release 2.1.34, an automatic setup wizard is available to step you through the initial installation of the location appliance. You also have the option of installing the location appliance manually.

An example of the complete automatic installation script (and manual installation process) is provided in the Cisco 2700 Series Installation and Configuration Guide. You can find this document online at http://www.cisco.com/en/US/products/ps6386/prod_installation_guides_list.html.

Location History Timestamps Match Browser's Locale

The WCS timestamp is based on the browser's location and not on the location appliance settings. Changing the time zone of the WCS or on the location appliance does not change the timestamp for the location history.

Assign a Controller/Network Design/Event Group to a Location Appliance Before Using Auto-Synch

With auto-synchronization, controllers, network designs, and event groups that are detected as unsynchronized are synchronized automatically. Before this automatic synchronization can be enabled, you must assign a controller, event group, or network design to a location appliance.

Controller Name Must be Unique Before Synchronization

The assigned controller names must be unique. If the controller names are duplicated, the synchronization process occurs only on one controller.

Verify WCS and Location Server Software Compatibility Before Synchronization

The software versions for WCS and the location server must be compatible for synchronization to perform properly. Please see the compatibility matrix noted in Table 1-1 of this release note for WCS and location server compatibility.

Recommended Wireless Adapter Clients for Calibration

We recommend using Cisco Aironet 802.11 a/b/g Wireless Cardbus Adapter Clients (AIR-CB21AG) with the latest drivers for calibrating location models. The client should be CCX compatible and version 2 or greater. Adapter client versions less than 2.0 are not ideal for calibration.

Recommended Settings for Absolute and Relative Discard RSSI Times (Location Parameters)

No value less than the default value of 3 minutes should be set for Relative Discard RSSI Time.

No value less than the default value of 60 minutes should be set for Absolute Discard RSSI Time.

Path: Location > Location Server > Administration > Location Parameters

Software Restart Button Removed

The Software Restart Button is no longer available on the Advanced Parameters page.

Path: Location > Location Server > Administration > Advanced Parameters

Enhanced Maintenance Backup Operation

Progress of an active backup and its completion percentage now appear on the Backup Operation page for location servers. You can also open another window while the backup continues in the background.

Path: Location > Location Server> Maintenance > Backup

Mandatory Default Root Password Change

You must change the default root password during initial configuration of the location appliance to ensure optimum network security.

•For releases 2.1.34 and later, you are prompted to change the password during the setup script.

•You can also change the password using the Linux command, "passwd."

Recovering Lost Root Password

If you lose or forget the root password for the location appliance, do the following:

---

Step 1 When the GRUB screen comes up, press Esc to enter the boot menu.

Step 2 Press e to edit.

Step 3 Navigate to the line beginning with "kernel," and press e.

At the end of the line enter a space and the number one (1). Press Enter to save this change.

Step 4 Press b to begin boot sequence.

At the end of the boot sequence, a shell prompt appears.

Step 5 You can change the root password by entering the passwd command.

Step 6 Enter and confirm the new password.

Step 7 Restart the machine.

---

New Feature Support

Please note the new feature support added since 2.0.48.0.

Smooth Location Positions (NEW Location Parameter)

You can adjust smoothing for a particular element. Options range from Off (no smoothing) to Maximum smoothing. The Off (no smoothing) option is appropriate for an item that is in constant movement such as an asset tag on medical equipment or store inventory. Maximum smoothing is appropriate for an item that is generally immobile.

Path: Location > Location Server > Administration > Location Parameters

Location Changes (NEW Event Notification)

Location Change events are generated by the location server when client stations, asset tags, rogue clients and rogue access points move from one location to another. Events are also logged when cleared.

Path: Location > Notifications

Battery Level (NEW Event Notification)

Battery Level events are generated by the location server for all tracked asset tags. Events are also logged when cleared.

Path: Location > Notifications

Number of Tracked Elements and Tracked Elements Limit (NEW Advanced Parameters)

Up to 2,500 elements can be tracked by a location server. This total value plus the current number of elements being tracked appears on the Advanced Parameters page. A major alert appears when the 2,500 limit is met.

Path: Location > Location Server > Administration > Advanced Parameters

Cisco UDI (NEW Advanced Parameter)

You can view the product identifier, version identifier, and serial number for a location server on the Advanced Parameters page. These values are unique to each location appliance.

Path: Location > Location Server > Administration > Advanced Parameters

Import and Export of Asset Information (NEW Administration Parameters)

You can import asset information stored in a flat text file into a location server. Information imported in the file must be in the following format: #Class, MAC Address, Asset Category, Asset Group, Asset Name.

Exported information is stored in the same format. You can name the file or keep the default file name of assets.out.

Path: Location > Location Server > Administration > Import Asset Information OR Export Asset Information

Display Contributing Access Points for Client and Tag Locations (NEW Monitor Parameters)

Client and Tag location can be monitored with respect to the access point that generated the signal. Strength of the access point signal and age of the last reading is also reported. This expanded information for clients and tags is available on the map page. To view, pass the mouse over the relevant client or tag. To enable, check the Location Debug option box found on the Tag Properties and Client Properties pages.

Path: Monitor > Devices > Tag OR Client

---

Note Additional information is available in the "Monitoring Clients" and "Monitoring Tagged Assets" sections of Chapter 7 in the Cisco Location Appliance Configuration Guide.

---

Display Last Detected Information for Clients and Tags with Filtering Option (NEW Monitor Parameters)

You can set how often the location server updates its client and tag location information from their respective summary pages. Information updates can be as often as every 5 minutes.

To initiate this option for tags, you would select the desired polling frequency from the Last Detected Within menu.

---

Note You can also define which tags are polled by defining additional search criteria such as location server, asset name or floor area via the Search for Tags by menu.

---

To initiate this option for clients, you would select the desired polling frequency from the Load Location Server data as old as menu.

---

Note You can define which clients are polled by defining additional search criteria such as location server, user name, MAC address or floor area via the Search for Clients by menu.

---

Path: Monitor > Devices > Tag OR Client

---

Note Additional information is available in the "Monitoring Clients" and "Monitoring Tagged Assets" sections of Chapter 7 in the Cisco Location Appliance Configuration Guide.

---

Inspecting Location Readiness and Location Quality (NEW Monitor Parameters)

You can configure Cisco WCS to verify the ability of the existing access point deployment to estimate the true location of an element within 10 meters at least 90% of the time. The location readiness calculation is based on the number and placement of access points.

You can also check the location quality and the ability of a given location to meet the location specification (10 m, 90%) based on data points gathered during a physical inspection and calibration.

Inspecting Location Readiness Using Access Point Data:

You would select Inspect Location Readiness from the menu found at the top-right of the Monitor>Maps page. A color-coded map appears showing those areas that do (Yes) and do not (No) meet the 10 meter, 90% location specification.

Path: Monitor > Maps

Inspecting Location Quality Using Calibration Data:

After completing a calibration model based on data points generated during a physical tour of the area, select the appropriate RF Calibration Model from the menu at the top-right of the Monitor>Maps page. Then select the Inspect Location Quality link found on the page that appears.

Path: Monitor > Maps

Deployment Planning for Data, Voice, and Location (NEW Monitor Parameter)

You can calculate the recommended number and location of access points based on whether data, and/or voice traffic is active, and/or location is considered. Use the Planning Mode option on the Maps page to begin the access point calculation.

Path: Monitor > Maps

Analyzing Element Location Accuracy Using Testpoints (NEW Location and Monitor Parameter)

You can analyze the location accuracy of rogue and non-rogue clients and asset tags by entering testpoints on an area or floor map. You can use this feature to validate location information generated either automatically by access points or manually by calibration. Refer to Chapter 5 of the Cisco Wireless Control System Configuration Guide, Software Release 4.0 for more details.

Path: Location > Location Servers > Advanced Parameters and Monitor > Maps

Caveats

This section lists open and resolved caveats in location appliance release 2.1.42.0.

Open Caveats

The following caveats are open (unresolved) in this release (2.1.42.0):

•CSCsc09186—When you perform a location calibration, the process of taking data points can take up to one minute per point if a single controller is unreachable.

Workaround: Verify that controllers are reachable during calibration or remove those controllers that are not accessible.

•CSCsc39959—An element search by MAC address or asset information may not reflect all elements seen in maps and summary lists, when operating with a release 3.2 WCS and release 1.x location appliance.

Workaround: Upgrade the location appliance to release 2.0 or greater.

•CSCsd36689—Access points in monitor mode do not detect probing clients as accurately as they do when in local mode. These access points do not track the clients' RSSI values.

Workaround: Operate in local mode for the most accurate operation, if possible.

•CSCse13406—On rare occasions, when multiple users are collecting data points for calibration, a user attempting to add a data point may see the map image vanish when WCS is resident on a Windows OS machine. The following error message may appear, "Unexpected inability to imwrite calmodel progress image." This is a cosmetic issue only. This caveat does not affect functionality.

Workaround: Navigate back to the calibration model and click save again. You can then continue to add datapoints.

•CSCse34650—After performing a calibration using a CCX compatible client on a floor with multiple controllers, it has been observed that some access points do not contribute enough calibration data points. This inaccuracy may be reflected on the Location Inspector quality accuracy page.

Workaround: There is no known workaround.

•CSCse60657—In campus environments of 60 buildings or more with multiple-floors, some synchronization errors may occur on the location appliance given the number of image (floor) transfers. (Location appliances are limited to 30 MB for each message transfer.)

Workaround: Limit the number of buildings assigned to each Campus structure.

•CSCse76666—When a location server is synchronizing with WCS and both polling and location calculation activities are active, a location appliance may go into a state in which no location calculations can occur. This intermittent condition can also happen when a heat map is generated. The condition does not occur if polling is turned "off."

Workaround: To prevent this condition from occurring, do the following:

(1) Turn OFF all polling.

(2) Wait for a few minutes, as close to the actual polling interval as possible. (This allows ongoing polling and calculation threads time to finish processing).

(3) Proceed with the synchronization operation.

(4) Turn ON polling. (Continued on next page)

If you are unable to prevent the condition from occurring, restart the location appliance.

•CSCse76683—Once the 2,500 limit of supported elements for the location appliance is met, no new location calculations are reported for any element beyond the 2,500 limit. Location calculations are reported once an element within the recognized 2,500 elements ages out. This condition occurs even when polling is turned "off."

Workaround: Adjust the Prune Data Interval (History Parameters) to prune recognized elements. Once pruning occurs, reset the Prune Data Interval to its previous value.

•CSCse76793—In some situations, the antenna name may not appear when you pass a mouse over a given access point on a map even though it does appear on the Position AP page.

Workaround: Choose a different name to the antenna and then the correct name and then select Save.

•CSCsg33783—You must change the default root password during initial configuration of the location appliance to ensure optimum network security.

–For releases 2.1.34 and later, you are prompted to change the password during the setup script.

–You can also change the password using the Linux command, "passwd."

Workaround: None.

Resolved Caveats

The following caveats are resolved in this release (2.1.42.0):

•CSCsg44373—Calibration was failing because WCS was receiving an erroneous RSSI value of positive (+)127 from the controller. WCS now filters out all RSSI values greater than or equal to zero (0).

•CSCsg67865—Previous to this release, the start and stop dates of daylight savings time (DST) for 2007 were reflected inaccurately in the Java Runtime Environment (JRE) in the location appliance due to a recent United States mandate. In 2007, DST within the US will begin on the second Sunday in March and end on the first Sunday in November. A mandatory upgrade to release 2.1.42.0 which incorporates support for this new DST period is required to prevent incorrect time reporting during certain periods of DST. Specifically, not upgrading to your location appliance to version 2.1.42.0 or later will result in incorrect time reporting from March 11, 2007 through April 2, 2007 and from October 29, 2007 through November 4, 2007.

•CSCsg68493—Previous to this release, the location appliance exposed an incorrect API call that could be exercised by a partner application extracting maps and resulted in a performance impact. In some circumstances, frequent exercise of map extraction in large access point networks (1200+ access points) could halt the location appliance and make it unresponsive.

•CSCsg83691—Previous to this release, after completion of a full calibration, data point icons would display as generic icons instead of the recognized data point icon. This was seen when location quality was queried (Path: Inspect Location Quality > Calibration Model > Floor).

•CSCsg93752—Previous to this release, older versions of floor hierarchies that were stored in the memory cache of the location appliance were not cleared appropriately after their deletion or after resynchronization with WCS. This resulted in the display of older floor hierarchies on the element detail page of WCS.

The following caveats were resolved in earlier 2.1.x releases:

•CSCsc64772—Previous to this release, when aggressive polling or historical parameters were configured for the location server, such as polling for all element categories every 10 seconds and saving history points every minute, database operations would take longer to complete, and the server momentarily took longer to respond to requests.

•CSCsd03171—Previous to this release, enabling the Advanced Debug option caused the communication setting to reset to the default HTTP setting even when configured for HTTPS.

•CSCsd05107—Previous to this release, conducting a client search using the 802.11b/g protocol filter would list 802.11b users but not 802.11g users.

•CSCsd05623—Previous to this release, if the customer lost the root password for the location appliance, there appeared to be no documented password recovery.

This issue was addressed by adding specific documentation in the 2.048.0 and 2.1.34.0 location appliance release notes and onward and in the location appliance configuration guide (June 2006 and onward.)

•CSCsd29958—Previous to this release, if you modified SNMP access for a controller via WCS and pushed the changes to the location server, the changes did not take effect until you either restarted the location server or unassigned and reassigned the controller to the location server on the synchronization page.

•CSCsd91565—Previous to this release, the total count of installed 802.11 b/g clients displayed on the Client Summary page but did not display on the floor summary page (Monitor>Map).

•CSCsd95125—Previous to this release, the Client list would display the client on the correct floor; however, the mini-map would display the client on a different, incorrect floor. Links to the client's resident floor were also incorrect.

•CSCsd95144—Previous to this release, Location History would often report an incorrect 802.11 state for clients in the Location History table and in the Client Details page when you changed from associated to disassociated.

•CSCse12576—Previous to this release, during the calibration procedure, a CCX v.2 or later compatible client was recommended to take advantage of the latest features. Additionally, the Aironet information element (IE) option had to be enabled on the controller and the wireless LAN on which the client would communicate. If the Aironet IE option was disabled, the calibration procedure often did not generate sufficient data.

•CSCse22079—Previous to this release, you could not delete datapoints added during the calibration procedure.

•CSCse43442—Previous to this release, a logical condition prevented release of internal resources and threads would block up to two minutes when they logged errors. Errors logged included: (1) access points detected by controllers that were not yet assigned to maps; and (2) controllers synchronized for areas that had no maps or unsynchronized maps. The increased blocking time associated with error logging, increased the time required for location calculations and resulted in more infrequent location calculations and delayed information in the user interface and API.

If You Need More Information

If you need information about a specific caveat that does not appear in these release notes, you can use the Cisco Bug Toolkit to find caveats of any severity. Click this URL to browse to the Bug Toolkit:

http://tools.cisco.com/Support/BugToolKit/

(If you request a defect that cannot be displayed, the defect number might not exist, the defect might not yet have a customer-visible description, or the defect might be marked Cisco Confidential.)

Troubleshooting

For the most up-to-date, detailed troubleshooting information, refer to the Cisco TAC website at http://www.cisco.com/cisco/web/support/index.html. Click Technology Support, choose Wireless from the menu on the left, and click Wireless LAN.

Documentation Updates

Software Documentation

The following information is missing in the latest Cisco Location Appliance Configuration Guide.

Using HTTPS or Non-Default Ports

When you have a non-default port or HTTPS turned on, you must pass the correct information along with the command. For example, getserverinfo must include -port <<port>> -protocol <<HTTP/HTTPS>>. Similarly, for stopping the server, stoplocserver - port <<port>> -protocol <HTTP/HTTPS>>.

Configuring NTP Server

You can configure NTP servers to set up the time and date of the 2700 location appliance.

The /etc/ntp.conf file is the main configuration file in which you place the IP addresses or DNS names of the NTP servers you want to use (see the following example).

server ntp.mydomain.com # my corporate NTP

server 192.168.2.5 # my second NTP

To get NTP configured to start at bootup, enter the following:

[root@loc-server1]# chkconfig ntpd on

To start, stop, and restart NTP after booting, follow these examples:

[root@loc-server1]# service ntpd start

[root@loc-server1]# service ntpd stop

[root@loc-server1]# service ntpd restart

After configuring and starting NTP, make sure it is working properly. To test whether the NTP process is running, use the following command:

[root@loc-server1]# pgrep ntpd

You should get a response of plain old process ID numbers.

Enter the ntpdate -u<serverIP> command to force your server to become instantly synchronized with its NTP servers before starting the NTP deamon for the first time (see the following example).

[root@loc-server1]# service ntpd stop

[root@loc-server1] ntpdate -u 192.168.1.100

Looking for host 192.168.1.100 and service ntp

host found: ntpl.my-site.com

12 Aug 08:03:38 ntpdate[2472]: step time server 192.168.1.100 offset 28993.084943 sec

[root@smallfry tmp]# service ntpd start

---

Note For more information on the NTP configuration, consult the Linux configuration guides.

---

Related Documentation

The following documents are related to location appliances:

•Cisco 2700 Series Location Appliance Installation and Configuration Guide

•Cisco Location Appliance Configuration Guide

•Cisco Wireless Control System Configuration Guide

•Cisco Wireless LAN Controller Command Reference

---

Note You can see the latest online versions of these documents at http://www.cisco.com/en/US/products/ps6386/tsd_products_support_series_home.html

---

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.

---

Cisco and the Cisco Logo are trademarks of Cisco Systems, Inc. and/or its affiliates in the U.S. and other countries. A listing of Cisco's trademarks can be found at www.cisco.com/go/trademarks. Third party trademarks mentioned are the property of their respective owners. The use of the word partner does not imply a partnership relationship between Cisco and any other company. (1005R)

Copyright © 2007 Cisco Systems, Inc. All rights reserved.

---

.