Skip to main content

LVS - Adding the 2nd array

Update:  Wiki article here:

I had set up the FC array with only half the disks, thinking I would just add a 2nd disk later.  Once I discovered that Openfiler uses LVM, I wanted to just extend the current LV.

First, I wanted to move the VMs off this LV just in case, and of course that was no simple matter.  I had no vCenter server set up, so had to do that (from scratch), then discovered that when I migrated the VMs from Workstation 8 into ESXi 4.1, all VMware Tools bits broke.  Disks went offline, network stuff had to be removed/re-added, OS type reset to 'unknown', etc.

With the vCenter install, discovered a few key points:

  1. To use a remote SQL server, you need to install the SQL native client 10.0 (gives you a 64-bit DSN).
  2. If you set the vCenter to auth by a set account, like a service account, you lose AD logon for other users.
  3. Firewall!  Don't forget about me!  I just turned it off for now, but will be re-enabling once I have time to do a wiki article on it.
  4. This guy has instructions for a scripted DSN config:
  5. This also came up:
  6. And finally, don't forget that it requires the .NET framework component installed (default option under the 'application server' feature).

Ok...vCenter done and VMs moved to the SATA array on iSCSI.  Performance for the storage vMotion seems pretty good.

The LVS troubleshooting I've placed on the wiki.  Quickly before I left this morning I tested things out - and all is good!  Now have a single FC target that is 516GB!  To be honest, I'm not sure that's a good thing - I will test things out again tonight by breaking the LV down and setting up multiple smaller targets, say two per RAID card.  You can also do mirroring...maybe I could do two smaller targets mirrored across two arrays? Lots of fun stuff.


Popular posts from this blog

DFSR - eventid 4312 - replication just won't work

This warning isn't documented that well on the googles, so here's some google fodder:

You are trying to set up replication for a DFS folder (no existing replication)Source server is 2008R2, 'branch office' server is 2012R2 (I'm moving all our infra to 2012R2)You have no issues getting replication configuredYou see the DFSR folders get created on the other end, but nothing stagesFinally you get EventID 4312:
The DFS Replication service failed to get folder information when walking the file system on a journal wrap or loss recovery due to repeated sharing violations encountered on a folder. The service cannot replicate the folder and files in that folder until the sharing violation is resolved.  Additional Information:  Folder: F:\Users$\\Desktop\Random Folder Name\  Replicated Folder Root: F:\Users$  File ID: {00000000-0000-0000-0000-000000000000}-v0  Replicated Folder Name: Users  Replicated Folder ID: 33F0449D-5E67-4DA1-99AC-681B5BACC7E5  Replication Group…

Fixing duplicate SPNs (service principal name)

This is a pretty handy thing to know:

SPNs are used when a specific service/daemon uses Kerberos to authenticate against AD. They map a specific service, port, and object together with this convention: class/host:port/name

If you use a computer object to auth (such as local service):

If you use a user object to auth (such as a service account, or admin account):

Why do we care about duplicate SPNs? If you have two entries trying to auth using the same Kerberos ticket (I think that's right...), they will conflict, and cause errors and service failures.

To check for duplicate SPNs:
The command "setspn.exe -X

C:\Windows\system32>setspn -X
Processing entry 7
MSSQLSvc/ is registered on these accounts:
CN=SQL Admin,OU=service accounts,OU=resources,DC=company,DC=local

found 1 groups of duplicate SPNs. (truncated/sanitized)

Note that y…

Logstash to Nagios - alerting based on Windows Event ID

This took way longer than it should have to get here's a config and brain dump...

You want to have a central place to analyze Windows Event/IIS/local application logs, alert off specific events, alert off specific situations.  You don't have the budget for a boxed solution.  You want pretty graphs.  You don't particularly care about individual server states.  (see rationale below - although you certainly have all the tools here to care, I haven't provided that configuration)

ELK stack, OMD, NXlog agent, and Rsyslog.  The premise here is as follows:

Event generated on server into EventLogNXlog ships to Logstash inputLogstash filter adds fields and tags to specified eventsLogstash output sends to a passive Nagios service via the Nagios NSCA outputThe passive service on Nagios (Check_MK c/o OMD) does its thing w. alerting
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…