book

Implementing Cisco UCS Solutions

by Farhan Nadeem, Prasenjit Sarkar

December 2013

Intermediate to advanced

370 pages

7h 26m

English

Packt Publishing

Read now

Unlock full access

Support files, eBooks, discount offers and moreWhy Subscribe?Free Access for Packt account holdersInstant Updates on New Packt Books
What this book coversWhat you need for this book

ErrataPiracyQuestions
Looking at the UCS equipmentStateless computingRapid provisioning of serversSimplified troubleshootingVirtualization readinessChoice of industry-standard form factorsExtended memory technology for increased density
The Cisco UCS FIsThe Cisco UCS blade serversThe Cisco UCS rack-mount servers
The Cisco 6296UP FIThe Cisco 6248UP FIThe Cisco 6140UP FIThe Cisco 6120UP FIExploring connectivity transceivers for FIs
A look at the chassis frontA look at the chassis backEnvironmental requirements
The Cisco 2208XP IOM cardThe Cisco 2204XP IOM cardThe Cisco 2104XP IOM card
Learning more about blade serversThe B22 M3 blade serverB200 M1/M2/M3 blade serversB230 M1/M2 blade serversThe B420 M3 blade serverB440 M1/M2 blade serversLearning more about rack-mount serversThe C22 M3 rack-mount serverThe C24 M3 rack-mount serverThe C220 M3 rack-mount serverThe C240 M3 rack-mount serverThe C260 M2 rack-mount serverThe C420 M3 rack-mount serverThe C460 M2 rack-mount server
VICs for blade serversVIC 1280VIC 1240VIC M81KRVICs for rack-mount serversVIC 1225VIC P81E
Nonredundant modeN+1 redundant modeGrid redundant mode
Blade server installationInstallation and removal of CPUInstallation and removal of RAMInstallation and removal of internal hard disksInstallation of mezzanine cardsInstallation of blade servers on the chassis
IOM – FI cabling topologyIOM – FI physical cabling
Configuring Cisco UCS emulatorSystem requirementsHypervisor prerequisitesInstalling UCSPE on VMware Player using a ZIP fileInstalling UCSPE on VMware Player using an OVA fileInstalling UCSPE on VMware WorkstationInstalling UCSPE on VMware vSphere ESXi
Stash areaAdding a new chassis with blade serversAdding an empty chassisConfiguring and adding a blade server to the chassisConfiguring and adding a rack-mount serverModifying server components
Introducing Cisco UCSMUCSM firmware version
Navigation paneThe Equipment tabThe Servers tabThe LAN tabThe SAN tabThe VM tabThe Admin tabThe Fault Summary area
Chassis/FEX Discovery PolicyPower PolicyMAC Address Table AgingDNS ServerTime Zone ManagementSNMP
Getting help with CLI commandsAccessing the history of CLI commandsAccessing other CLIsScope commandsApplying changesAn example configuration using CLI commands
Understanding Fabric Interconnect switching modesEthernet End Host Mode (EHM)Ethernet switching mode
Configuring upstream switchesLearning how to configure Fabric Interconnect uplink portsConfiguring VLANs
Dynamic pin groupsFailure responseStatic pin groupsFailure response re-pinning
Learning how to configure Fabric Interconnect server portsConfiguring IOM ports
What is MAC address abstraction?Learning to create vNICs
Learning storage connectivity options
Overview of SCSIOverview of Fiber ChannelOverview of iSCSIOverview of Fiber Channel over Ethernet (FCoE)
Learning about zoning
Example configuration – connecting SAN directly to Fabric Interconnects
Dynamic pin groupsFailure responseStatic pin groupsFailure response re-pinning
Understanding identity and resource pools
Overview of service profiles
Creating a basic service profileCreating a service profile in the expert modeCreating a service profile from a service profile template
Configuring the server BIOS policyConfiguring adapter policiesConfiguring scrub policiesConfiguring QoS policiesLocal disk configuration policiesMaintenance policiesConfiguring IPMI
Identifying the service profileConfiguring the networking settingsConfiguring the storage connectivityConfiguring zoningvNIC/vHBA placementServer Boot Order configurationConfiguring the server maintenance policyConfiguring a SAN boot policyAssociating service profilesOperational policies
Licensing Cisco UCS Fabric Interconnect
Organizational inheritance
Active Directory integrationPredefined rolesAbout UCS locales
Understanding IEEE 802.1Q
Role differentiationRole issues
Virtual Ethernet interfacesLearning about port profiles
The Virtual Ethernet ModuleThe Virtual Supervisor Module
VEM functions
The physical switch chassisLine cardsThe N1KV backplane
Performance advantages using vPath
VSM installation
Using Layer 2 connectivityUsing Layer 3 connectivityUsing the Domain IDL2 modeL3 modeSystem VLANs and opaque dataVSM to vCenter communication
Backing up the Cisco UCS configuration
Creating a manually run backup job using GUICreating a scheduled backup job using GUICreating a backup job using CLI
Configuring the first Fabric InterconnectConfiguring the second Fabric InterconnectFabric Interconnect elections
The Split-brain scenarioPartition in spacePartition in time
Port-channel uplink failure and recovery on Fabric Interconnect
Identifying a mezzanine adapter failureCommon mezzanine adapter error messages
Common IOM error messagesFabric Interconnect server port failureRectifying the Global Chassis Discovery Policy configuration error
Common error messages with Fabric Interconnect
Common failure messages for UCS Chassis
Understanding the challenges in Infrastructure
Configuring vCenter with UCSMIntegration with Cisco UCS PowerToolConnecting your UCS Manager using PowerTool

Content preview from Implementing Cisco UCS Solutions

Development of Nexus 1000v

N1KV was developed jointly by VMware and Cisco. As such, it is certified by VMware to be compatible with VMware vSphere, vCenter, ESXi, and many other vSphere features.

Virtual Ethernet interfaces

Cisco N1KV when enabled for VN-Link, operates on the basis of virtual Ethernet (vEth) interfaces. Once enabled for VN-Link, it maintains network configuration attributes, such as security and statistics for a given virtual interface across mobility events. vEth interfaces are comparable of physical network access ports. A mapping gets created between each vEth interface and the corresponding vNICs on the VM. You may ask me why ...