Guest

Preview Tool

Cisco Bug: CSCvs75448 - Cisco DNA Center Provisioning failure when changing hostname using template

Last Modified

Jun 03, 2020

Products (1)

  • Cisco DNA Center

Known Affected Releases

DNAC1.3.1.4

Description (partial)

Symptom:
Cisco DNA Center may report the following error on its Provisioning tab > Provisioning Status when changing the device hostname using a template.

For example -
  
Template provisioning    FAILED
Provisioning failed for the template Hostname.Message: Unable to push CLI ' Current output : Access_1A_2B_3C_4D_5F# Current expects : Access_1A_' to device x.x.x.x using protocol ssh2

Here "Access_1A_2B_3C_4D_5F" is the new hostname and "Access_1A_2B_3C_4D" is the old one.

The username gets successfully configured on the device despite the error and no error is seen on the device itself.

Conditions:
So far this has mostly been seen when using 4 or more underscores in the hostname, but the exact trigger is not known yet, and it may not be limited to just this condition.
Bug details contain sensitive information and therefore require a Cisco.com account to be viewed.

Bug Details Include

  • Full Description (including symptoms, conditions and workarounds)
  • Status
  • Severity
  • Known Fixed Releases
  • Related Community Discussions
  • Number of Related Support Cases
Bug information is viewable for customers and partners who have a service contract. Registered users can view up to 200 bugs per month without a service contract.