Server Management and Automation Windows Server 2012 R2

Server Management and AutomationWindows Server 2012 R2 Won Huh Product Marketing Manager

Transformational trends Cloud computing New social and app patterns Compute Storage Network Data explosion Consumerization of IT

Customer needs and opportunities IT budgets flat or shrinking even as business expectations increase. Provide differentiated services to customers. We spent most of our time keeping the lights on, not staffed to take on impactful projects. Enable me to build and operate infrastructure efficiently across my customer base. Need a solution that works across my diverse datacenter environments. Protect my existing investments through easy systems integration. Application owners pressing us for agility and availability, going directly to public clouds.

Scenario summary Ecosystem and extensibility Simplify your routine tasks Multiserver management Deployment options Standards-based management

Standards-based management Simplifies the management of a diverse ecosystem Standard APIs Windows Management Framework Standard protocols Standard models

Managing a diverse ecosystem STANDARDS-BASED MANAGEMENT “The NxM Problem” IT Pro Tool Developer Solution Provider Number of devices to manage Methods to manage each device Disk Storage Operating system Devices Managed objects

Windows Management Framework STANDARDS-BASED MANAGEMENT Maximize the value of using the Windows Management Framework IT Pro Tool Developer Solution Provider Windows Management Framework Disk Storage Operating system Devices Managed objects

Standard models, protocols, and APIs STANDARDS-BASED MANAGEMENT Maximize the value of using the Windows Management Framework IT Pro ToolDeveloper Solution Provider Standard APIs: MI Client, Windows PowerShell, Open Data Protocol (OData) Windows Management Framework Standard protocols: WS-Management, REST, HTTP, PSRP Standard models: Common Information Model (CIM) schema, Storage Management Initiative Specification (SMI-S) Disk Storage Operating system Devices Managed objects

OpenManagment Infrastructure STANDARDS-BASED MANAGEMENT • New WMI provider API (MI) with extended Windows PowerShell semantics. • Open Management Infrastructure (OMI) for Linux and UNIX with the same MI provider API. • Full implementation of WS-Man on Windows and Linux/UNIX. • New MI client with integrated Windows PowerShell layer. Windows Linux/UNIX Windows PowerShell MI provider Classic provider MI provider MI client API Microsoft .NET MI API Native MI API Windows Management Instrumentation Open Management Infrastructure Any device WS-Man protocolhandler WS-Man protocol handler WS-Man protocol handler WS-Man protocol handler WS-Management

One Management Infrastructure STANDARDS-BASED MANAGEMENT Open source Windows Management Infrastructure server implemented by Microsoft. • Includes Windows Server Management protocol stack. • Interacts with MI client and Windows PowerShell outofthebox. Portable • Uses the same MI provider interface as Windows Management Infrastructure. • Can share provider development tools with Windows Management Infrastructure. Scalable Small footprint

Open Management Infrastructure vs. OpenPegasus STANDARDS-BASED MANAGEMENT

Approach for Windows Server 2012 R2 STANDARDS-BASED MANAGEMENT Simplify and lower the cost of: • Instrumenting services and devices for Windows—through Windows Management Infrastructure (WMI) providers. • Developing PowerShell cmdlets in native code, as CIM providers. • Standards-based way to access and manage storage. • SMI-S service in the box for easier storage discovery. Use SMI-S to manage external storage arrays: Use OMI to manage network switches: • Standards-based way to access and manage network switch. • OMI in the box for configuring network switch.

Switch managementStandards based automation Easily deploy and operate network switches in standards approach Switch x CIM • PowerShell scripts for common switch management tasks. • SCVMM imports and validates port configuration from switch. • Logo Program: Server Certification for switch endors implementing CIM Schema. • Define mechanisms to auto generate PowerShell cmdlets for vendor extensions. Windows (PowerShell) Switch y CIM WS-Man SCVMM Non-Windows Switch z CIM

Switch SchemaHigh level overview

Sample PowerShell script $tors="192.168.0.1","192.168.0.2","192.168.0.3" $so=New-CimSessionOption-UseSsl $s=New-CimSession-CN$tors-port7779-AuthBasic-Credential$cred -Sessionoption $so #enable SSH Feature $ssh=Get-CimInstance-CimSession$s MSFT_Feature|? FeatureName -eq2 Set-CimInstance-CimSession$s $ssh-Property @{ IsEnabled =$true } #Enable all ports $ports=Get-CimInstance-CimSession$s CIM_EthernetPort $ports |Invoke-CimMethod-MethodRequestStateChange-Parameter @{ RequestedState =2} #Set a Port to trunk mode and specify list of VLANs $lanep= Get-CimAssociatedInstance$ports[5]-ResultClassNameCim_LanEndpoint $vlanep=Get-CimAssociatedInstance$lanep-ResultClassNameCim_VLanEndpoint $vlanepsd=Get-CimAssociatedInstance $vlanep -ResultClassNameCim_VLanEndpointSettingData #Set Port Mode to Trunk Set-CimInstance $vlanep-Property @{DesiredEndpointMode =5} #Set list of trunk VLANs Set-CimInstance$vlanepsd-Property @{TrunkVlanList=“2,3,4”}

Out-of-band hardware managementStandards based automation Manage hardware in standards approach BMC x SMA S H • Support multiple industry standards, schemas and protocols. • PowerShell Cmdlets and WMI provider shipping in box to provide a common abstraction layer. • Test scripts for validating hardware implementation. SMASH (WS-Man) BMC y I P M I PCSV IPMI (RMCP+) Windows (PowerShell) PCSV (WS-Man) BMC z PCSV

Sample PowerShell script #### Currently customers have no easy way to automate hardware management . #### Different vendors support different protocols /mechanisms - and PowerShell coverage is low #### In Windows Server v.Next - customers will be able to consistently manage hardware from different vendors #### Key point to note here # - Simplicity and elegance # - Rich PowerShell experience # Get data from the devices - In this demo we are managing three different BMCs $a=Get-PCSVDevice10.20.30.111-Credentialadmin-AuthDefault-ProtocolIPMI $b=Get-PCSVDevice10.20.30.112-Credentialadmin-AuthDigest-ProtocolSMASH $c=Get-PCSVDevice10.20.30.113 -Credentialadmin-AuthDigest-ProtocolPCSV $hosts= $a,$b,$c $hosts |SelectManufacturer,Model,FirmwareVersion # Show Manufacturer, Model and Firmware Version $hosts|SelectPowerState # Show Current Power State $hosts|Set-PcsvDevice-NextBoot"Network“ # Set to PXE Boot from network $hosts|Restart-PcsvDevice# Restart the machines. This will prompt the user to # confirm because this is a "high impact action" $hosts|Restart-PcsvDevice–Force # Use force to suppress prompt and restart machine

Sample PowerShell script $a = Get-PcsvDevice -TargetComputerName$ip-ManagementProtocol IPMI -Credential $cred # Switch ON the machine $a | Start-PcsvDevice $a | Stop-PcsvDevice # Common automation scenario - set the machine to boot from network and restart the machine. # Let’s see how to do it using PCSV cmdlets in a pipeline # Step 1 - Set the machine to boot from network , but just for the next boot # Step 2 - Reboot the machine $bmc= Get-PcsvDevice -TargetComputerName$ip-ManagementProtocol IPMI -Credential $cred $bmc | Set-PcsvDeviceBootConfiguration -OneTimeBootSource "CIM:Network:1" -PassThru | Restart-PcsvDevice • PS C:\> $ip= "10.10.1.10" • PS C:\> Get-PcsvDevice -TargetComputerName$ip-ManagementProtocol IPMI -Credential $cred • TargetComputerName Manufacturer Model SerialNumberEnabledState • ------------------ ------------ ----- ------------ ------------ • 10.10.1.10 DELL PowerEdge R720 CN7123456700EH Disabled

Server Management and Automation Windows Server 2012 R2