Cisco UCS Manager Firmware Management Guide, Release 3.1 - Firmware Upgrade Scenarios [Cisco UCS Manager] Cisco UCS Manager Firmware Management Guide, Release 3.1 - Manage Firmware through Cisco UCS Manager [Cisco UCS Manager] This policy enables you to specify a set of firmware versions that make up the host firmware package (also known as the host firmware pack).
The host firmware package includes the following firmware for server and adapter endpoints: Adapter CIMC BIOS Board Controller FC Adapters HBA Option ROM Storage Controller Local Disk GPUs SAS Expander Remember: To update local disk firmware for blade or rack servers, always include the blade package in the host firmware package. Cisco UCS Manager Firmware Management Guide, Release 3.1 - Guidelines and Prerequisites [Cisco UCS Manager] Before you upgrade any endpoint, consider the following guidelines and limitations: Determine the Appropriate Type of Firmware Upgrade for Each Endpoint Some endpoints, such as Cisco adapters and the server CIMC, can be upgraded through either a direct firmware upgrade or a firmware package included in a service profile.
The configuration of a Cisco UCS domain determines how you upgrade these endpoints. If the service profiles associated with the servers include a host firmware package, upgrade the adapters for those servers through the firmware package. Upgrades of an adapter through a firmware package in the service profile associated with the server take precedence over direct firmware upgrades. Cisco UCS Manager Firmware Management Guide, Release 3.1 - Guidelines and Prerequisites [Cisco UCS Manager] Before you upgrade any endpoint, consider the following guidelines and limitations: Determine the Appropriate Type of Firmware Upgrade for Each Endpoint Some endpoints, such as Cisco adapters and the server CIMC, can be upgraded through either a direct firmware upgrade or a firmware package included in a service profile.
The configuration of a Cisco UCS domain determines how you upgrade these endpoints. If the service profiles associated with the servers include a host firmware package, upgrade the adapters for those servers through the firmware package. Cisco UCS Manager Firmware Management Guide, Release 3.1 - Overview [Cisco UCS Manager] The Cisco UCS Manager A bundle software (Cisco UCS Manager, Cisco NX-OS, IOM firmware) can be mixed with previous B or C bundle releases on the servers (host firmware (FW), BIOS, CIMC, adapter FW and drivers).
The following table lists the mixed A, B, and C bundle versions that are supported on Cisco UCS 6200 fabric interconnects: The following table lists the mixed A, B, and C bundle versions that are supported on Cisco UCS Mini fabric interconnects: Cisco UCS allows cross-version firmware support. The following table shows a matrix of the A bundle software (Cisco UCS Manager, Cisco NX-OS, IOM firmware) that can be mixed with the previous release’s B, C, or M bundles on the servers (host firmware (FW), BIOS, CIMC, adapter FW and drivers). Configure or Change CIMC IP address on UCS C200 series servers. Introduction This documents provides steps to configure IP address for CIMC access to UCS C series servers.
KVM Features Overview of KVM features: 1. Cisco C-Series Rack Servers provides a physical local video and two usb connections for a usb keyboard, video monitor, and usb mouse connection through the front panel of the Rack Server using the Cisco provided dongle connector. 2. Set up CIMC for UCS C-Series Server. Introduction This support document provides an overview for the steps required to set up CIMC network connectivity for the UCS C-Series server.
Prerequisites Requirements Cisco recommends that you: Have a working knowledge of the Cisco UCS C-Series Server Blade hardware and software administration. Components Used The information in this document is based on Cisco UCS C-Series Servers. The information in this document was created from the devices in a specific lab environment. Network Diagram There is currently no specific network diagram available. Conventions. HOW TO: Regenerate expired UCS Manager certificate « vStrong.info. The default (self-signed) UCSM keyring certificate must be manually regenerated if the cluster name changes or the certificate expires (it is valid for one year).
Affected object: sys/pki-ext/keyring-default Description: default Keyring's certificate is invalid, reason: expired Cause: invalid-keyring-certificate Code: F0910 Here is what needs to be done: Make sure Fabric Interconnects have correct time settings, preferably configured to synchronise time with a NTP server(s). UCSM – Admin – All – Timezone Management;SSH to UCS Manager cluster IP address and login as an administrator user;Issue the following commands: N.B. After you issue ‘commit-buffer‘ command, all GUI sessions will be disconnected;After a couple of minutes, validate new certificate: Open web browser, connect to UCSM cluster IP address and accept the certificate warning. EMC UIM/P users: New certificate needs to be exported from UCSM and imported into UIM/P. Understanding UCS VIF Paths. In the UCS world where a virtual NIC on a virtual server is connected to a virtual port on a virtual switch by a virtual cable, it is not surprising that there can be confusion about what path packets are actually taking through the UCS infrastructure.
Similarly knowing the full data path through the UCS infrastructure is essential to understanding troubleshooting and testing failover. I’m sure you have all seen the table below in UCS Manager where it details the path that each virtual NIC or HBA takes through the infrastructure. But what do all these values mean? And where are they in the infrastructure? That is the objective of this post. Figure 1 I will also detail the relevant CLI commands to confirm, and troubleshoot the complete VIF (Virtual Interface) Path. UCS Boot-from-SAN Troubleshooting with the Cisco VIC (Part 2) So, first let me define some terms….the Cisco VIC is also called “Palo” – a codename that sort of stuck (much the chagrin of the marketing team).
Palo’s official name is M81KR – now do you see why “Palo” sort of stuck ? We have some new VIC cards as well – the VIC-1240 and VIC-1280 and Sean McGee (@mseanmcgee) talks more about the VIC-1280 here. The VIC-1240 is a built-in option on the M3 blades. Now that we settled that, where is Part 1 of this article? Why am I writing part 2? As Ryan pointed out, LUNLIST only works prior to the OS HBA driver loading. To get to the command, you need to gain access to the UCS CLI and run the following: Cisco UCS Manager B-Series Troubleshooting Guide - General Troubleshooting Solutions [Cisco UCS Manager] Cisco UCS B-Series GUI Firmware Management Guide, Release 2.1 - Downloading and Managing Firmware in Cisco UCS Manager [Cisco UCS Manager]
Common Tips in UCS Firmware Management. Introduction This document presents some common tips to simplify your daily firmware management process.
Prerequisites. B_CiscoUCSCentral-CLI-Reference-Manual-Release1-3. B_CiscoUCSCentral_Software-UserManual-Release1-3. B_Cisco_UCSC_Install_and_Upgrade_Guide_1-3. Space: Cisco Developed UCS Integrations. Cisco UCS B200 M3 Blade Server Installation and Service Note. Each channel is identified by a letter—A, B, C, D for CPU1, and E, F, G, H for CPU 2. Each DIMM slot is numbered 0, 1, or 2. Note that each DIMM slot 0 is blue, each slot 1 is black, and each slot 2 is off-white or beige. The figure below shows how DIMMs and channels are physically laid out on the blade server. The DIMM slots in the upper and lower right are associated with the second CPU (CPU shown on right in the diagram), while the DIMM slots in the upper and lower left are associated with the first CPU (CPU shown on left). Figure 19. The figure below shows a logical view of the DIMMs and channels. Figure 20. DIMMs can be used in the blade server in a one DIMM per Channel (1DPC) configuration, in a two DIMMs per Channel (2DPC) configuration, or a three DIMMs per Channel (3DPC) configuration.
Each CPU in a Cisco UCS B200 M3 blade server supports four channels of three memory slots each. Each channel is identified by a letter—A, B, C, D for CPU1, and E, F, G, H for CPU 2. Figure 19. Cisco UCS - Creating Service Profile Templates. Introduction Service Profile Templates can make it easy for you to provision many servers because it will allow you to quickly create multiple service profiles having the same basic parameters like say the number of vNICs and vHBAs. In this video, from TrainSignal’s Implementing Cisco Unified Computing System (UCS) Training Cisco UCS expert Jason Nash will show you the required steps to creating a Service Profile Template in your Cisco Unified Computing System. (Instructional video below provides a walkthrough of the steps contained in this article.) To create a service profile template from within your Cisco Unified Computing System Manager, navigate to Servers > Service Profile Templates, and right-click on root.
On the context menu, select Create Service Profile Template. Identify Service Profile Template The first thing you’ll be asked to enter is your service profile template’s name. Next, choose a template type. After selecting a template type, choose an appropriate UUID assignment. Understanding Cisco UCS Service profile templates. Cisco UCS C-Series Server Integration with Cisco UCS Manager 2.1 - Cisco UCS C-Series Integration with Cisco UCS Manager [Cisco UCS C-Series Rack-Mount UCS-Managed Server Software] Cisco UCS Manager 2.1 provides two connectivity modes for Cisco UCS C-Series Rack-Mount Server management. The following are the two connectivity modes: Dual-wire Management (Shared LOM): This management mode is supported in the Cisco UCS Manager releases earlier than 2.1.
Shared LAN on Motherboard (LOM) ports on the rack server are used exclusively for carrying management traffic. A separate cable connected to one of the ports on the PCIe card carries the data traffic. Using two separate cables for managing data traffic and management traffic is also referred to as dual-wire management. Set up CIMC for UCS C-Series Server. UCS upgrade procedure - Begin here. UCS Infrastructure upgrade. UCS Host Firmware Upgrade - Video. HOW TO: Upgrade Cisco UCS Manager, Fabric Interconnects, I/O Modules and B-Series blade server firmware « vStrong.info.
These instructions are for Cisco UCS B200 M2 blade server firmware upgrade from 2.0(1q) to 2.0(3a) (Vblock support matrix 2.5.9). Before you start downloading firmware and upgrading UCS Manager and the blades, it may be a good idea to go through some housekeeping: Login to UCS Manager. Verify overall status of Fabric Interconnects, I/O Modules, Servers and Adapters; Navigate to Admin tab, Faults, Events and Audit Log.
Make sure there are no alerts or if they can be safely ignored;Equipment tab, Fabric Interconnects, Fabric Interconnect A/B. Make sure you have enough space on bootflash; Backup your current configuration. Admin tab, All node, select Backup Configuration, Create Backup Operation. Enable Call Home. Hope this will help.