Archive by category "System Center"

IBM Storage management pack SCOM

With the SCOM management pack for IBM you can monitor the following systems:

  • DS8000
  • Flex Systems
  • SAN Volume Controller (SVC)
  • Storwize V3500
  • Storwize V3700
  • Storwize V5000
  • Storwize V7000 & Unified
  • XIV Systems

Logon to your storage system. Add a user for monitoring purpose in the monitoring user group.
Be sure that port 22 is open from the SCOM landscape to the IBM Management Addresses.

Download the newest IBM_Storage_MP_for_SCOM_#.#_Windows setup from the IBM site.
Install the IBM Storage SCOM-control utility.

Import the SCOM management packs, the setup placed them on:
C:\Program Files\IBM\Storage\Host\IBMStorageSCOM\mps

Open the configuration utility command line.

Link IBM Storage SCOM-Control utility with SCOM:
scomu.cmd --sc-set --servername scomsrv01 --domain domain01 --username usr --password pass

Choose:

  • Password authentication mode:
    scomu.cmd --add -t storwize --ip #### --authmode password --username ### --password ###
  • Public key authentication mode:
    scomu.cmd --add -t storwize --ip #### --authmode publickey --username ### --certpath c:\storwize.cert --passphrase xxxxx

List the added storage systems:
scomu.cmd --list

Delete a connection:
scomu.cmd --del -t storwize.v7000 --ip 172.24.101.175

Remove Temporary Template SCVMM

When you manually remove a .VHD file from the library, is it possible that you cannot remove the template from the SCVMM library. The template has some Temporary  Template dependencies on it. On the dependencies tab in your template configuration file you see the Object that is linked.

Solution:

Double click on the linked object and copy the name.

Open a Virtual Machine Manager Powershell

remove-scvmtemplate -vmtemplate "Temporary Template1c2fe 00e-4d16-4975-b85b-8c4fad34fff5"

Once runned the linked temporary template has been removed and you are able te remove te template.

VMM Cannot find the device or this device is not valid for a boot device.

This error occurs when you rollout a Generation 2.
Issue occurs because the Bootmgfw.efi file is set as the first startup device that the VM tries to start from, instead of the .vhdx file which contains the operating system.

Solution:

To resolve this issue you must change the firstbootdevice in the template.
Open a Virtual Machine Manager Command Shell:

Get-SCVMTemplate -name “Windows 2012 VM Template” | Set-SCVMTemplate -FirstBootDevice “SCSI,0,0″

Change multiple GEN2 templates.

Get-SCVMTemplate | where-object {$_.FirstBootDevice -cnotcontains "SCSI,0,0" -and $_.Generation -eq "2"} | Set-SCVMTemplate -FirstBootDevice "SCSI,0,0"