Cisco UCS PowerTool Suite Installation And Configuration Guide, Release .
Cisco UCS PowerTool Suite Installation and Configuration Guide,Release 3.0(2)First Published: 2016-03-01Last Modified: 2021-09-09Americas HeadquartersCisco Systems, Inc.170 West Tasman DriveSan Jose, CA 95134-1706USAhttp://www.cisco.comTel: 408 526-4000800 553-NETS (6387)Fax: 408 527-0883
2017–2021 Cisco Systems, Inc. All rights reserved.
CONTENTSCHAPTER 1Preface1Audience1Conventions1Related Cisco UCS Documentation3Documentation Feedback 3Obtaining Documentation and Submitting a Service RequestCHAPTER 2Overview5About Cisco UCS PowerTool SuiteSystem RequirementsCHAPTER 355Install Cisco UCS PowerTool Suite9Installing or Upgrading UCS PowerTool ModulesUninstalling Cisco UCS PowerTool SuiteCHAPTER 43Configure Cisco UCS PowerTool SuiteCisco UCS Common Module9101111Getting Cisco UCS Software Images11Cisco UCS Hardware and Software Compatibility Tool Integration13Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)iii
ContentsCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)iv
CHAPTER1PrefaceThis preface includes the following sections: Audience, on page 1 Conventions, on page 1 Related Cisco UCS Documentation, on page 3 Documentation Feedback, on page 3 Obtaining Documentation and Submitting a Service Request, on page 3AudienceThis guide is intended primarily for data center administrators with responsibilities and expertise in one ormore of the following: Server administration Storage administration Network administration Network securityConventionsThis document uses the following conventions:ConventionsIndicationbold fontCommands an keywords and user-entered text appearin bold font.italic fontDocument titles, new or emphasized terms, andarguments for which you supply values are in italicfont.[]Elements in square brackets are optional.Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)1
PrefaceConventionsNoteTipConventionsIndication{x y z}Required alternative keywords are grouped in bracesand separated by vertical bars.[x y z]Optional alternative keywords are grouped in bracketsand separated by vertical bars.stringA nonquoted set of characters. Do not use quotationmarts around the string or the string will include thequotation marks.courier fontTerminal sessions and information the system displaysappear in courier font. Nonprinting characters, such as passwords are in anglebrackets.[]Default responses to system prompts are in squarebrackets.!,#An exclamation point (!) or a pound sign (#) at thebeginning of a line of code indicates a comment line.Means reader take a note. Notes contain helpful suggestions or references to material not covered in themanual.Means the following information will help you solve a problem. The tips information might not betroubleshooting or even an action, buy could be useful information, similar to a Timesaver.CautionMeans reader be careful. In this situation, you might perform an action that could result in equipment damageor loss of data.TimesaverMeans the described action saves time. You can save time by performing the action described in the paragraph.WarningIMPORTANT SAFETY INSTRUCTIONSThis warning symbol means danger. You are in a situation that could cause bodily injury. Before you workon any equipment, be aware of the hazards involved with electrical circuitry and be familiar with standardpractices for preventing accidents. Use the statement number provided at the end of each warning to locateits translation in the translated safety warnings that accompanied this device.SAVE THESE INSTRUCTIONSCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)2
PrefaceRelated Cisco UCS DocumentationRelated Cisco UCS DocumentationDocumentation RoadmapsFor more information, you can access the related documents from the following links: Cisco UCS Manager PowerTool Release 3.x User Guide Cisco IMC PowerTool, Release 3.x User Guide Cisco UCS Central PowerTool, Release 3.x User Guide Cisco UCS Documentation Roadmap Cisco UCS C-Series Documentation Roadmap Cisco UCS Central Configuration GuidesOther Documentation ResourcesAn ISO file containing all B and C-Series documents is available at the ype.html?mdfid 283853163&flowid 25821 From this page, clickUnified Computing System (UCS) Documentation Roadmap Bundle.The ISO file is updated after every major documentation release.Follow Cisco UCS Docs on Twitter to receive document update notifications.Documentation FeedbackTo provide technical feedback on this document, or to report an error or omission, please send your commentsto ucs-docfeedback@cisco.com. We appreciate your feedback.Obtaining Documentation and Submitting a Service RequestFor information on obtaining documentation, submitting a service request, and gathering additional information,see What’s New in Cisco Product Documentation w/whatsnew.html.Subscribe to What’s New in Cisco Product Documentation, which lists all new and revised Cisco technicaldocumentation, as an RSS feed and deliver content directly to your desktop using a reader application. TheRSS feeds are a free service.Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)3
PrefaceObtaining Documentation and Submitting a Service RequestCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)4
CHAPTER2OverviewThis chapter consists of the following sections: About Cisco UCS PowerTool Suite, on page 5 System Requirements, on page 5About Cisco UCS PowerTool SuiteCisco UCS PowerTool suite is a set of PowerShell modules that helps automate all aspects of Cisco UCSManager, Cisco UCS Central, and Cisco IMC. It also helps automate server, network, storage, and hypervisormanagement. Cisco UCS PowerTool suite enables easy integration with existing IT management processesand tools. The PowerTool cmdlets work on the Cisco UCS Management Information Tree (MIT). Thesecmdlets can be used to execute read, create, modify, and delete operations on all the UCS Managed Objects(MOs) in the MIT.NotePrior to the release 2.5(2), the PowerTool modules were posted at cisco.com.Release 2.5(2) onwards, the PowerTool modules will be available o.System RequirementsEnsure that the system meets the following requirements: Windows PowerShell 5.1 or PowerShell 6.x and above .NET Framework 4.7.1 or above or .NET Core 2.0 and aboveCisco UCS ManagerCisco UCS Manager PowerTool is compatible with the following Cisco UCS Manager releases: Release 4.2 Release 4.1Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)5
OverviewSystem Requirements Release 4.0 Release 3.2 Release 3.1 Release 3.0 Release 2.5 Release 2.2 Release 2.1 Release 2.0Cisco UCS C-Series ServersCisco IMC PowerTool is compatible with the following Cisco UCS C-Series releases: Release 4.2 Release 4.1 Release 4.0 Release 3.1 Release 3.0 Release 2.0 Release 1.5Cisco UCS E-Series ServersCisco IMC PowerTool is compatible with the following Cisco UCS E-Series releases: Release 2.2(1) and higherCisco UCS CentralCisco UCS Central PowerTool is compatible with the following Cisco UCS Central releases: Release 2.0 Release 1.5 Release 1.4 Release 1.3 Release 1.2Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)6
OverviewSystem RequirementsInstallation RequirementsImportantIt is recommended to uninstall the modules of lower version before upgrading to higher version.Close any instances of PowerShell running with the PowerTool module loaded.Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)7
OverviewSystem RequirementsCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)8
CHAPTER3Install Cisco UCS PowerTool SuiteThis chapter consists of the following sections: Installing or Upgrading UCS PowerTool Modules, on page 9 Uninstalling Cisco UCS PowerTool Suite, on page 10Installing or Upgrading UCS PowerTool ModulesYou can install the individual PowerShell module of PowerTool using Install-Module Cmdlet from PowerShell.For example, you can install Cisco.UCSManager module from PowerShell gallery and perform operationson UCSM using this module.Uninstall the PowerShell modules of PowerTool with the older version before installing the new version. Touninstall the PowerTool modules, use the Uninstall-Module Cmdlet. Example:Uninstall-Module -Name Cisco.UCSManagerNote Prior to the release 2.5(2), the PowerTool modules were posted at cisco.com.Release 2.5(2) onwards, the PowerTool modules will be available o. The Cisco.UCS.DesiredStateConfiguration module is not supported in 3.x release.Perform the following steps to install the PowerShell modules of PowerTool from PowerShell gallery:Step 1Step 2Launch PowerShell using Run as Administrator on Windows or sudo on Non-Windows.Install the following PowerShell modules of PowerTool from PowerShell Gallery using the Install-Module Cmdlet: Cisco.IMC Cisco.UCSManager Cisco.UCSCentralSee the Microsoft documentation for more information about:Install-Module -Name Cisco.UCSManagerCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)9
Install Cisco UCS PowerTool SuiteUninstalling Cisco UCS PowerTool SuiteThe PowerTool module packages are available oUninstalling Cisco UCS PowerTool SuitePerform the following steps to uninstall the PowerShell modules of PowerTool.Step 1Launch PowerShell using Run as Administrator on Windows or sudo on Non-Windows.Step 2Uninstall the following PowerShell modules of PowerTool using the Uninstall-Module Cmdlet: Cisco.IMC Cisco.UCSManager Cisco.UCSCentral Cisco.UCS.CommonExample: Uninstall-ModuleNoteCisco.UCSManagerYou cannot uninstall the dependent modules first. For example: Cisco.UCSManager, Cisco.UCSCentral andCisco.IMC are dependent on the module Cisco.UCS.Common.So, you need to uninstall these modules first before uninstalling Cisco.UCS.Common.See the Microsoft documentation for more information about:Uninstall-ModuleTo verify if all the modules have been Uninstalled, use the Get-InstalledModule Cmdlet.Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)10
CHAPTER4Configure Cisco UCS PowerTool SuiteThis chapter consists of the following sections: Cisco UCS Common Module, on page 11 Getting Cisco UCS Software Images, on page 11 Cisco UCS Hardware and Software Compatibility Tool Integration, on page 13Cisco UCS Common ModuleCisco UCS Common module contains cmdlets for features or actions common to all Cisco UCS modules. Acmdlet replaces the duplicate cmdlets available in the older releases of Cisco UCS Manager, Cisco IMC andCisco UCS Central PowerTool. The cmdlets in Retained Cmdlet column have been retained and it worksfor all three PowerTool modules.Retained CmdletCmdlet Removed in Cisco Central Cmdlet Removed in Cisco lCommunity tion Get-UcsCentralPowerToolConfiguration guration Set-UcsCentralPowerToolConfiguration ionExport-UcsCertralPSSessionExport-ImcPSSessionIf you are using cmdlets that are removed from this release in any of the scripts, then use the cmdlets fromthe Retained Cmdlet column instead.Getting Cisco UCS Software ImagesThe following cmdlets can be used to get the available driver or firmware images for Cisco UCS Manager,Cisco UCS Central, or Cisco IMC servers from Cisco.com.The following cmdlet is obsolete and will not be supported after February, 2022. Get-UcsSoftwareImageList—To get all the images available for either UCS Manager, Cisco IMC, orUCS CentralCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)11
Configure Cisco UCS PowerTool SuiteGetting Cisco UCS Software Images Get-UcsSoftwareImage—This cmdlet downloads the image to a local file system. This cmdlet takespipeline input from the Get-UcsSoftwareImageList reImageList -Credential PSCredential [-Category string ] [-Type string ] [-Model string ] [-AllReleases][-Proxy WebProxy ] [-Ucs BaseHandle[] ] [ CommonParameters ]Get-UcsSoftwareImageList -Credential PSCredential -MdfId uint -SoftwareId uint [-AllReleases] [-Proxy WebProxy ][-Ucs BaseHandle[] ] [ CommonParameters ]NoteAllReleases switch parameter is available from UCS PowerTool Suite 2.0(2) and higher. Specifying the–AllRelease switch parameter, lists all the available images in Cisco.com for the selected device type.–Version parameter is valid for UCS PowerTool Suite Release 2.0(1) e -SoftwareImage ImageDetails -Path string [-EulaAccepted] [-Xml][ CommonParameters geList -Category DefaultGet-UcsSoftwareImageList -Category ModularServerGet-UcsSoftwareImageList -Category ModularServer -Type FirmwareGet-UcsSoftwareImageList -Category ModularServer -Type DriversGet-UcsSoftwareImageList -Type FirmwareGet-UcsSoftwareImageList -Type Drivers images Get-UcsSoftwareImageList image[0] Get-UcsSoftwareImage -Path "C:\Images" -EulaAccepted -verboseGet-UcsSoftwareImageList Get-UcsSoftwareImage -Path "C:\Images" -verboseThe following cmdlets which were used for getting software images from Cisco.com are no longersupported from this release onwards: Get-UcsCcoImageList Get-UcsCcoImageCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)12
Configure Cisco UCS PowerTool SuiteCisco UCS Hardware and Software Compatibility Tool IntegrationCisco UCS Hardware and Software Compatibility ToolIntegrationCisco UCS Hardware and Software Compatibility List (HCL) Tool provides interoperability information forUCS components and configurations tested and validated by Cisco, by Cisco partners, or both.From Release 2.1.1 of UCS PowerTool Suite, custom cmdlets for interacting with the HCL tool are added.With this feature, you can create a Hardware Profile from a UCS blade or rack server and upload it to theHCL tool. Also, you can get the recommended versions of the firmware or driver versions from the HCL toolby selecting the uploaded hardware profile.Connect to Cisco UCSBefore executing any cmdlet, you should first connect to Cisco UCS using the following:C:\ cred Get-CredentialC:\ ucs Connect-Ucs -Name IP Address -Credential credGet-UcsOsVendorThe Get-UcsOsVendor cmdlet is used to get the operating system vendor code and name from the HCL tool.SyntaxGet-UcsOsVendor [-Id string ] [-Proxy WebProxy ] [ CommonParameters ]Detailed DescriptionPropertyDescriptionRequiredIdSpecifies the OsVendor Id.FalseProxySpecifies the web proxy to be used Falsefor the communication with HCLapi.CommonParametersThis cmdlet supports the commonparameters: -Verbose, -Debug,-ErrorAction, -ErrorVariable,-OutBuffer, and -OutVariable.ExampleC:\ osVendor Get-UcsOsVendorC:\ OSVendorT SuSEOracleRed HatVMwareCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)13
Configure Cisco UCS PowerTool SuiteCisco UCS Hardware and Software Compatibility Tool he Get-UcsOperatingSystem cmdlet is used to get all the supported operating systems for the selected vendor.SyntaxParameter Set: VendorGet-UcsOperatingSystem -OsVendor OsVendor [-Proxy WebProxy ] [ CommonParameters ]Parameter Set: IdGet-UcsOperatingSystem -OsVendorTreeId string [-Proxy WebProxy ] [ CommonParameters ]Detailed ifies the OsVendor object.TrueOsVendorTreeIdSpecifies the tree id of OsVendor.TrueProxySpecifies the web proxy to be used Falsefor the communication with HCLapi.CommonParametersThis cmdlet supports the commonparameters: -Verbose, -Debug,-ErrorAction, -ErrorVariable,-OutBuffer, and -OutVariable.ExampleThe following example has Microsoft OS vendor details passed as osVendor[1].C:\ osVersion Get-UcsOperatingSystem -OsVendor osVendor[1]C:\ osVersionT N--------Windows ServerWindows ServerWindows ServerWindows ServerWindows ServerWindows ServerWindows Server2008201220082012200820192016R2 SP1R2R2SP2New-UcsHardwareProfileThe New-UcsHardwareProfile cmdlet is used to create a hardware profile from the selected server. Thehardware profile created using this cmdlet can be uploaded to the HCL tool using the Add-UcsHardwareProfilecmdlet. This cmdlet takes managed object of the type ComputeBlade, ComputeRackUnit, ComputeServerNode,and ServiceProfile as pipeline input. By default, the cmdlet collects the serial number of the server. If you donot want the cmdlet to collect the serial number, use the -NoSerialNumber switch parameter.SyntaxCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)14
Configure Cisco UCS PowerTool SuiteCisco UCS Hardware and Software Compatibility Tool IntegrationNew-UcsHardwareProfile [-NamePrefix string ] [-NoSerialNumber] -ManagedObject ManagedObject -OsVendorCode string -OsVersionCode string [-Ucs BaseHandle[] ] [ CommonParameters ]New-UcsHardwareProfile -Name string [-NoPostFix] [-NoSerialNumber] -ManagedObject ManagedObject -OsVendorCode string -OsVersionCode string [-Ucs BaseHandle[] ][ CommonParameters ]Detailed s the name of the Hardware Trueprofile.NamePrefixSpecifies the name prefix of theHardware profile.FalsePathSpecifies path at which theHardware Profile JSON file islocated.TrueLiteralPathSpecifies path at which theHardware Profile JSON file islocated.TrueNoPostFixSpecifies that the cmdlet does not Falseattach the postfix string to theHardware Profile name.ManagedObjectSpecifies the managed object. You Truecan pass an associatedServiceProfile or blade or RackUnitor ServerNode as the parameter orfrom pipelineNoSerialNumberSwitch parameter instructs cmdlet Falsenot to capture Serial Number insidethe Hardware Profile.OsVendorCodeSpecifies the operating system'svendor code obtained usingGet-UcsOsVendor cmdlet.OsVersionCodeSpecifies the operating system code Trueobtained usingGet-UcsOperatingSystem cmdlet.UcsSpecifies the ucs handle or handles FalseCommonParametersThis cmdlet supports the commonparameters: -Verbose, -Debug,-ErrorAction, -ErrorVariable,-OutBuffer, and -OutVariable.TrueExampleCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)15
Configure Cisco UCS PowerTool SuiteCisco UCS Hardware and Software Compatibility Tool IntegrationC:\ managedObject Get-UcsManagedObject -Dn "sys/rack-unit-1"C:\ hardwareProfile New-UcsHardwareProfile -Name "Test-HardwareProfile"-OsVendorCode osVendor[1].ID -OsVersionCode osVersion[1].ID-ManagedObject managedObjectC:\ hardwareProfile ConvertTo-Json -Depth 100 Out-File C:\hardwareProfile.jsonAdd-UcsHardwareProfileThe Add-UcsHardwareProfile cmdlet is used to upload the hardware profile to the HCL tool. Specify theCisco.com credentials and hardware profile objects which were created using the New-UcsHardwareProfilecmdlet. You can save multiple hardware profiles for the account specified. You can also specify the JSONfile as input for uploading a hardware profile to the HCL tool. These hardware profiles can be used later toget the information about the recommended driver and firmware versions for the adaptors.SyntaxAdd-UcsHardwareProfile -Credential PSCredential -HardwareProfile CiscoHardwareProfile [-Proxy WebProxy ] [-Xml] [ CommonParameters ]Add-UcsHardwareProfile -Credential pscredential -Path string [-Proxy WebProxy ][-Xml] [ CommonParameters ]Add-UcsHardwareProfile -Credential pscredential -LiteralPath string [-Proxy WebProxy ] [-Xml][ CommonParameters ]Detailed fies the hardware profileTrueobject created using theNew-UcsHardwareProfile cmdlet.ProxySpecifies the web proxy to be used Falsefor the communication with HCLapi.CredentialSpecifies the Cisco.com credential Trueof user.PathSpecifies path at which Hardware TrueProfile JSON file is locatedLiteralPathSpecifies path at which Hardware TrueProfile JSON file is located.CommonParametersThis cmdlet supports the commonparameters: -Verbose, -Debug,-ErrorAction, -ErrorVariable,-OutBuffer, and -OutVariable.ExampleCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)16Required
Configure Cisco UCS PowerTool SuiteCisco UCS Hardware and Software Compatibility Tool IntegrationC:\ result Add-UcsHardwareProfile -Credential cecCred -Path C:\hardwareProfile.jsonC:\ ::::::2019-06-20T06:37:07 00:002019-06-20T06:37:07 00:009463Test-HardwareProfile leThe Get-UcsHardwareProfile cmdlet is used to get all the hardware profiles present in the HCL tool for thegiven cisco.com credential. You can use the optional name or Id parameter to get the specific hardware profile.SyntaxParameter Set: DefaultGet-UcsHardwareProfile -Credential PSCredential [-Proxy WebProxy ] [ CommonParameters ]Parameter Set: NameGet-UcsHardwareProfile -Credential PSCredential -Name string [-Proxy WebProxy ][ CommonParameters ]Parameter Set: IdGet-UcsHardwareProfile -Credential PSCredential -Id string [-Proxy WebProxy ][ CommonParameters ]Detailed s the name of the Hardware Trueprofile.IdSpecifies the name of the Hardware TrueProfile.ProxySpecifies the web proxy to be used Falsefor the communication with HCLapi.CredentialSpecifies the Cisco.com credential Trueof user.CommonParametersThis cmdlet supports the commonparameters: -Verbose, -Debug,-ErrorAction, -ErrorVariable,-OutBuffer, and -OutVariable.ExampleC:\ getHardwareProfile Get-UcsHardwareProfile -Credential cecCred -Name"Test-HardwareProfile 0"C:\ getHardwareProfileCreationDate : 2019-06-20T06:37:07 00:00LastModified : 2019-06-20T06:37:07 00:00Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)17
Configure Cisco UCS PowerTool SuiteCisco UCS Hardware and Software Compatibility Tool IntegrationCecIdIdNameUcsServer:: 9463: Test-HardwareProfile 0: fileThe Remove-UcsHardwareProfile cmdlet is used to delete the hardware profile from the HCL tool.SyntaxRemove-UcsHardwareProfile -Credential PSCredential -HardwareProfile CiscoHardwareProfile [-Proxy WebProxy ] [ CommonParameters ]Remove-UcsHardwareProfile -Credential PSCredential -Id string [-Proxy WebProxy ][ CommonParameters ]Remove-UcsHardwareProfile -Credential PSCredential -Name string [-Proxy WebProxy ][ CommonParameters ]Detailed s the name of the Hardware Trueprofile.IdSpecifies the name of the Hardware TrueProfile.ProxySpecifies the web proxy to be used Falsefor the communication with HCLapi.CredentialSpecifies the Cisco.com credential Trueof user.CommonParametersThis cmdlet supports the commonparameters: -Verbose, -Debug,-ErrorAction, -ErrorVariable,-OutBuffer, and -OutVariable.ExampleC:\ Remove-UcsHardwareProfile -Credential cecCred -Name "Test-HardwareProfile 0"Hardware Profile with Name Test-HardwareProfile 0 removed successfullyInvoke-UcsHclUtilityThe Invoke-UcsHclUtility cmdlet is used to get the recommended driver and firmware versions of the adaptorsfor the hardware profile available in the HCL tool.SyntaxInvoke-UcsHclUtility -Credential PSCredential -HardwareProfile CiscoHardwareProfile [-Proxy WebProxy ] [-Tree] [-Advisories] [-AdvisoryType string ] [ CommonParameters ]Invoke-UcsHclUtility -Credential PSCredential -Name string [-Proxy WebProxy ] [-Tree][-Advisories] [-AdvisoryType string ] [ CommonParameters ]Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)18
Configure Cisco UCS PowerTool SuiteCisco UCS Hardware and Software Compatibility Tool IntegrationInvoke-UcsHclUtility -Credential PSCredential -Id string [-Proxy WebProxy ] [-Tree][-Advisories] [-AdvisoryType string ] [ CommonParameters ]Detailed DescriptionPropertyDescriptionNameSpecifies the name of the Hardware Trueprofile.AdvisoriesSpecifies the switch parameter to Falseshow the Advisories published forthe components or adaptors that ispart of the hardware profile.AdvisoriesTypeSpecifies the type of advisory to be Falsefetched.TreeIf specified, the cmdlet displaysdetailed output in a tree view.NoteRequiredFalseIf you use -Tree, thenyou cannot use theoutput of cmdlet for thepipelineHardwareProfileSpecifies the hardware profileobject.TrueProxySpecifies the web proxy to be used Falsefor the communication with HCLapi.CredentialSpecifies the Cisco.com credential Trueof user.CommonParametersThis cmdlet supports the commonparameters: -Verbose, -Debug,-ErrorAction, -ErrorVariable,-OutBuffer, and -OutVariable.ExampleC:\ hclResult Invoke-UcsHclUtility -Credential cecCred -Name "Test-HardwareProfile 0"C:\ hclResultCompatibilityProfiles Advisories--------------------- ---------{810}C:\ hclResult.CompatibilityProfilesVersion: oad/release.html?mdfid 283862063&flowid 25886&softwareid 283655681Cisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)19
Configure Cisco UCS PowerTool SuiteCisco UCS Hardware and Software Compatibility Tool IntegrationInstallationDocUrl ides-list.htmlDriverIsoDownload 3/type/283853158/release/4.0(1)HardwareTypes: Cisco.Ucs.Core.HardwareTypesComponent: {ST1000NM0045, HUSMR7680BDP301, Micron 5100 MTFDDAV240TCB}OsVersion: Windows Server 2019OsVendor: MicrosoftOsVersionId: 810OsVendorId: 1Notes: {96 : Requires minimum FW version 4.1.2d}Get-UcsHclAdvisoryTypesSyntaxTo view the advisories for the server model and its components, use the Get-UcsHclAdvisoryTypes cmdlet.Get-UcsHclAdvisoryTypes -Credential pscredential [-Proxy WebProxy ][ CommonParameters ]PropertyDescriptionRequiredCredentialSpecify the Cisco.com usercredentialTrueProxySpecify the web proxy to be used Falsefor communicating with HCL API.CommonParametersThis cmdlet supports the commonparameters: Verbose, Debug,ErrorAction, ErrorVariable,WarningAction, WarningVariable,OutBuffer, PipelineVariable, andOutVariable.ExampleC:\ advisoryResult Get-UcsHclAdvisoryTypes -Credential cecCredC:\ advisoryResultEOL AdvisoryField NoticeCisco UCS PowerTool Suite Installation and Configuration Guide, Release 3.0(2)20
Cisco UCS Manager PowerTool Release 3.x User Guide Cisco IMC PowerTool, Release 3.x User Guide Cisco UCS Central PowerTool, Release 3.x User Guide Cisco UCS Documentation Roadmap Cisco UCS C-Series Documentation Roadmap Cisco UCS Central ConfigurationGuides OtherDocumentationResources
Cisco UCS Manager PowerTool is a PowerShell module which helps automate all aspects of Cisco UCS Manager including server, network, storage and hypervisor management. PowerTool enables easy integration with existing IT management processes and tools. The PowerTool cmdlets work on the UCS Manager's Management Information Tree (MIT), performing
Cisco Certified Internetwork Expert logo, Cisco IOS, Cisco Press, Cisco Systems, Cisco Systems Capital, the Cisco Systems logo, Cisco Unified Computing System (Cisco UCS), Cisco UCS B-Series Blade Servers, Cisco UCS C-Series Rack Servers, Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS
2.1. Cisco UCS 5108 Chassis 9 2.2. Cisco UCS Fabric Interconnects 9 2.3. Cisco UCS Fabric Extenders 10 2.4. Cisco UCS Blade Servers 11 2.5. Cisco UCS Rack Mount C-Series Servers 11 2.6. Virtual Interface Cards (VIC) and other Network Adapters 11 2.7. Cisco UCS Manager (UCSM) 12 2.8. Physical Scope of the TOE 13 2.9. Logical Scope of the TOE 15
Cisco UCS anatomy gives a nuts-and-bolts description of Cisco UCS in terms of how our components—Cisco Unified Fabric, Cisco UCS management, and Cisco UCS servers—combine to create a single unified system. The next three sections, Unified I/O architecture, Cisco UCS management, and Cisco UCS servers take a deep dive into the
Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS Management Software, Cisco Unified Fabric, Cisco Application Centric Infrastructure, Cisco Nexus 9000 Series, Cisco Nexus 7000 Series. Cisco Prime Data Center Network Manager, Cisco NX-OS Software, Cisco MDS Series, Cisco Unity, Collaboration Without
Cisco UCS Fabric Interconnects (Read Only / Cut Through Interfaces) SNMP, Syslog, SMTP, SMASH CLP, CIM XML, Smart Call Home 20, 40, 48, and 96 portsCisco UCS I/O Modules and FEX's Cisco UCS Blade Server Chassis Cisco UCS Blade and Rack Servers (Cut through Interfaces to CIMC) Serial over LAN, KVM, IPMI Cisco UCS I/O Adapters Cisco UCS Manager
SQL Server 2016 Databases on Cisco HyperFlex 3.5.1a and Cisco UCS C240 M5 All-Flash Systems with Windows Server 2016 Hy-per-V Last Updated: December 14, 2018 . 2 . Blade Servers, Cisco UCS C-Series Rack Servers, Cisco UCS S-Series Storage Servers, Cisco UCS Manager, Cisco UCS Management Software, Cisco Unified Fabric, Cisco Application .
RTS performs tree risk assessment in accordance with ANSI A300 (Part 9) - Tree Risk Assessment. Not only because we must as ISA Certified Arborists who are Tree Risk Assessment Qualified (TRAQ), but also because it ensures consistency by providing a standardized and systematic process for assessing tree risk. Risk assessment via TRAQ methodology takes one of three levels, depending on the .
