my personal blog about systemcenter

Archive for January, 2014

3PAR SMI-S Provider and SCOM MP’s

Categories: 3PAR, Operations Manager, SCOM, Windows Server 2012 R2
Comments Off on 3PAR SMI-S Provider and SCOM MP’s

HP have updated their Management Pack to 3.1 and now supports Operations Manager 2012 R2 and Windows Server 2012 R2 , after adding the Management Pack in a new installation it failed with wrong password for the SMI-S Provider no matter what i did.

clip_image002

So unable to logon , recreated user in different name same result

clip_image004

after digging around a bit and reading the documentation AGAIN , i could see that the SMI-S provider isnt started pr default , so a telent to 5988 comfirmed that the 3PAR wasnt listening on that port that explained why the logon didnt work

image

So logon to 3par and “startcim”

clip_image008

We then created a new user (instead of the 3parmon user just to seperate users)

clip_image010

And assigned the browse role

clip_image012

And back to the add HP 3PAR StorServ Storage System

clip_image014

And now with greater sucess

clip_image016

And after a little while we can see the install populating in Operations Manager

So always check the documentation again Smiley

Hyper-V 2012 R2 VLAN Blues

Categories: Broken, Hyper-V, Unsupported, Virtual Machine Manager, VMM, Windows Server 2012 R2
Comments Off on Hyper-V 2012 R2 VLAN Blues

clip_image002

We have been building another Hyper-V platform and started with the management cluster , this will just use standard switches so we created a team and a Management Fabric network on that

clip_image004

We then set a VLAN for the VM’s , but no matter what we did it didnt work , looking at switches showed that the MAC address was in VLAN 10 no matter what we did

clip_image005

After digging around we looked at the network interfaces , and we had set VLAN 10 on the nic used for the Hyper-V Switch , so no matter what we set on the VM everything was forced to VLAN10

So we removed the network , set the default adapter for ManagementVM and then everything was working as designed

So its friday so we can laugh at ourself , DO NOT set a VLAN on Hyper-V port :)


HP Insight Remote Support 7.0.8 vs Hyper-V

Categories: Broken, Hyper-V, Windows Server 2012, Windows Server 2012 R2
Comments Off on HP Insight Remote Support 7.0.8 vs Hyper-V

Long story short as pr today , i nominate HP Insight Remote Support 7.0.8 to the 2014 award add programs.

clip_image002

HP Insight Remote 7.0.8 Clean Install Windows 2012 VM , running on Hyper-V 2012 R2 , YES the documentation does not state support for Hyper-V , but riddle me this we purchased for a bucket load of money HP support and HP hardware , Hyper-V is running on a Supported HP platform but registration with HP failes with a cryptic error

10 jan 2014 09:59:58.178 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No registration requested.

10 jan 2014 10:00:08.181 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No registration requested.

10 jan 2014 10:00:18.200 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No registration requested.

10 jan 2014 10:00:28.203 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No registration requested.

10 jan 2014 10:00:31.391 HPRSExecutionManager[DcsMain] INFO c.h.d.classify.ClassificationEngine – Element progress: 1 of 1: 1.0 avg. duration: 210742ms

10 jan 2014 10:00:31.391 HPRSExecutionManager[DcsMain] INFO com.hp.dcs.harvest.HarvestingEngine – Element progress: 1 of 1: 1.0 avg. duration: 1ms

10 jan 2014 10:00:38.221 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No registration requested.

10 jan 2014 10:00:48.240 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No registration requested.

10 jan 2014 10:00:50.741 HPRSExecutionManager[DcsMain] INFO com.hp.uca.discovery.DcsMainThread – Idle timer elapsed, shuting down discovery…

10 jan 2014 10:00:50.741 HPRSExecutionManager[DcsMain] INFO com.hp.uca.discovery.DcsMainThread – DcsMainThread stopped!

10 jan 2014 10:00:58.243 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No registration requested.

10 jan 2014 10:01:00.821 IntegrationManager[AdapterManager] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [CCMgr] Configuration change detected, trigger reload of subcomponents…

10 jan 2014 10:01:00.821 IntegrationManager[AdapterManager] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [TCtrl] reloadConfiguration()…

10 jan 2014 10:01:00.821 IntegrationManager[AdapterManager] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [TCtrl] reloadConfiguration(), done.

10 jan 2014 10:01:08.337 IntegrationManager[RGMgr-1] WARN c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No GDID found; ; assume the SupportNode is *NOT* registered.

10 jan 2014 10:01:08.337 IntegrationManager[RGMgr-1] WARN c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No RegToken found; assume the SupportNode is *NOT* registered.

10 jan 2014 10:01:08.337 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] No indication that SupportNode is already *registered*.

10 jan 2014 10:01:08.462 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] CheckForExternalRegistrationMessage(), got message, now set trigger for self-registration and allow immedate registration.

10 jan 2014 10:01:08.462 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] Triggered for self-registration.

10 jan 2014 10:01:08.462 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [SYNCR] New registration requested by: ‘RGMgr-1’.

10 jan 2014 10:01:08.478 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] Registration required; isRegistered[false]/new msg available[true]/internal open request[true].

10 jan 2014 10:01:18.509 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [TCtrl] All WebServiceClientManagers suspended.

10 jan 2014 10:01:18.509 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] prephaseReRegistration() done, all client other tasks suspended.

10 jan 2014 10:01:20.791 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [SC_RGMgr-1] Registration call returned failure.

10 jan 2014 10:01:20.806 IntegrationManager[RGMgr-1] WARN c.h.u.i.a.hp.remotesupport.HpAdapter – Registration failed; Registration-Service warning: type ‘ClientError'(100) Get GDID error; Failed to get GDID!

10 jan 2014 10:01:20.837 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] runRegistrationProcedureHostNode(00:00:02.328), done.

10 jan 2014 10:01:20.837 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [TCtrl] Trigger all WebServiceClientManagers to awake…

10 jan 2014 10:01:20.837 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] postphaseReRegistration() done, all client tasks triggered to accept calls.

10 jan 2014 10:01:20.837 IntegrationManager[InternalAdapter] WARN c.h.u.i.a.i.m.SupportNodeUpdater – Support Node registration has null value: oos id = 33eab9f9-6783-4ae4-9ae6-7ef88c50f332, GDID=null

10 jan 2014 10:01:30.855 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] Triggered for self-registration.

10 jan 2014 10:01:40.858 IntegrationManager[RGMgr-1] INFO c.h.u.i.a.hp.remotesupport.HpAdapter – [RGMgr-1] Triggered for self-registration.

So one suggestion was to try bare metal or another Hypervisor

clip_image004

And same install procedure , and sucess.

Time to log a support case but for now it looks like Insight Remote Support dont like Hyper-V

Windows Azure Pack Publishing using SNI

Categories: Hyper-V, VMM, Windows Azure Pack, Windows Server 2012, Windows Server 2012 R2
Comments Off on Windows Azure Pack Publishing using SNI

Windows Azure Pack uses port 30071 and 30081 for its public facing authentication and portal pr default , in our demo enviroment we wanted to pushlish these but on defalt SSL port to avoid issues with customer firewalls that could be blocking high ports.

To using a single ip for Windows Azure Pack we use Service Name Indication a feature in IIS8-> that enables “hostheader” for SSL

http://www.iis.net/learn/get-started/whats-new-in-iis-8/iis-80-server-name-indication-sni-ssl-scalability

This is a demo enviroment so we can pushlish directly from WAN to LAN without a proxy please dont do this in production

The steps here are for single server install again not prodution reference post for chaning ports

http://blogs.technet.com/b/privatecloud/archive/2013/12/10/windows-azure-pack-reconfigure-portal-names-ports-and-use-trusted-certificates.aspx

The steps needed for us (thank you to Marc van Eijk for asking why we just didnt do that) was the following

Create a dns records in the public and for

cloud.systemcenter365.com for tennant portal and cloudauth.systemcenter365.com for authentication

these point in out case to 77.233.248.6 and we have created a WAN-LAN NAT on port 80 and 443 for access

image

On our internal DNS server we created 2 zones to about going through the firewall and back when testing internally , out internal domain name is internal.systemcenter365.com , for now we used a zone for the FQDN as we only want to “regulate” the names used for Windows Azure Pack and nothing else , but we could just have created the systemcenter365.com zone internally and then created the records needed.

But for now we created a zone cloud.systemcenter365.com and cloudauth.systemcenter365.com that points to the local server hosting the endpoints , this is a requirement when using the powershell commands to install this.

We then used https://www.digicert.com/util/ digicert certification utility to order and install a public certificate so we dont remind people just to accept a certificate error.

image

We used a wildcard certificate from digicert (disclaimer :they provide for free for MVP’s)

image

On the webserver hosting the WAP endpoints

image

Change the TenantSite from 30081 to 443 and enable “Require Server Name Indication” and set the hostname to in our example cloud.systemcenter365.com

image

image

Change the Authsite from 30071 to 443 and enable “Require Server Name Indication” and set the hostname to in our example cloudauth.systemcenter365.com

After we have set the ports in IIS and enabled the SNI we need to configure Windows Azure to respond to the ports

Set-MgmtSvcFqdn -Namespace “TenantSite” -FullyQualifiedDomainName “cloud.systemcenter365.com” -Port 443 -Server sqlwap

Set-MgmtSvcFqdn -Namespace “AuthSite” -FullyQualifiedDomainName “cloudauth.systemcenter365.com” -Port 443 -Server sqlwap

Set-MgmtSvcRelyingPartySettings –Target Tenant –MetadataEndpoint ‘https://cloudauth.systemcenter365.com/FederationMetadata/2007-06/FederationMetadata.xml’ -ConnectionString “Data Source=sqlwap.internal.systemcenter365.com;User ID=sa;Password=”

Set-MgmtSvcIdentityProviderSettings –Target Membership –MetadataEndpoint ‘https://cloud.systemcenter365.com/FederationMetadata/2007-06/FederationMetadata.xml’ -ConnectionString “Data Source=sqlwap.internal.systemcenter365.com;User ID=sa;Password=”

And after chaning the fqdn and the endpoints our site now responds and works with http://cloud.systemcenter365.com

image

and a root redirect is always nice to have

DPM 2012 R2 Windows Server 2012 R2 Disable ODX

Categories: Broken, Data Protection Manager, Hyper-V, Windows Server 2012, Windows Server 2012 R2
Comments Off on DPM 2012 R2 Windows Server 2012 R2 Disable ODX

Shared Volume IO Is Paused ,

Unexpected failure. Error code: [email protected]

CSV Backup is still a challange

It seems that we are seeing some of the same issues running Data Protection Manager 2012 R2 and Windows Server 2012 R2 as we did in the earlier versions

So for now until further fixes

Set-ItemProperty hklm:\system\currentcontrolset\control\filesystem -Name "FilterSupportedFeaturesMode" -Value 1
is your best friend
This was against a HP 3PAR but its know to be a issue against EMC also