The documentation set for this product strives to use bias-free language. For the purposes of this documentation set, bias-free is defined as language that does not imply discrimination based on age, disability, gender, racial identity, ethnic identity, sexual orientation, socioeconomic status, and intersectionality. Exceptions may be present in the documentation due to language that is hardcoded in the user interfaces of the product software, language used based on RFP documentation, or language that is used by a referenced third-party product. Learn more about how Cisco is using Inclusive Language.
Release Notes for Cisco Plug and Play Connect, Release 1.0x
What’s New in June 2018 Release
What’s New in July 2017 Release
Supported Platforms and Software Requirements
Enhanced Capabilities with Cisco IOS XE Everest 16.5.1
Redirecting a Device That Has Been Assigned a Loopback Profile
Communications, Services, and Additional Information
These release notes apply to the following software releases of Cisco Plug and Play Connect:
■General Availability Release 1.0
These release notes contain the following sections:
■What’s New in June 2018 Release
■What’s New in July 2017 Release
■Supported Platforms and Software Requirements
■Redirecting a Device That Has Been Assigned a Loopback Profile
The Cisco Plug and Play Connect cloud service works with your Smart Account and the Cisco Plug and Play solution to provide automatic plug and play server discovery when other methods such as DHCP or DNS are not available. A Cisco network device contacts the Plug and Play Connect cloud service to obtain the IP address of the appropriate plug and play server that is defined for your organization. The Plug and Play Connect web portal is linked to Cisco Commerce Workspace (CCW), facilitating automatic registration of the serial numbers and PIDs of purchased devices in Plug and Play Connect, and these can then be synced to Plug and Play in the Cisco DNA Center or APIC-EM controller. For more information, see the Plug and Play Connect website:
Cisco Plug and Play Connect requires a Smart Account during device procurement. Simply assign a Smart Account when you order eligible products with Cisco Plug and Play in CCW.
The Cisco Plug and Play Connect cloud service integrates with Cisco DNA Center 1.2 and later.
The beta feature that previously allowed you to optionally associate a device with a configuration or configuration template has been removed.
Users with Virtual Account Admin and Virtual Account User roles have access to all of the Cisco Plug and Play Connect cloud service functionality. Previously, only Smart Account Admins had access.
Note: The Click to Accept agreement can be accepted only by users with the Smart Account Admin role.
The following tables list Cisco routers, switches, wireless access points, NFVIS platforms, and minimum software releases that support Cisco Plug and Play Connect.
CSR 1000V 2
Note: Only official software releases obtained from the Cisco.com software download website are supported for image deployment. Engineering builds are not supported.
For Cisco network devices running Cisco IOS XE Everest 16.5.1 or later, Plug and Play Connect can take advantage of additional capabilities built into the Plug and Play IOS Agent in the device, as follows:
■Support for standard and non-standard HTTP/HTTPS ports. Earlier releases support only the standard ports of 80/443.
■Support for certificate installation to initialize an HTTPS connection to an on-premises APIC-EM controller. Earlier releases do not support certificate installation.
■Support for both primary and secondary controllers in the PNP profile for redundancy (designed for Network Services Orchestrator). Earlier releases support only a primary controller.
■Network devices contact the Plug and Play Connect service every 10 minutes to get controller information. Network devices with earlier releases contact the Plug and Play Connect service every 3 minutes.
If a device in the Plug and Play Connect portal is not associated with any controller profile or configuration within 24 hours of its first contact with the portal, the device is deemed as not intended for using Plug and Play Connect and is assigned a loopback profile (127.0.0.1) by the portal.
If you want to redirect this device to a controller later, follow these steps:
1. Define a controller profile in the Plug and Play Connect portal.
2. Associate the device with that controller profile.
3. Reset the device to a factory default state.
4. Reload the device to cause it to recontact the Plug and Play Connect portal, where it will be redirected to the specified controller. Note that the reload is included in the reset procedures linked in Step 3.
■ Plug and Play Connect website —Documentation for Plug and Play Connect.
■ Release Notes for Cisco DNA Center —Release Notes for Cisco DNA Center.
■ Cisco DNA Center User Guide (Release 1.2 and later)—For Release 1.2.8 and later, see the “Provision Your Network” chapter for information on how to use Plug and Play in Cisco DNA Center to onboard devices. For Releases 1.2 through 1.2.7, see the “Network Plug and Play” chapter.
■ Other Cisco DNA Center documentation —For all other Cisco DNA Center documentation.
■ Release Notes for Cisco Network Plug and Play —Release Notes for Cisco Network Plug and Play on APIC-EM.
■ Solution Guide for Cisco Network Plug and Play —Solution Guide for the Cisco Network Plug and Play solution on APIC-EM.
■ Configuration Guide for Cisco Network Plug and Play on Cisco APIC-EM —Describes how to use the Network Plug and Play application in the APIC-EM to configure Cisco network devices.
■ Cisco Open Plug-n-Play Agent Configuration Guide —Describes how to configure the Cisco Open Plug-n-Play Agent software application that runs on a Cisco IOS or IOS-XE device.
■ Cisco Application Policy Infrastructure Controller Enterprise Module Deployment Guide —Describes how to deploy and troubleshoot the Cisco APIC-EM controller.
■ Cisco Application Policy Infrastructure Controller Enterprise Module Configuration Guide —Describes how to configure settings for the Cisco APIC-EM controller.
■ Release Notes for the Cisco Application Policy Infrastructure Controller Enterprise Module —Release Notes for the Cisco APIC-EM.
■ Release Notes for Cisco Intelligent Wide Area Network Application (Cisco IWAN App) —Release Notes for Cisco IWAN.
■ Software Configuration Guide for Cisco IWAN on APIC-EM —Configuration Guide for Cisco IWAN.
■ Open Source Used In Cisco Plug and Play Connect —List of open source code used in the Cisco Plug and Play Connect cloud portal.
■To receive timely, relevant information from Cisco, sign up at Cisco Profile Manager.
■To get the business impact you’re looking for with the technologies that matter, visit Cisco Services.
■To submit a service request, visit Cisco Support.
■To discover and browse secure, validated enterprise-class apps, products, solutions and services, visit Cisco Marketplace.
■To obtain general networking, training, and certification titles, visit Cisco Press.
■To find warranty information for a specific product or product family, access Cisco Warranty Finder.
Cisco Bug Search Tool (BST) is a web-based tool that acts as a gateway to the Cisco bug tracking system that maintains a comprehensive list of defects and vulnerabilities in Cisco products and software. BST provides you with detailed defect information about your products and software.
THE SPECIFICATIONS AND INFORMATION REGARDING THE PRODUCTS IN THIS MANUAL ARE SUBJECT TO CHANGE WITHOUT NOTICE. ALL STATEMENTS, INFORMATION, AND RECOMMENDATIONS IN THIS MANUAL ARE BELIEVED TO BE ACCURATE BUT ARE PRESENTED WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED. USERS MUST TAKE FULL RESPONSIBILITY FOR THEIR APPLICATION OF ANY PRODUCTS.
THE SOFTWARE LICENSE AND LIMITED WARRANTY FOR THE ACCOMPANYING PRODUCT ARE INCORPORATED HEREIN BY THIS REFERENCE. IF YOU ARE UNABLE TO LOCATE THE SOFTWARE LICENSE OR LIMITED WARRANTY, CONTACT YOUR CISCO REPRESENTATIVE FOR A COPY.
The Cisco implementation of TCP header compression is an adaptation of a program developed by the University of California, Berkeley (UCB) as part of UCB’s public domain version of the UNIX operating system. All rights reserved. Copyright © 1981, Regents of the University of California.
NOTWITHSTANDING ANY OTHER WARRANTY HEREIN, ALL DOCUMENT FILES AND SOFTWARE OF THESE SUPPLIERS ARE PROVIDED “AS IS” WITH ALL FAULTS. CISCO AND THE ABOVE-NAMED SUPPLIERS DISCLAIM ALL WARRANTIES, EXPRESSED OR IMPLIED, INCLUDING, WITHOUT LIMITATION, THOSE OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT OR ARISING FROM A COURSE OF DEALING, USAGE, OR TRADE PRACTICE.
IN NO EVENT SHALL CISCO OR ITS SUPPLIERS BE LIABLE FOR ANY INDIRECT, SPECIAL, CONSEQUENTIAL, OR INCIDENTAL DAMAGES, INCLUDING, WITHOUT LIMITATION, LOST PROFITS OR LOSS OR DAMAGE TO DATA ARISING OUT OF THE USE OR INABILITY TO USE THIS MANUAL, EVEN IF CISCO OR ITS SUPPLIERS HAVE BEEN ADVISED OF THE POSSIBILITY OF SUCH DAMAGES.
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.
All printed copies and duplicate soft copies of this document are considered uncontrolled. See the current online version for the latest version.
Cisco has more than 200 offices worldwide. Addresses, phone numbers, and fax numbers are listed on the Cisco website at www.cisco.com/go/offices.
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. (1721R)