Table Of Contents
Release Notes for Cisco Network Positioning System Release 1.0
Obtaining Documentation and Submitting a Service Request
Release Notes for Cisco Network Positioning System Release 1.0
Last Updated: January 18, 2012Text Part Number: OL-25798-01These release notes describe the requirements for running Cisco Network Positioning System (NPS) on the Cisco ASR 1000 Series routers.
Contents
These release notes contain these sections:
Introduction
Cisco NPS enables consumers of cloud services to select the optimal Data Center for service delivery. Cisco NPS leverages policy-driven engines to make this selection based on network proximity, latency, packet loss, and data center capabilities.
These components are supported in Release 1.0:
•
Performance Manager (PFM)
•
•
•
System Requirements
This section describes the system requirements for Cisco NPS support on the Cisco routers. It includes this information:
Hardware Supported
Cisco NPS is supported on the Route Processor 2 (RP2) on these Cisco ASR 1000 Series Router chassis types:
•
•
•
•
Note
Memory Requirements
The minimum memory requirements for Cisco NPS running on a Cisco ASR 1000 router are:
•
•
Minimum Software Versions
For information about Cisco IOS XE on the Cisco ASR 1000 Series Routers, refer to the Release Notes for Cisco ASR 1000 Series Aggregation Services Routers for Cisco IOS XE Release 3.5S at:
http://www.cisco.com/en/US/products/ps9343/prod_release_notes_list.html
New and Changed Information
This is the first release of Cisco NPS on Cisco ASR 1000 routers.
Installation Notes
For information about installing NPS software on ASR 1000 routers, refer to Cisco Network Positioning System Installation on Cisco ASR 1000 Routers at:
http://www.cisco.com/en/US/products/ps9343/products_installation_and_configuration_guides_list.html
Caveats
These open caveats apply to Cisco NPS Release 1.0 on Cisco ASR 1000 Routers:
•
Basic Description:
Some show commands do not show "More" correctly.
Symptom:
"More" lines are not shown correctly on VM.
Conditions:
This issue occurs when output exceeds one page, and the "More" option is given at the bottom of the page.
Workaround:
No workaround.
•
Basic Description:
cd xmpp password change does not go through.
Symptom:
CD is unable to connect to the XCP/Jabber server after attempting to change the password.
Conditions:
This issue only occurs if the user tries to change the password while keeping the username the same.
Workaround:
While this CLI should be rarely used, the user can change the username along with the password.
•
Basic Description:
nps-pxe: After executing show proximity ip route, exec debug commands give same output
Symptom:
Remnants of the show proximity ip route command are seen when you execute debug commands.
Conditions:
This issue occurs sometimes under high scale conditions, when one executes a debug command after breaking the show proximity ip route command at -more-.
Workaround:
Let the show proximity ip route command be executed completely.
•
Basic Description:
CD process is unable to connect to Jabber server after DNS configuration.
Symptom:
After switching from static mapping of hostname to ip address to using a nameserver, the CD process cannot connect to the Jabber server.
Conditions:
This issue occurs when you switch config as in the following example:
from:
ip host ccnsr.com 26.0.0.2
to:
ip nameserver 11.0.0.2
Workaround:
Create a static resolution for the local host and reconnect.
•
Basic Description:
NPS: seeing "monit[606]: `smmd' process is not running" on IOS console.
Symptom:
"monit[600]: `smmd' process is not running" a message printed in IOS console log when activating virtual-instance.
Conditions:
This issue occurs when logging console is enabled and virtual-instance is activated.
Workaround:
None.
•
Basic Description:
NPSSRE: SRE process fails clear service-resolution statistics under stress
Symptom:
SRED gives the following error, and the SRED process fails:
trap divide error rip:4108df rsp:7fffe2659ee0 error:0Conditions:
Requests must be sent at the rate of 10 requests per second. The SRE must require both PXE and PFM resolution. DCs must be advertised using XMPP.
Workaround:
None.
•
Basic Description:
At 10 requests per second, some POST requests get a 400 response 20 seconds later.
Symptom:
NPS returns a 400 Bad Message final response with a previously buffered ranked DC list in response to a POST request 20 seconds after the POST request is sent.
Conditions:
Under a load of 10 requests [POST/GET] per second with Proximity as the priority algorithm and with 35 DCEs advertising, this issue is seen on 0.022% of the ITSM POST requests. Frequency of occurrence is directly related to request per second rate, and the issue is not noticed at or below two requests [POST/GET] per second.
Workaround:
ITSM should drop the POST request if a 202 accepted is not received within 15 seconds and retry the request again. If ITSM receives the 400 Bad Message HTTP header but with a ranked list, it should ignore it.
Related Documentation
For more information about Cisco NPS, refer to these documents:
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 an RSS feed and set content to be delivered directly to your desktop using a reader application. The RSS feeds are a free service. Cisco currently supports RSS Version 2.0.
This document is to be used in conjunction with the documents listed in the "Related Documentation" section.
Cisco and the Cisco logo are trademarks or registered trademarks of Cisco and/or its affiliates in the U.S. and other countries. To view a list of Cisco trademarks, go to this URL: 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. (1110R)
Any Internet Protocol (IP) addresses and phone numbers used in this document are not intended to be actual addresses and phone numbers. Any examples, command display output, network topology diagrams, and other figures included in the document are shown for illustrative purposes only. Any use of actual IP addresses or phone numbers in illustrative content is unintentional and coincidental.
© 2011-2012 Cisco Systems, Inc. All rights reserved.
