Skip to main content

Where to put it all?

I was telling my wife the other day how back in college, or earlier, I would have killed for the setup I'm using now - only now, I'm finding it extremely cumbersome and prone to making my desk very unusable.

The desk measures 6x3' and is crammed to the gills with stuff - NICs, RAM, the odd HSF, headphones, CD spindles, screws & drivers, papers, four monitors, speakers, two 8-port switches, wireless router, two keyboards w. mice, and cables upon cables. No matter how often I clean it off, it gets stacked with stuff again in no time. I think the real issue is that I'm just not organized, and have no place to put things even if I was organized. The other issue is that there's a lot of junk! It spills over onto the floor, under and around the desk (where the two APC 1200VA UPSes live). This drives my wife crazy. Actually...I think all of it drives her crazy. I should do something about that...if for nothing else than to make her life a little more sane!

It doesn't help that new computer 'stuff' just keeps appearing...I may want to keep the two additional PE4600 chassis out in the garage for now... :)

Oh yeah...there are also two Antec P180's and one PowerEdge 4600 converted for ATX usage sitting on the desk, with two more standard-size cases looking for homes currently sitting on my wife's desk (it's okay, she's out of town - when she's back...not so much okay).

I've taken a 'before' picture, so hopefully before she's back I'll have an acceptable 'after' picture.

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…