Skip to main content

New home server environment

Well, with the days off I took, plus a few extra bits of hardware, things are shaping up nicely.

Hyper-V server
Motherboard: Asus P5E-VM HDMI LGA775
RAM: 2x2GB & 2x1GB Mushkin PC2
CPU: Intel E6400 2.13GHz
Disks: 160GB Seagate SATA for boot, 8x1TB WD Black in RAID5
Cards: Dell-branded LSI 8408 Dual SAS w. SAS-SATA breakout cables, Intel PRO/1000 CT nic

Running 2008 R2 x64 with Hyper-V and the Starwind iSCSI target. The RAID5 array is broken down into three 1.8TB and one 1TB logical disks, the former being used as VMFS iSCSI datastores and the latter using NFS and SMB shares for ISOs, files, etc. The VHDs for the Hyper-V part of the server are also stored on this disk.

The Starwind was super-easy to set up, only hitch I ran into was that I needed to restart the Starwind/iSCSI initiator services to get ESX seeing the LUNs. Performance is 'just fine' so far - nothing empirical to report, yet.

The on-board nic is used for LAN access, while the CT card is used for iSCSI, each on their own separate Gb switches (a Dell 2708 and D-Link Green, both 8-port). I had to disable the Hyper-V vSwitch to get LAN access working may need to tinker with that yet. Also, had to disable the firewall to get iSCSI working, even with the proper in/outbound rules enabled. I'm guessing there are some ports needed that are not documented or somesuch. Both ESX and Hyper-V have 3260 open, so not sure what else is needed.

Still trying to decide what to do with the Hyper-V box...for sure a VC is going on there, not sure what else yet. 6GB doesn't give me a huge amount of room, especially with a VC in the works that'll need 2-3GB of RAM just for itself.

ESX vSphere server
Motherboard: Asus P6T SE X58 LGA1366
RAM: 6x2GB G.Skill DDR3-1600
CPU: Intel i7 920 2.66GHz
Disks: 36GB SATA Raptor
Cards: Two Intel PRO/1000 CT nics

Running ESX 4.0 (or vSphere, as it's being called). I've not separated the service console from the VM Network, as I needed the second nic for iSCSI, and due to the strict HCL, I cannot use the on-board nic. Still need to get the VC operational.

Plans are to run a 2008 R2 domain for MCITP purposes, as well as a few BSD/Asterisk machines for some other work I'm doing.

I'll try and keep more posted here in future, I've been lax about it as of late.


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…