Skip to main content

Lab update 2014 - thanks, Mister Lab

After a few years now of running a fair-size home VMware lab - my thoughts.

  • It has gotten me two jobs so far - or rather, it has piqued the interest of interviewers - and thus paid for itself several times over with the resulting salary increases.  Good job, Mister Lab.
  • It did help me with the VCP4 certification (even though the exam was garbage) - I felt that using physical hosts vs. virtual hosts did give me a 'real-world' advantage, especially around troubleshooting.
  • I am now at the point where I've outgrown it, in a way.  Or rather, I can only go so far with it, so my time is better spent using old equipment from work. 
  • To clarify the point above - I have three 16GB hosts at home, but three 64GB hosts at work.  Math is simple.  OpenFiler "SAN" at home, true iSCSI SAN(s) at work.  Etc.
  • SSDs were 'just' coming out when I built this - or rather, they were just becoming affordable.  My 15k SAS array is kinda stupid now compared to SSD performance/power consumption/price.
  • The FC stuff I learned was interesting, but didn't really come close to what you would actually do with FC in a real environment.  It was cheap, so no real regrets, but ended up not being super-helpful, either.
  • My workstation with 24GB (meant to supplement the lab) ended up being used almost as much, even if it was annoying when it came time for (Windows) reboots and such.
So all that said, I think I'll be shutting down the lab for the time being.  It'll save us ~800w of continuous power draw, and it's not like I'm stopping labwork - just moving on to a better environment.

Comments

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$\user.name\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):
MSSQLSVC/tor-sql-01.domain.local:1433

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

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/server1.company.local:1433 is registered on these accounts:
CN=SERVER1,OU=servers,OU=resources,DC=company,DC=local
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 going...so here's a config and brain dump...

Why?
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)

How?
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
OMD
Open Monitoring Distribution, but the real point here is Check_MK (IIRC Icinga uses this...).  It makes Nagios easy to use and main…