Skip to main content

Few notes on the home ESX box

I'm now running ESX within Workstation. It connects via a separate Gb NIC to the iSCSI switch on to Starwind 2TB imagefile. On the other Gb NIC is the LAN/Service console.

Note if you want to use NFS to host your ISOs on the iSCSI server: Completely doable, but if you find yourself getting 'NFS Error: Unable to Mount filesystem', it's probably because you either don't have the NFS Client firewall rule enabled, or you haven't added a VMkernel to your LAN vSwitch. I just added one with an IP address on the LAN's subnet. Did that, works like a charm now!

Oh yeah, you need root access enabled in the NFS properties on the server that is hosting your NFS share.

I also had the NUMA CPU error on booting up ESX4 inside Workstation 7. The following link fixed it: (the post by dmadden)

I've since installed ESXi since this will be a permanent install (also got the NUMA CPU error). Oddly enough, NFS works fine, but iSCSI refuses to see the iSCSI targets. I can vmkping the target IP.

Decided to reboot, found out that there is no shutdown command! See here:

Thank goodness for the fast reboot times of ESXi.

Some ESXi commands related to iSCSI:

esxcli nmp device list
esxcfg-swiscsi -e
esxcfg-swiscsi -s

Update: I'm just retarded. My iSCSI issues lay in the fact that I'm going through another adapter, courtesy of VMware Workstation. Another adapter, that I configured with an IP address. You know...the same IP address I set on the ESX virtual machine.

At any rate, I've run into more issues...whereas before ESX would boot my old VMs, I now cannot create a x64 VM at all, due to VT somehow not working correctly.

Update 2: Actually...if I'd just read the release says explicitly that you can only run 32-bit guests inside ESX inside Workstation. Sheesh. Well don't I feel silly. First time release notes have been worth something! I'll probably just run everything as VMs in Workstation at this point.

Update 3: Yeah, this won't work. Can't connect to the iSCSI network now! Dagnabbit. I am now officially out of luck. Can't install the 8TB array in this machine even if I wanted to...I'd need a board with 1 x8 and 2 x16 slots. Honest to goodness.


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…