Network Automation Practitioners Forum

Error during CLI discovery: Unable to find recognizable prompt. "Nexus 5548"

Go to solution
Outstanding Contributor.

Error during CLI discovery: Unable to find recognizable prompt. "Nexus 5548"

Hello ,


i am facing aproblem in discovering "Nexus 5548" in Network automation , Error during CLI discovery: Unable to find recognizable prompt. 


how to solve that ?!



Error Details:

show version  
Cisco Nexus Operating System (NX-OS) Software
TAC support:
Copyright (c) 2002-2013, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained herein are owned by
other third parties and are used and distributed under license.
Some parts of this software are covered under the GNU Public
License. A copy of the license is available at

  BIOS:      version 3.6.0
  loader:    version N/A
  kickstart: version 6.0(2)N1(1)
  system:    version 6.0(2)N1(1)
  Power Sequencer Firmware:  
             Module 1: version v3.0
             Module 2: version v1.0
             Module 3: version v2.0
  Microcontroller Firmware:        version v1.2.0.1
  QSFP uC:   Module not detected
  BIOS compile time:       05/09/2012
--More--   kickstart image file is: bootflash:///n5000-uk9-kickstart.6.0.2.N1.1.bin
  kickstart compile time:  1/29/2013 7:00:00 [01/29/2013 18:40:46]
  system image file is:    bootflash:///n5000-uk9.6.0.2.N1.1.bin
  system compile time:     1/29/2013 7:00:00 [01/29/2013 20:44:48]

  cisco Nexus5548 Chassis ("O2 32X10GE/Modular Supervisor")
  Intel(R) Xeon(R) CPU         with 8262952 kB of memory.
  Processor Board ID FOC16080FH0

  Device name: N5k02-IT-SFAC
  bootflash:    2007040 kB

Kernel uptime is 322 day(s), 22 hour(s), 48 minute(s), 48 second(s)

Last reset at 157448 usecs after  Mon Mar  4 14:33:49 2013

  Reason: Disruptive upgrade
  System version: 5.0(2)N1(1)

--More--   Core Plugin, Ethernet Plugin



Mostafa Hassan

All the best .
Mostafa Hassan
Micro Focus Expert

Re: Error during CLI discovery: Unable to find recognizable prompt. "Nexus 5548"

Hi Mustafa;


There are several reasons that NA may not be able to assign a driver to a specific device. 

One is that the device is not supported yet and we need to add that model number to the current list of supported devices.  We determine this by getting the SysOID of the device and verifying that it supported.  If it is not, then we need to open a case and fill out the driver request form.


Another reason is that NA may not be able to connect to the device properly due to special characters in the banner or one of the prompts that NA doesn't recognize and can't find what it is looking for.  If this is the case, we find out what the issue is and generate an access variable that we can set in the password rule to allow the specials characters to be ignored or processed on.


Either way, we will need some logging.  So, please do the following;


I will need you to run another driver discovery against the device

but before running the device discovery task, go to admin/troubleshooting in the WebUI and select “reset all logs to default level”, then click Submit.
In the  “enable logging for” scroll window select the following items (use the keyboard Ctrl key to highlight multiple items);

  • Device/Driver/ParseXML/Discovery
  • Device/Driver/Discovery
  • Device/Session/SNMP
  • Device/Session/Log

Then in the scroll box associated with “at level”, select “Trace (most messages)”
(check your selections, you should have the five above highlighted)
Click Submit

Go to the Discover Device Task page

Before clicking on save, checkmark “Store complete device session log” (in the Task options section) and “Store log output generated by this task”.
Click Save
Note the TaskID that shows up in the address field of the browser, you will need it later.

After the task completes, collect the logs:   
Cut and Paste the session log into a txt file.
Go to Admin->Troubleshooting and click on “Download Troubleshooting Information” link.
Check these boxes: 
"Administrative Settings"
"Wrapper logs including the last <4> historical files"
"System Status File".
In the task log section,  find the task log that contains the TaskID you noted above and select it.
Click Download
Post the in this thread.



Online outReach Resource
HP Support

The views and opinions expressed in my contributions are my own and do not necessarily reflect the views and strategy of HP

If you find that this or any other post resolves your issue, please be sure to mark it as an accepted solution.
If you are satisfied with anyone’s response please remember to give them a KUDOS by clicking on the STAR at the bottom left of the post and show your appreciation.
Outstanding Contributor.

Re: Error during CLI discovery: Unable to find recognizable prompt. "Nexus 5548"

Hello Joe ,

Thanks for your reply .
I have sorted this issue yesterday , that i have manually assigned the device driver in NA , so what i can say is that forcing the discovery with that driver and it worked fine after that ,

This issue i faced only for nexus switches OS version 6.x , i have Nexus 7009x and Nexus 5548 , and the issue was for nexus only , for other devices was straight forward while discovery .

All the best .
Mostafa Hassan