Can't break out of the (none)# prompt on a Nexus9000 C93108TC-EX

[macgyver0099_1]

Hi,

I am trying to upgrade and configure my Nexus9000 C93108TC-EX. However the device boots directly into some kind of sub IOS and shoots straight into a "(none)# prompt. I tried to break out of it using several different methods found on the Internet, as well as attempting to boot from an IOS from my USB flash drive. I also tried a procedure I found that encompassed the below commands to no avail.

(none)# dir bootflash (none)# setup-bootvars.sh <aci_image.bin>

My question, therefore, is what do I need to do to get this thing to regular configuration mode so I can upgrade the IOS and configure it for production?

[gmonroy · Accepted solution]

macgyver0099_1,

    Could you supply a "show version" for clarification?

Also a few points:

• If you are seeing the (none) prompt and you are running an ACI code, this is expected until you join it to a fabric (requires APIC controllers).
  1. If you already have an existing ACI fabric, you can cable this specific leaf to an existing spine to begin the discovery process (assumin versions match up between the new node and the existing fabric)
  2. Once it has joined the fabric, it can be upgraded via a policy upgrade:
     1. https://www.cisco.com/c/en/us/td/docs/switches/datacenter/aci/apic/sw/2-x/managing_ACI_fabric_upgrades_and_downgrades/b_Managing_ACI_Fabric_Upgrades_and_Downgrades.html
  3. If you are unable to join it to the fabric, you should be able to break into loader (reload, then "ctrl + c" or "ctrl + ]") and boot into the later ACI Image (should have n9000 in the filename) you have on your USB. IOS images will not work on Nexus 9000 devices.
• If you are running the ACI version, there is no prompt that will allow you to perform any configuration directly from the switch node. All configuration should be done through the APIC controllers. Until the leaf is joined to an APIC controller, you will have limited control over functionality of a leaf running ACI OS.
• If you do not have any APIC controllers or are expecting this to otherwise run on standalone NXOS, follow this guide for steps to convert (similar to booting from USB drive, but pointing to an NXOS image instead of an ACI image):
  • https://www.cisco.com/c/en/us/td/docs/switches/datacenter/nexus9000/sw/6-x/upgrade/guide/b_Cisco_Nexus_9000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide_Release_6x/b_Cisco_Nexus_9000_Series_NX-OS_Software_Upgrade_and_Downgrade_Guide_Release_6x_c...

Hopefully this gives you some direction.

-Gabriel

[macgyver0099_1]

Hi,

Thanks for the info.  I was able to get to the loader> prompt, but not further.  The document seems to be at least, in part, aimed at the modular version of the Cisco Nexus 9000.  This is a standalone switch.  The version is of ACI that it is now borrowing from flash is aci-n9000-dk4.12.0.2m.bin.  I could not get it to boot the NX-OS on my flash drive.

[gmonroy]

macgyver0099_1,

    Can you clarify what your goal is? Is it to get it to a standalone NXOs version? Also you mention that it is unable to boot into the NXOS version, can you share which cmd and what the output was that you saw indicating that it would boot into the NXOS version you specified?

-Gabriel

[YanL · Accepted solution]

ACI to NXOS

keep hitting CTRL+C after a switch reload to get to loader> prompt.

then tftp is sometimes the easiest solution and you don't have to be on site:

loader>boot tftp://username@x.x.x.x/nxos7.0.3.I5.2.bin (I've seen where the BIOS is too old and you will get an image error while decompressing, then use an nxos6 version first)

I find booting from USB challenging since USB enumeration seems different per platform and I usually not on site.

syntax possibilities:

boot usb:nxos7.0.3.I5.2.bin

boot usb0:nxos7.0.3.I5.2.bin

boot usb1:nxos7.0.3.I5.2.bin

boot usb2:nxos7.0.3.I5.2.bin

If you are trying to join an ACI fabric the leaf cannot be running software higher that the controllers but could be bellow the controllers a few minor revisions. Same instructions but boot an ACI image. (ps you will have to upgrade the EPLD manually if they are not at the proper level).

• Leaf/Spine firmware/EPLD version should match the APICs before they can join a fabric. If you need to upgrade or convert to ACI manually go with version N -1 to auto upgrade EPLD with GUI.
  • apic1#bash
  • admin@apic1:~> version
  • admin@apic1:~> moquery -c firmwareCompRunning | grep -E "dn|expectedVer|version"
  • leaf1# moquery -c firmwareRunning
  • leaf1# cat /mnt/pss/installer_detail.log | grep -E "Compatibility|New-Version|FPGA"
  • leaf1# /bin/check-fpga.sh FpGaDoWnGrAdE

cheers

[macgyver0099_1]

Thank you.  This actually did the trick.  I was just attempting to apply the procedure using usb1 instead of usb2, which is how it was showing up in the directory.  Once the correct drive was identified, the procedure worked like a charm.  Thank  you for all of your assistance.

[navydivervet]

  I received a replacement 9k, which came with NXOS code. When I installed the NXACI image, it's in the bootflash as n9000-dk9.13.1.1i.bin.crdownload

I'm now stuck at the loader prompt. I'm unable to install new image, or boot, from usb, or any other method. I'm trying to install n9000-dk9.13.0.2n.bin

[YanL · Accepted solution]

did you try booting from USB or from tftp server?

loader>set ip address x.x.x.x x.x.x.x

loader>set gw x.x.x.x

loader>boot tftp://username@x.x.x.x/nxos7.0.3.I5.2.bin

or

loader>boot usbx:nxos7.0.3.I5.2.bin (x could be 0, 1, 2)

[navydivervet · Accepted solution]

Thanks so much. It was just syntax, as usb1 worked

[macgyver0099_1]

Yeah, that was the problem I had.  I didn't check to see what usb# the Nexus was using.  Once I changed it to USB2 in my case, everything worked lightning quick.

---

---

[navydivervet]

Thanks again. What steps should I take to ensure that it will boot from my new image?

[YanL]

I believe it's
leaf# setup-bootvars.sh aci-n9000-dk9.11.0.1d.bin
The firmware must be in /bootflash

[YanL]

I usually boot from one minor revision behind what I have on APIC the use the APIC to upgrade to the version I'm running in prod. This takes care of all like boot variables and epld upgrades...

[Will Phinney]

This helped me too! Thanks