Skip to main content

VMware Workstation, ESXi VMs, and external iSCSI storage

From a post I made here:   http://communities.vmware.com/thread/342742?tstart=0


It started out simple, then got longer, and ended a saga.  The iSCSI saga.  


I would paste the whole thing here...but I'd imagine the VMware communities will be around well after this article is rendered obsolete.


Bottom line:  If your switchport is accepting tagged packets on VLAN10 only, and your physical adapter is tagging packets for VLAN10, setting the virtual machine networking (bridged to said physical adapter) to ALSO tag packets for VLAN10 will break stuff.  Leave the VLAN tagging for the physical devices.


After the saga came to a close, I then tried to add the iSCSI targets to my workstation, but ran into this:  http://www.jeremycole.com/blog/2007/11/09/the-iscsi-name-specified-contains-invalid-characters-or-is-too-long/


Yes, my naming scheme was foiled by a subtle Microsoft...oversight.  This is what the Initiator does:  (http://technet.microsoft.com/en-us/library/ee338474(WS.10).aspx)
Generates an event log if a target has a node name that is not valid. It ignores that target, and in some cases, all targets that are discovered with it (for example, if a target in the SendTargets node has an invalid node name, Microsoft iSCSI Initiator ignores all targets within the SendTargets text response). 


Found a little more 'best practice' stuff here:  http://www.cognizant.com/InsightsWhitepapers/vmware_esx_wp.pdf
Hostname Naming Convention
It is recommended that the hostname should not
contain an underscore. Labels cannot start nor end
with a hyphen. Special characters other than the
hyphen (and the dot between labels) are not
advisable, although they are sometimes used. (1)


One other tidbit: https://forums.openfiler.com/viewtopic.php?id=815
The underscore is not a legal character int he iSCSI spec and the MS initiator docs does say that invalid paths will be ignored. [sic]


I rescind my previous comment about Microsoft's insights, and I thank them for following RFCs.  


So there we have it - it's an RFC oversight...or intention.  At any rate, everything is working wonderfully, and if I didn't have underscores in the names, I'd even be able to access it from the host.


Good times!

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…