1.16k likes | 1.43k Views
Welcome Technical Services Virtual Boot Camp Session 8. Technical Services India Team. Technology · Architecture Overview UCS C-series UCS B- series · UCS Interoperability Hardware Software · Troubleshooting Case Study (Lab Demo) Q&A. Cisco Support Community.
E N D
WelcomeTechnical Services Virtual Boot Camp Session 8 Technical Services India Team
Technology • · Architecture OverviewUCS C-series UCS B-series • · UCS InteroperabilityHardware Software • · Troubleshooting • Case Study (Lab Demo) • Q&A Cisco Support Community Technology Process Recap – Session 7 (18th Feb)
Cisco Support Community Technology Process Course Material https://supportforums.cisco.com/docs/DOC-37994 ...PPT https://supportforums.cisco.com/videos/7517 ....Video https://supportforums.cisco.com/docs/DOC-37851 ...Q&A
Technology • · Firmware Install and upgrade UCS C-series UCS B-series • · Troubleshooting • Case Study (Lab Demo) • Important logs • Part Identification and RMA • Q&A Cisco Support Community Technology Process Today Agenda (Session -8)
Technology – UCS Cisco Support Community Technology Process AvinashShukla TeclusD'Souza ChetanBadami
Agenda • UCS Upgrade Procedure • C-series • B-series • UCS H/W and S/W Interoperability • UCS Troubleshooting • UCSM / FI / IOM / Blade • C-series
UCS H/W and S/W Interoperability Avinash Shukla Cisco TAC
Operating System • Check the support matrix before installing the OS on the blade • Install / keep the drivers (Eth / FC) updated as per the matrix • Few important things to check: • Is the blade running the certified OS and OS version? • Are there any special needs for that OS? E.g. VMWare – OEM Image • Are the drivers at the OS level updated and current? • Answer: • UCS S/W and H/W matrix • http://www.cisco.com/web/techdoc/ucs/interoperability/matrix/matrix.html • http://www.cisco.com/en/US/products/ps10477/prod_technical_reference_list.html
Agenda • C series firmware upgrade • Pre-requisites • Firmware ISO location and downloading • Upgrade process • B series firmware upgrade • Pre-requisites • Firmware bundles and downloading • Upgrade process • Additions / Modifications from version 2.1
Pre-requisites C Series
Things to consider • Release Notes will cover gotchas and concerns in the upgrade process • Upgrades from one version back will always work • Check release notes about prior versions • If customer is really far behind it might require two upgrades to get to current code • Schedule an maintenance window • CIMC and server will reboot during upgrade
C Series Upgrade • Downloading iso file
Upgrade process C Series
Verify Upgrade • To verify check that all components are upgraded
Pre-requisites B Series
Things to consider • Release Notes will cover gotchas and concerns in the upgrade process • Upgrades from one version back will always work • Check release notes about prior versions • If customer is running a very old version, it might require two upgrades to get to current code • Schedule an maintenance window • FI and IOM will reboot during upgrade • Make sure network and storage fabric are redundant • Highly recommended to backup UCSM configuration
Be patient • Upgrade process is not quick • Sometimes bugs will result in the first release after FCS • Expect a maintenance release shortly after FCS • Follow the upgrade procedure for each version • The procedure is not always the same from one version to another.
Downgrading • Sometimes there might be data loss • Might have to erase config to downgrade • Database changes in new versions cannot always be back ported
Bundles • Prior to 1.4 there was only all inclusive bundle • Now there are multiple bundles • Infra-bundle – contains code for FI, IOM, and UCSM • B-series bundle – contains BIOS and blade specific code • C-series bundle – contains BIOS and rack server specific code
Bundles • All firmware work is done from Equipment tab in UCSM
Bundles • Packages can be viewed/deleted from “Packages” tab
Bundles • Bundles are downloaded from the “Download Tasks” tab • Downloads can be through desktop or using ftp/scp/sftp/tftp
Cisco.com to download FCS bundles FI, IOM, and UCSM software B-Series packages C-Series packages
Pre 1.4 bundles are single download 1.0-1.3 bundles
Upgrade process B Series
Upgrade Process • Again always consult release notes • Upgrade through GUI is easiest • General Process is • Backup UCSConfig (Full & All Config) • Download code • Update components • Activate components in order of (Check RN cause order can change) • Interface cards – Set Startup Only • CIMC • IOM – Set Startup Only • UCSM • FI
Updating Components • Update means copy new code to backup location of all UCSM components • Simply stages the new code • Can update all components at once
Updating Components • Time to update will vary based on component • IOMs take a long time. Up to 5 minutes • If any component has issues check FSM for that component • Update process does not work on FI • Once everything is in “Ready” state you can move to Activate
Activate Components • In this process you activate the code that you copied • Some code is activated but set to “activate on next reboot” • Understand that in this stage you can create outages • Activate “leaves of the tree” first • BU uses this term to mean that order should be • Interface card = leaf • CIMC = twig • IOM = branch • UCSM = trunk • FI = root
Activate Blade Components • Recommended Method is to use Policies • Host Firmware Policy to apply latest BIOS, Board Controller, Adapters, etc.
Activate Interface cards • Set to “Set to startup version only” • If you uncheck above box it will cause a blade reboot!!!
Activate CIMC • CIMC can bet activated without disruption to OS on blade • KVM session will be lost while activating
Activate IOM • Same as Interface card “Set Startup Version Only” • IOM needs to be at same version as FI!!!
Activate UCSM • Will cause UCSM to disconnect • Takes a few minutes
Activate Fabric Interconnect • Recommended to activate one FI at a time • A complete outage will not occur • Fail one fabric • Wait for all Network and FC traffic failover to second Fabric • Highly recommended to have an outage window • Biggest risk is SAN storage • FI will upgrade and reboot • Part of the process is to reboot connected IOM as well • Can take up to 10-15 minutes for FI and all IOM to come back online • If any failure during first FI upgrade STOP! Do not attempt to upgrade second FI
Activate Fabric Interconnect • Activate FI from Equipment tab • Upgrade subordinate first
Activate Fabric Interconnect • Choose correct Kernel and System Version • FI will take a few minutes and then reboot • IOMs will get updated as well