Cisco UCS 6120XP
Start the console session.
Plug in serial cable to console port of device from PC COM1 port
Open PuTTY and select "Serial" connection type, leave baud rate (Speed) and other settings as default.
Plug power into device and if a power button exists, turn it on.
Boot to the command prompt.
As the device starts up, repeatedly press Ctrl L until the loader> prompt appears, then type the dir command:
User break with default console settings
Loader Version pr-1.3
loader> dir
bootflash:
span.log
ucs-6100-k9-kickstart.4.0.1a.N2.1.2j.bin
ucs-6100-k9-system.4.0.1a.N2.1.2j.bin
sysdebug
chassis.img
nuova-sim-mgmt-nsg.0.1.0.001.bin
pnuos
installables
cisco_nexus_1000v_certificate.pem
distributables
initial_setup.log
.tmp-kickstart
.tmp-system
mts.log
vdc_2
vdc_3
vdc_4
vms_cert_store
bootflash
distributables_hdr
cores
license
received
TZ_DATA.DAT
techsupport
chassis2.img
fexth.bin
backup
externalrep
Type boot followed by the filename with kickstart in it shown above in blue:
loader> boot ucs-6100-k9-kickstart.4.0.1a.N2.1.2j.bin
Booting kickstart image: ucs-6100-k9-kickstart.4.0.1a.N2.1.2j.bin....
........................................................................Image v
erification OK
Starting kernel...
Usage: init 0123456SsQqAaBbCcUu
INIT: version 2.85 booting
Starting UCS6120XP POST...
Further output will bring you to the switch(boot)# prompt.
Set a new password for the admin username and log in with those credentials.
Type the config terminal command:
switch(boot)# config terminal
Enter configuration commands, one per line. End with CNTL/Z.
Type the admin-password Passw0rd123 command, then press Ctrl Z or type the exit command:
switch(boot)(config)# admin-password Passw0rd123
switch(boot)(config)# exit
switch(boot)#
Power cycle the device and enter admin for the login and Passw0rd123 for the password when prompted:
System is coming up ... Please wait ...
Cisco UCS 6100 Series Fabric Interconnect
s-ucsfi-1-B login: admin
Password: Passw0rd123
Cisco Nexus Operating System (NX-OS) Software
TAC support: http://www.cisco.com/tac
Copyright (c) 2009, Cisco Systems, Inc. All rights reserved.
The copyrights to certain works contained in this software are
owned by other third parties and used and distributed under
license. Certain components of this software are licensed under
the GNU General Public License (GPL) version 2.0 or the GNU
Lesser General Public License (LGPL) Version 2.1. A copy of each
such license is available at
http://www.opensource.org/licenses/gpl-2.0.php and
http://www.opensource.org/licenses/lgpl-2.1.php
Further output will bring you to the s-ucsfi-1-B# prompt.
Erase the configuration and reboot.
Type the connect local-mgmt command:
s-ucsfi-1-B# connect local-mgmt
Type the erase configuration command and type yes to confirm:
s-ucsfi-1-B(local-mgmt)# erase configuration
All UCS configurations will be erased and system will reboot. Are you sure?
(yes/no):yes
Removing all the configuration. Please wait....
/bin/rm: cannot remove directory `/bootflash/sysdebug//tftpd_logs': Device or resource busy
sudo: cannot get working directory
sudo: cannot get working directory
Configurations are cleaned up. Rebooting....
Allow the device to restart.
2022 Jul 5 03:22:53 s-ucsfi-1-B %$ VDC-1 %$ %PFMA-2-PFM_SYSTEM_RESET: Manual system restart from Command Line Interface
[ 811.287561] Shutdown Ports..
[ 811.321941] writing reset reason 9,
2022 Jul 5 03:22:55 s-ucsfi-1-B %$ VDC-1 %$ Jul 5 03:22:55 %KERN-0-SYSTEM_MSG: [ 811.287561] Shutdown Ports.. - kernel
2022 Jul 5 03:22:55 s-ucsfi-1-B %$ VDC-1 %$ Jul 5 03:22:55 %KERN-0-SYSTEM_MSG: [ 811.321941] writing reset reason 9, - kernel
INIT: Sending processes the TERM signale Jul 5 03:23:00 2022):
Sending all processes the TERM signal...
Sending all processes the KILL signal...
Saving random seed:
Syncing hardware clock to system time WARNING from hwclock: The clock was in 11 minute mode, which normally means that something else, possibly an NTP daemon, has been setting the hardware clock. Setting the clock with hwclock turns off 11 minute mode. See hwclock documentation.
Unmounting file systems: umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
Unmounting file systems (retry): umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
/var/tmp: c
umount2: Device or resource busy
umount: /var/tmp: device is busy
umount2: Device or resource busy
umount: /var/tmp: device is busy
mount: you must specify the filesystem type
mount: /var not mounted already, or bad option
Please stand by while rebooting the system...
[ 858.200468] Restarting system.
Copy all the output from the session into your records.
Right-click PuTTY's titlebar, from that dropdown menu click on "Copy All to Clipboard"
Open the file of record certifying the deconfiguration of this device and use CTRL V to paste all the output from PuTTY into that file. Formatting the text with a fixed-width font helps it look more readable.
End the session.
Close PuTTy.