Category: Hardware

Articles related to Hardware and their management

QoS and poor SAN performance in Cisco UCS

Symptoms: Very poor SAN performance on Cisco UCS B200 M3 Blades. Deploying VMs from templates and cloning VMs hang. CPU stats in a VM indicated 100% cpu in wio state Background: Cisco UCS provides a QoS feature to allow prioritization of certain types of traffic. Cisco UCS supported multi-hop FCoE from release 2.1 onwards.  
Read More »

Service Profile Association failure due to dynamic vNICS

Symptoms: The following errors were encountered when associating a Service Profile with a B200 M3 UCS Blade: ERROR 1: SRIOV PF/VF vNIC configuration failure. Incompatible Bios Policy Settings for SRIOV vNICs There are not enough resources overall. ERROR 2: [FSM:STAGE:REMOTE-ERROR]: Configure adapter for pre-boot environment(FSM-STAGE:sam:dme:ComputePhysicalAssociate:NicConfigPnuOSLocal)   Background:  Cisco’s Virtual Interface Cards (VIC) such as the
Read More »

UCS CSR

While configuring certificates in UCSM 2.1(1f), I observed that the UCSM does not permit you to create a Certificate Signing Request (CSR) for certificates with more than one Subject Alternative Name (SAN). However, you can create a certificate with 1 SAN as shown in the image below. The certificate’s SAN is requested using the DNS
Read More »

UCS MAC Nomenclature

Given below is a nomenclature for Cisco UCS MAC Addresses:     Example: 00:25:B5:02:0B:02 => The second MAC address (OP=02) in a MAC Pool in UCS Domain 2 (KL=02) for an ESXi Host (M=0) in Fabric B (N=B)

UCS WWN Nomenclature

Given below is a nomenclature for Cisco UCS WWPNs and WWNNs:     Examples: (1) 20:00:00:25:B5:01:0A:01  => The first WWPN (OP=01) in a WWPN pool in UCS Domain 1 (KL=01) which is used by an ESXi host (M=0) in Fabric A (N=A). (2) 20:00:00:25:B5:03:2F:03  => The third WWNN (OP=03 and N=F) in a WWNN pool
Read More »

IBM HS22 Blade boot failure

Problem: After upgrading firmware (BIOS, SAS Controller, IMM) on an IBM HS22 (MT:7870) Blade and inserting it into a BladeCenter H slot, the Blade did not boot from HDD. Background & Analysis: The HS22 Blade was intended to replace another failed HS22 blade. The replacement HS22 Blade was first inserted into another BladeCenter H chassis
Read More »