After replacing UCSC-C220-M5SX, it does not boot to OS, it boots to shell

After replacing UCSC-C220-M5SX, it does not boot, it boots to shell

After replacing UCSC-C220-M5SX

it boots to EFI shell

Resolution step:

on the BIOS, boot option I set to Boot Mode Legacy

but on the Boot Option, it does not appear Local HDD

Go to CIMC

Configuring the Server Boot Order

Before You Begin

You must log in as a user with admin privileges to configure server boot order.

Procedure

Step 1

In the Navigation pane, click the Server tab.

Step 2

On the Server tab, click BIOS.

The BIOS page appears.

Step 3

In the Actions area, click Configure Boot Order.

A dialog box with boot order instructions appears.

Step 4

Review the instructions, and then click OK.

The Configure Boot Order dialog box displays.

Step 5

In the Configure Boot Order dialog box, update the following properties:

Name	Description
Device Types table	The server boot options. You can select one or more of the following: HDD—Hard disk drive FDD—Floppy disk drive CDROM—Bootable CD-ROM PXE—PXE boot EFI—Extensible Firmware Interface
Add >	Moves the selected device type to the Boot Order table.
< Remove	Removes the selected device type from the Boot Order table.
Boot Order table	Displays the device types from which this server can boot, in the order in which the boot will be attempted.
Up	Moves the selected device type to a higher priority in the Boot Order table.
Down	Moves the selected device type to a lower priority in the Boot Order table.
Apply button	Saves the changes to the configured boot order or reapplies a previously configured boot order. CIMC sends the configured boot order to the BIOS the next time the server is rebooted.
Cancel button	Closes the dialog box without saving any changes or reapplying the existing configuration. If you select this option, the actual boot order will not be changed the next time the server is rebooted.

Step 6

Click Apply.

Additional device types may be appended to the actual boot order, depending on what devices you have connected to your server.

Select Compute -> BIOS -> Configure Boot Order -> configure boot order -> add HDD

save, reset, all good

it boots to OS

Comments

Cisco UCS C Rack version CIMC issue with adobe flash player end of life

Issue: can not open CIMC in the browser due to Adobe Flash no longer supported it affecting firmware ver 2.x Workaround: Uninstall current flash and Firefox, use flash_player 22.exe with Firefox ver 45 You can download it from here https://drive.google.com/drive/folders/1oSoNuoCevCx00tQfT0eJLwaBEegmWJwE next step: upgrade the firmware to ver3.x above NOTE: 2.0.4c and above you should be able to upgrade to 3.0.3f or 3.0.4 easily then you can goto 4.0 or 4.1 as required Don't upgrade to 3.0.3a, this version have a bug ver 3.x above using HTML5 After firmware upgraded: you need to download and install the latest Firefox that support HTML5 Firmware upgrade matrix https://www.cisco.com/c/dam/en/us/td/docs/unified_computing/ucs/c/sw/CIMC-Upgrade-Downgrade-Matrix/index.html =============================================================== Workaround 2: Run power shell script on FE laptop: Change IP, username and password on the script, before you run it Script: $cimcIP = &

Upgrade Software On A Cisco Catalyst 3850 Series Switch Stack

Upgrade Software On A Cisco Catalyst 3850 Series Switch Stack Set a new SW#1 as stand alone copy bin file using usb copy usbflash0:xxxxx.bin flash: New-SW01#request platform software package install switch all file flash:cat3k_caa-universalk9ldpe .16 .03 .08 .SPA.bin new auto-copy New-SW01#reload New-SW01# request platform software package clean connect the stack cable

Recovering Fabric Interconnects When You Do Not Have Working Images on The Fabric Interconnect or The Bootflash

Recovering Fabric Interconnects When You Do Not Have Working Images on The Fabric Interconnect or The Bootflash You can perform these steps when both or any fabric interconnect goes down during firmware upgrade, gets rebooted, and is stuck at the loader prompt, and you do not have working images on the fabric interconnect. Procedure Step 1 Reboot the switch, and in the console, press Ctrl+L as it boots to get the loader prompt. Note You may need to press the selected key combination multiple times before your screen displays the loader prompt. Example: loader> Step 2 Configure the interface to receive the kickstart image through TFTP. Enter the local IP address and subnet mask for the system at the loader> prompt, and press Enter . Example: loader> set ip 10.104.105.136 255.255.255.0 Specify the IP address of the default gateway. Example: loader> set gw 10.104.105.1 Boot the kickstart image file from the required server. Example: loader> boot tftp://10.104.10

Cisco Problem and Solution

Search This Blog