Network Plug and Play Troubleshooting Guide for Cisco Digital Network Architecture Center, Release 1.2.x

 

First Published: February 15, 2019

 

The Cisco Network Plug and Play (PnP) feature in Cisco DNA Center provides a simple, secure way to deploy network devices for branch or campus networks. This document provides detailed steps to troubleshoot issues you may encounter during device onboarding using Cisco DNA Center release 1.2.x and PnP. 

 

 

Contents

Device States Supported in PnP, Cisco DNA Center v1.2.x. 3

Device Troubleshooting Commands. 4

Device Cleanup to Manufacturing Default State. 6

Troubleshooting from the Cisco DNA Center GUI 6

Collecting PnP Logs from Maglev. 7

 

Device States Supported in PnP, Cisco DNA Center v1.2.x

The following table lists the main device states that a device goes through during onboarding.

 

The following table lists all the sub-states a device goes through during onboarding. By default, the “Onboarding State” column is not shown in the device list and it can be added as shown below.

 

 

 

Device Troubleshooting Commands

You can use the following CLI commands to troubleshoot device onboarding issues.

 

 

Cisco network devices to be deployed must be in a factory default state. If you are using a network device that was previously configured or is in an unknown state, you must reset it to the factory default condition.

Device Cleanup to Manufacturing Default State

If you are using a Cisco router or switch that was previously configured or is in an unknown state, execute the following CLI commands to reset the device to the factory default condition:

If you are using a Cisco Aironet 3700, 3600, 2700, 2600, 1700, 1600, or 700 Series Access Point device that was previously configured or is in an unknown state, execute the following CLI commands to reset the device to the factory default condition:

If you are using a Cisco Aironet 3800, 2800, or 1800 Series Access Point device that was previously configured or is in an unknown state, execute the following CLI commands to reset the device to the factory default condition:

To view active connections for the Cisco Plug and Play IOS Agent:

If needed, you can enable debug information and capture the output for the Cisco Plug and Play IOS Agent as follows:

Troubleshooting from the Cisco DNA Center GUI

If a device ends in an error state or you want to look at the history, click on a device and then click the History tab. Most of the errors should be available there. You can click on Info to find additional information such as syntax errors.

 

Collecting PnP Logs from Maglev

Log Levels

Change the logging level to Debug. By default, the log level in Cisco DNA Center is Info. If you want to change the logging level and collect the logs, use System Settings > Settings > Debugging Logs. Change both connection-manager-service and onboarding-service to the Debug logging level.

 

Collecting All Maglev Logs

You can collect all cluster logs from Maglev using the rca command

1.     Login to your cluster.

ssh maglev@controller-ip-address -p 2222

2.   Run the rca command.

rca

This will generate a file like /data/rca/maglev-192.0.2.11-rca-2018-04-09_23-12-00_UTC.tar.gz. This file can be about ~200 MB

3.     Copy it with scp it to your local folder.

scp -P 2222 maglev@controller-ip-address:/data/rca/maglev-192.0.2.11-rca-2018-04-09_23-12-00_UTC.tar.gz ~/Downloads

4.     Once in your local folder, untar this file.

tar -xvf maglev-192.0.2.11-rca-2018-04-09_23-12-00_UTC.tar.gz

This creates a folder called data.

5.     CD to the folder.

cd data/rca/maglev-192.0.2.11-rca-2018-04-09_23-12-00_UTC

6.     Untar the file var-log.tar.gz.

tar -xvf var-log.tar.gz

This creates a folder called var.

7.     CD to var/log/containers, which contains the service logs. For example, the onboarding service logs can be a file (the name is based on service name and container ID) such as onboarding-service-1502674267-xdtjv_fusion_onboarding-service-395ff66e199c0a5797358d03a963b9612a6320c99857394ef27e588959c8a72a.log

 

 

 

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.

© 2019 Cisco Systems, Inc. All rights reserved.