my personal blog about systemcenter

All posts in NetApp

‘VMNAME’ could not initialize. (Virtual machine ID GUID)

Categories: Hyper-V, NetApp
Comments Off on ‘VMNAME’ could not initialize. (Virtual machine ID GUID)

Recently ran into a issue where i couldnt start a VM located on a NetApp Running SMB 3.

Rights on the filesystem looked without issue , opening the vhd over the network worked but anything manipulated from HYper-V failed with a resource attached to the system failed.

After digging around a bit i found that the time was shifted on the NetApp box so any kerebous authentication failed

image

And the culprint on the NetApp was

secd.kerberos.clockskew: Kerberos client or node clock skew error (-1765328351). 

Description :

This message occurs when there is a “time error”(clock skew, time skew, time out of bounds). This error indicates that there is a time discrepancy between client and node or client and Key Distribution Center (KDC). The kerberos authentication request from the client was forwarded to the KDC and it failed because the timestamp encrypted in the client’s kerberos ticket was different by more than the maximum time difference that is configured on the KDC.

Action :

Ensure that the clock time of the node is identical to that of the client and to that of the KDC. Ensure that the correct time zone setting is selected on the node. To keep the node and KDC time clocks in synchronization automatically, configure Network Time Protocol (NTP) services on the node. You might also want to increase the clock skew interval. To do so, modify the kerberos-realm configuration clock-skew (“Maximum tolerance for computer clock synchronization” in Windows(R) Active Directory) parameter from the default 300 seconds to 600 seconds or more. Note: Increasing the clock-skew interval makes the client protocols less secure against network replay attacks.

and then setting a NTP server that actually worked then everything was working again after a few minutes.

And then setting a NTP server on the NetApp box that are in sync with ActiveDirectory = Sucess.

Basic Install NetApp OnCommand C-Mode NetApp FAS 2552

Categories: NetApp, Operations Manager, SCOM
Comments Off on Basic Install NetApp OnCommand C-Mode NetApp FAS 2552

So we just to a new shiny FAS 2552 for use with NetApp Shift , we wanted to setup basic monitoring to start with to ensure that everything is in working order and status that way , NetApp will alert on critical errors though autosupport but putting everything together in a single place of glass eg Operations Manager makes a good case.

Sign in to your now account and download OnCommand 4.0.1 or newest version

 

This install will cover the basics and as soon as we get the box closer to production a new post will be added with further details

 

image

The OnCommand PlugIn require a named user during install to host the webservice , the account MUST be local admin on the Operations Manager management server you install on , be aware that default Operations Manager installation will make this user full admin in Operations Manager , so ensure that the BUILINT\Administrators don’t have full admin rights to Operations Manager

 

image

Start the installer on a Operations Manager management server

image

Add Console Integration/Management Packs , for the purpose of this post we wont cover VMM integration or shell

 

image

Add the named user created before install start

image

The installer imports management packs , in our environment took less than 10 minutes

image

Sucess :)

image

In OnCommand System Manager create a user with api access and read only , this is to ensure that we keep high privilege access account to a few as possible

 

image

Onder Cluster Data OnTap Management Servers Select Manage Storage Systems

image

Add the IP/DNS name for the Cluster Node , during initial setup i got a “Value cannot be null”

This was due to no Storage Virtual Machines created as this was a brand new install

image

As this is just a test install for now i just created a SVM just with CIFS just to get beyond the error during install

image

And back to adding the Storage System to the Operations Manager

 

image

 

Sucess :)

 

image

To avoid waiting for the schedules discovery i ran a discovery task to speed up things

image

And a few minutes later we start getting info about our shift FAS box

image

And hardware status

If you install the Management Pack after configuration of the Filer you wont see the Null Error

Next step is looking at rules/monitors/reporting

 

Have Fun