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. You can also exclude firmware of specific components from a host firmware package either when creating a new host firmware package or when modifying an existing host firmware package.
Important: Each host firmware package is associated with one list of excluded components, which is common across all firmware packages—Blade, Rack and M-Series. The firmware package is pushed to all servers associated with service profiles that include this policy. This policy is not dependent upon any other policies. 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. Do Not Activate All Endpoints Simultaneously in Cisco UCS Manager GUI If you use Cisco UCS Manager GUI to update the firmware, do not select ALL from the Filter drop-down list in the Activate Firmware dialog box to activate all endpoints simultaneously. Fabric Interconnect Traffic Evacuation. 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. Do Not Activate All Endpoints Simultaneously in Cisco UCS Manager GUI If you use Cisco UCS Manager GUI to update the firmware, do not select ALL from the Filter drop-down list in the Activate Firmware dialog box to activate all endpoints simultaneously. Fabric Interconnect Traffic Evacuation. 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).
For more information, see the Release Notes for Cisco UCS Software for your particular release. Important: Configure or Change CIMC IP address on UCS C200 series servers | Unified Computing | Cisco Support Community | 6011 | 12244866. 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. 3. 4. Configure CIMC IP address Step 1: Boot the server. Step 2: Quickly Press the “F8” key to enter the “CIMC Config” setup before the UCS server goes into auto reboot. Step 3: For the “NIC mode”, enable “Dedicated” and for “NIC redundancy” enable “None”. Step 4: To use fixed/static IP Address, disable the “DHCP enabled” option. Step 5: To use DHCP, enable the “DHCP enabled” option Step 6: Press the “F10” key to save the changed settings done so far.
Step 7: After 45 seconds, press the “F5” key to refresh the display. Step 8: Press the “ESC” key to exit the CIMC Configuration Utility. Logging In to CIMC. 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. Be familiar with UCS C-Series Servers Cisco Integrated Management Controller Understand the impact and implications of the different commands described in this document. Be familiar with the UCS C-Series components and topology. 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 Refer to the Cisco Technical Tips Conventions for more information on document conventions. Background Information There is currently no specific background information available. Getting CIMC Started Access CIMC. 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.
Like this: Like Loading... 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? Figure 1 I will also detail the relevant CLI commands to confirm, and troubleshoot the complete VIF (Virtual Interface) Path. Figure 2 Virtual Circuit First column in figure 1, Virtual Circuit number, this is a unique value assigned to the virtual circuit which comprises the virtual NIC, the virtual cable (red dotted line in figure 2) and the virtual switch port. Figure 3 Figure 4 Figure 5. UCS Boot-from-SAN Troubleshooting with the Cisco VIC (Part 2) | JeffSaidSo.
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? Well, my good friend Ryan Hughes (@angryjesters) got the ball rolling on this. He took it upon himself to write an excellent article explaining how to access the obscure-but-useful command called LUNLIST. 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: connect: connects to the VICs management processorattach-fls: attaches to the fabric login service of the adapter 6.
-Jeff Article Update: Update #2. Cisco UCS Manager B-Series Troubleshooting Guide - General Troubleshooting Solutions [Cisco UCS Manager] When you encounter an issue that requires troubleshooting or a request for assistance to the Cisco Technical Assistance Center (Cisco TAC), collect as much information as possible about the affected Cisco UCS domain. Cisco UCS Manager outputs this information into a tech support file that you can send to Cisco. You can create a tech support file for the following components of a Cisco UCS domain: UCSM—Contains technical support data for the entire Cisco UCS domain. UCSM management services—Contains technical support data for the Cisco UCS Manager management services, excluding Fabric Interconnects. 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 Requirements Cisco recommends that you: Have a working knowledge of Cisco UCS Server Blade software and hardware. Components Used The information in this document is based on Cisco UCS. The information in this document was created from the devices in a specific lab environment. Network Diagram A typical Cisco UCS topology looks something like this: Conventions Refer to the Cisco Technical Tips Conventions for more information on document conventions. Main Task 1. Complete these steps: Navigate to the SW Center Homepage and select a Product Category. 2.1 Firmware Management with GUI Before you perform firmware management, refer to prerequisites for firmware upgrade or downgrade.
View Installed Firmware Complete these steps in order to view installed firmware in UCS through the GUI: Log into Cisco UCS Manager. Packages The Packages tab: Images The Images tab: Download Tasks Verify. 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. Physical Representation of DIMMs and Channels 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.
Figure 19. Figure 20. 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 | Marcels Blog. 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. The general prerequisites for Dual-wire integration with Cisco UCS Manager are built into the C-Series Rack-Mount Server CIMC release 1.4(6) or later. Server CIMC release 1.4(6) or later Cisco UCS VIC 1225 Virtual Interface Card The following table lists theC-Series Rack-Mount Servers and supported management options: Based on your server model and CIMC version, you can use either one of these two integration options to connect the rack server withCisco UCS Manager 2.1. Cisco Nexus 2000 Series Fabric Extender documentation. 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. HOW TO: Upgrade Cisco UCS Manager, Fabric Interconnects, I/O Modules and B-Series blade server firmware Like this: Like Loading...