UCS how to
Contents
-
UCS how to
- Standard Shutdown procedure for UCS system
- Standard Powerup procedure for UCS system
- Recommended Order of Steps for Firmware Downgrades
- UCS initial Configuration
- Hyperflex compatibility
- UCS Platform Emulator
- How to configure Fibre Channel uplink ports on Cisco UCS 6248 fabric interconnects
- Uplink Fibre Channel Ports
- Then point a Web browser to the configured CIMC IP address.
- Downloading Firmware Images to the Fabric Interconnect from a Remote
- Activating a Capability Catalog Update
- License about
- Activating the Board Controller Firmware on a Cisco UCS B-Series M3 and M4 Rack Servers
- Directing show Command Output to a File
- Recovery from the switch(boot)# Prompt
- UCS health check report
- System Board 0 SEL_FULLNESS
- Visual Guide to collect Tech Support files (B and C series) - Cisco
- HOW TO: Upgrade Cisco UCS Manager, Fabric Interconnects, I/O Modules and
- Understanding Cisco UCS Service profile templates
- Collect logs
- Troubleshooting
Standard Shutdown procedure for UCS system
- Shutdown devices in the following order:
1. Graceful shutdown of blades
2. Disable Smart Call home (if enabled)
3. Chassis (unplug power)
4. Remove Power to Secondary FI
5. Remove power to Primary FI.
Standard Powerup procedure for UCS system
- Powerup devices in the following order:
1. plug power to Primary FI.
2. plug Power to Secondary FI
3. Chassis (plug power)
4. Enable Smart Call home (if need)
5. poweron blades
Recommended Order of Steps for Firmware Downgrades
* If you need to downgrade the firmware to an earlier release, we recommend that you do it in the following order:
- Retrieve the configuration backup from the release to which you want to downgrade. This is the backup you created when you upgraded to the current release.
- Unconfigure the features that are not supported in the release to which you want to downgrade.
- Create Full State and All Configuration backup files.
- Downgrade Cisco UCS Manager.
- Perform an erase-config.
- Import the configuration backup from the release to which you downgraded.
- Note Steps 5 and 6 are optional. Perform these steps only if the existing configuration becomes unusable. In this case, import the configuration backup either from Step 1 or Step 3.
UCS initial Configuration
https://speakvirtual.com/2013/02/08/cisco-ucs-101-installation-and-basic-config-2/
Hyperflex compatibility
https://ucshcltool.cloudapps.cisco.com/public/
1.8.1f
Cisco HX Data Platform Storage Cluster Specifications Cluster Limits: Cisco HX Data Platform supports up to 8 clusters on one vCenter. Cisco HX Data Platform supports up to 8 clusters on single HX FI Domain. Node Limits: Minimum converged nodes (per cluster): 3 Maximum converged nodes (per cluster): 8 Maximum compute-only nodes (per cluster): 8 Note It is recommended that the number of Compute-only nodes should be less than or equal to number of Converged nodes. Cisco HX Data Platform storage clusters supported nodes: Converged nodes – Hybrid: Cisco HyperFlex HX240c M4 or HX220c M4 Compute-only nodes: Cisco B200 M4, C240 M4, and C220 M4 Upgrade Guidelines  Note Cisco recommends that you upgrade to release 1.8(1f) from a previous release, unless you are running All-Flash nodes which require version 2.0 and above.
Upgrade cautions
Cautions and Guidelines Before you begin upgrade of a Cisco HyperFlex System, consider the following cautions, guidelines, and limitations. Optimizations in Capacity Tier—Backend access is optimized to significantly reduce the magnitude and frequency of high latency spikes. Important Upgrade Guidelines This upgrade is recommended for only those customers who have been identified having this problem. For hybrid clusters—The default upgrade process will not enable this optimization. Contact Cisco TAC to enable this performance enhancement during the upgrade process. Enabling this optimization will require a longer maintenance window. For All Flash clusters—The upgrade times will not be significantly affected and the default upgrade path will enable this performance enhancement. https://www.cisco.com/c/en/us/td/docs/hyperconverged_systems/HyperFlex_HX_DataPlatformSoftware/HyperFlex_upgrade_guide/2-0/b_HyperFlexSystems_Upgrade_Guide_2_0/b_HyperFlexSystems_Upgrade_Guide_1_8_c_chapter_010.html
vSwitches
By default, the "hx-vm-network" vSwitch is configured as active/active. All other vSwitches are configured as active/standby.
UCS Platform Emulator
https://developer.cisco.com/web/unifiedcomputing/home
How to configure Fibre Channel uplink ports on Cisco UCS 6248 fabric interconnects
https://jeremywaldrop.wordpress.com/2011/11/08/cisco-ucs-6248-unified-port-configuration/
Configure as FC Uplink Port. This will allow you to connect to your switching fabric.
Changing the port mode on either module causes an interruption in data traffic because changes to the fixed module require a reboot of fabric interconnect and changes on an expansion module require a reboot on that module.
Uplink Fibre Channel Ports
Uplink Fibre Channel ports handle FCoE traffic between the fabric interconnect and the next layer of the storage area network. All network-bound FCoE traffic is pinned to one of these ports.
By default, Fibre Channel ports are uplink. However, you can configure them to function as Fibre Channel storage ports. This is useful in cases where Cisco UCS requires a connection to a Direct-Attached Storage (DAS) device.
You can only configure uplink Fibre Channel ports on an expansion module. The fixed module does not include uplink Fibre Channel ports.
Then point a Web browser to the configured CIMC IP address.
Default username: admin
Default password: password
Downloading Firmware Images to the Fabric Interconnect from a Remote
The following example uses SCP to download the firmware package.
UCS-A# scope firmware UCS-A /firmware # download image scp://user1@192.168.10.10/images/ucs-k9-bundle.1.0.0.988.gbin OR UCS-A /firmware # show download-task
What to Do Next After the image file for the firmware bundles downloaded completes, update the firmware on the endpoints.
UCS-A# scope firmware UCS-A /firmware # show download-task Download task: File Name Protocol Server Userid State ucs-k9-bundle.1.0.0.988.gbin Scp 10.193.32.11 user1 Downloaded
Activating a Capability Catalog Update
The following example activates a Capability Catalog update and commits the transaction:
UCS-A# scope system UCS-A /system # scope capability UCS-A /system/capability # show version UCS-A /system/capability # activate firmware 1.0(3) UCS-A /system/capability* # commit-buffer UCS-A /system/capability #
License about
UCS-A# scope license UCS-A /license # show file detail UCS-A /license # show usage
Activating the Board Controller Firmware on a Cisco UCS B-Series M3 and M4 Rack Servers
Some Cisco UCS B200 M4 blade servers running on releases prior to Release 2.2(4b) may generate a false UCS Manager alert, documented in CSCuu15465. This false board controller mismatch alert was resolved in Cisco UCS Manager Capability Catalogs 2.2(4c)T and 2.2(5b)T. You will not see this alert if you use either the 2.2(4c)T or the 2.2(5b)T capability catalog.
The following limitations apply to M3 and M4 board controller firmware:
- You must be using Cisco UCS Manager, Release 2.2(1a) or greater.
- The board controller firmware and the CIMC firmware must be of the same package version.
- If the activation status of the board controller displays Pending Power Cycle after you upgrade the board controller, a manual power cycle is required. A fault is also generated. After the power cycle is complete, the fault is cleared and the board controller activation status displays Ready.
Procedure
The following is an example of the commands with sample values. Box-A# scope server 1/4 Box-A /chassis/server # scope boardcontroller Box-A /chassis/server/boardcontroller # show version Box-A /chassis/server/boardcontroller # show image Name Type Version --------------------------------------------- -------------------- ------- ucs-b200-m3-brdprog.3.0.gbin Board Controller 3.0 ucs-b200-m3-brdprog.8.0.gbin Board Controller 8.0 Box-A /chassis/server/boardcontroller # show firmware Box-A /chassis/server/boardcontroller # activate firmware 8.0 force Warning: When committed this command will reset the end-point Box-A /chassis/server/boardcontroller* # commit-buffer Box-A /chassis/server/boardcontroller # show version BoardController: Running-Vers: 8.0 Package-Vers: Activate-Status: Activating Box-A /chassis/server/boardcontroller # show version BoardController: Running-Vers: 8.0 Package-Vers: Activate-Status: Ready When is "Ready", work done. FOR B440 XXX: UCS-A# /chassis/server/boardcontroller # show firmware BoardController: Running-Vers: B440100C-B4402006 Activate-Status: Ready UCS-A# /chassis/server/boardcontroller # activate firmware B440100C-B4402006 Step 11 Clear the WILL_BOOT_FAULT by using the Cisco UCS Manager GUI to reset the server CIMC: a. In the Navigation pane, click the Equipment tab. b. On the Equipment tab, expand Equipment > Chassis > Chassis number > Servers, then choose your server. c. In the Work pane, click the General tab. d. In the Actions area, click Recover Server. e. In the Recover Server dialog, click Reset CIMC (Server Controller), then click OK. Wait for CIMC to reboot and for Cisco UCS Manager to do a shallow discovery of the server. This takes two to three minutes. At the end of this process the WILL_BOOT_FAULT is cleared.
Directing show Command Output to a File
You can direct show command output to a file, either on the volatile file system, on slot0 CompactFlash memory, or on a remote server.
The following example shows how to direct the show running-config output to a file on the volatile file system.
switch1# show running-config > volatile:switch1-run.cfg
The following example shows how to direct the show running-config output to a file on slot0 CompactFlash memory.
switch2# show running-config > slot0:switch2-run.cfg The following example shows how to direct the show running-config output to a file on a TFTP server. switch3# show running-config > tftp://10.10.1.1/home/configs/switch3-run.cfg Preparing to copy\ldotsdone
- Use the format bootflash: command to only format the bootflash: file system. You can issue the format bootflash: command from either the switch# or the switch(boot)# prompts. If you issue the format bootflash: command, you must download the kickstart and system images again.
Recovery from the switch(boot)# Prompt
To recover a system image using the kickstart image for a switch with a single supervisor module, follow these steps:
Step 1 Follow this step if you issued a init system command. Otherwise, skip to Step 2.
a. Change to configuration mode.
switch(boot)# config t
b. Configure the IP address of the switch's mgmt0 interface.
switch(boot)(config)# interface mgmt0
c. Enter the local IP address and the subnet mask for the switch, and press Enter.
switch(boot)(config-mgmt0)# ip address 172.16.1.2 255.255.255.0
Step 2 Issue the no shut command to enable the interface on the switch, and press Enter.
switch(boot)(config-mgmt0)# no shut
Step 3 Follow this step if you issued a init system command. Otherwise, skip to Step 4.
a. Enter the IP address of the default gateway, and press Enter.
switch(boot)(config-mgmt0)# ip default-gateway 172.16.1.1
Step 4 Exit to configuration mode.
switch(boot)(config-mgmt0)# exit
Step 5 Exit to EXEC mode:
switch(boot)(config)# exit
Step 6 Copy the system image from the required TFTP server, and press Enter.
switch(boot)# copy tftp://172.16.10.100/system-img bootflash:system-img
Trying to connect to tftp server......
Step 7 Copy the kickstart image from the required TFTP server, and press the Enter key.
switch(boot)# copy tftp://172.16.10.100/system-img bootflash:kickstart-img
Trying to connect to tftp server......
Step 8 Verify that the system and kickstart image files are copied to your bootflash: directory.
switch(boot)# dir bootflash:
total 100756
drwxrwxrwx 2 admin 1024 Fri Sep 27 17:35:13 2002 .ssh
drwxrwxrwx 2 admin 1024 Fri Sep 27 17:35:13 2002 .ssh2
-rw-r--r-- 1 admin 13636096 Fri Sep 20 19:58:56 2002 kickstart-233b
-rw-rw-rw- 1 admin 13636096 Wed Sep 25 17:26:47 2002 kickstart-233d
-rw-rw-rw- 1 admin 14340096 Fri Sep 27 17:28:41 2002 kickstart-240
-rw-r--r-- 1 admin 19280051 Fri Sep 20 20:02:33 2002 system-233b
-rw-rw-rw- 1 admin 19281464 Wed Sep 25 17:28:12 2002 system-233d
-rw-rw-rw- 1 admin 21917189 Fri Sep 27 17:29:51 2002 system-240
drwxr-xr-x 2 admin 3072 Tue Oct 01 10:54:18 2002 logs
-rwxr-xr-x 1 admin 636579 Mon Sep 30 05:32:42 2002 rdl
drwxr-xr-x 2 admin 1024 Mon Sep 30 05:37:55 2002 src
124688384 bytes total used
311350272 bytes free
459779072 bytes available
Step 9 Load the system image from the bootflash: directory:
switch(boot)# load bootflash:system-.img
Uncompressing system image: bootflash:/system.img
CCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCCC
MDS Switch
Would you like to enter the initial configuration mode?(yes/no): yes
UCS health check report
https://jeremywaldrop.wordpress.com/2012/04/04/cisco-ucs-powershell-health-check-report/
System Board 0 SEL_FULLNESS
http://www.cyberfella.co.uk/2012/04/16/ucs-management-logs/
vCenter Server, with a fault of System Board 0 SEL_FULLNESS.
This occurs when the UCS Management Log for a given blade breaches it’s own monitoring threshold of 90% full.
To clear it, Log into UCS Manager, Equipment tab, Servers, Server n, SEL Logs tab, and Backup or Clear the log.
Don’t forget to at least take a look at the log to make sure it hasn’t filled due to real, unresolved hardware problems. The SEL Log logs absolutely everything that goes on to the extent of even logging LED’s as they turn on and off on the equipment, so these logs fill quite quickly.
Visual Guide to collect Tech Support files (B and C series) - Cisco
HOW TO: Upgrade Cisco UCS Manager, Fabric Interconnects, I/O Modules and
1, Before you start downloading firmware and upgrading UCS Manager and the blades, it may be a good idea to go through some housekeeping:
a.Login to UCS Manager. Verify overall status of Fabric Interconnects, I/O
- Modules, Servers and Adapters;
b.Navigate to Admin tab, Faults, Events and Audit Log. Make sure there
- are no alerts or if they can be safely ignored;
c.Equipment tab, Fabric Interconnects, Fabric Interconnect A/B. Make
- sure you have enough space on bootflash;-Series blade server firmware ==
d.Backup your current configuration. Admin tab, All node, select Backup Configuration, Create Backup Operation. Make sure you specify the file name and extension, Click OK
2, Download firmware upgrade bundles from Cisco website Downloads Home > Products > Unified Computing and Servers > Cisco UCS Infrastructure and UCS Manager Software: a.UCS Infrastructure bundle – ucs-k9-bundle-infra.2.0.3a.A.bin b.UCS B-Series blade server products bundle – ucs-k9-bundle-b-series.2.0.3a.B.bin c.If you have any C-Series servers managed by UCS Manager then also download Software for the UCS C-Series rack-mount servers.
- ucs-k9-bundle-c-series.2.0.3a.C.bin
3,
Understanding Cisco UCS Service profile templates
http://blog.nessus.nl/734/understanding-cisco-ucs-service-profile-templates/
Collect logs
show chassis inventory expand show fabric-interconnect inventory expand
http://www.techrepublic.com/article/create-service-profiles-for-cisco-ucs-b-series-blade-servers/
https://www.petri.com/cisco-ucs-creating-service-profile-templates
http://blog.nessus.nl/734/understanding-cisco-ucs-service-profile-templates/
Troubleshooting