Skip to main content

New InfraDog features - VMware integration

InfraDog has a new feature being released today (Android, iOS to follow next week):

VMware integration!
I've been playing around with the final beta for the last 24 hours and have learned a number of interesting things about the new feature and the app in general.

  1. Adding the vCenter is super easy - on the management point software just add the vCenter hostnames, and it automatically picks up any attached hosts.  Push to cloud, done.
  2. Once on your device, it functions much like the regular server options, but you now have new tasks available (maintenance mode!) and an 'instances' section that populates with the VMs on that host.
  3. Clicking on a VM gives you server-like info with a few new options: remote console (view-only) and new tasks (the usual VMware soft/hard power options).
  4. I had one small UI complaint, but it turned out to be PEBKAC (PEBSAF?).  See below, because I enjoy embarassing myself in public.
From the main screen you hit 'System'.  This gives you the 'Windows Computers' and the new option 'VMware vCenter & Hosts'.  Hit the latter and you see your vCenters (greyed out) and their respective hosts (selectable).  Once you select a host, you have a new screen with the host info, instances (VMs), and tasks.

The issue: If you want to go back to the vCenter screen to select a different host, you must go back to the System menu.  Not a huge deal, but seems unnecessary.  At any rate...the extra tools you get for remote troubleshooting are 100% worth any small UI quirks.

OR YOU CAN JUST HIT THE BACK BUTTON.  You dumdum.


Moving on
Let's look at a use case that I just made up in my head: You have an application server VM that is showing as down.  Event logs are clear, no prior warning.  Can't ping it or do any usual tests.  So you browse to the VM, hit the remote console, and boom: BSOD.  Reset the VM and after the boot cycle the application is back online, giving you time to research and figure out what broke it.

As someone who likes tools...having the right tool for the job is important, but having ANY tool is even more important.  Ever tried to take a screw out with your thumbnail?  Ya, you only try that once.  Point being, you might not use the remote console option or VM tasks options every day...but just having that tool in your pocket can make a big difference.


One last tidbit
I've been told it's okay to reveal this now...  A month ago or so I was invited to a seminar InfraDog put on to detail the VMware integration.  During the evening's presentation they also showed off their roadmap and some VERY cool features.  The one I'm most excited about is AD integration because due to legacy issues our users generate a lot of lockout tickets.

Mentioned this new option to my manager and it practically sold itself - the ability to unlock accounts/reset passwords (and more) from within the app would be a huge benefit to user happiness around here.  Other things like change group membership, update info, etc will also be good tools to have in your back pocket.

Maybe they should rename the app to SwissArmyDog...


Addendum
Haha, turns out you can also modify the CPU/RAM config of a VM inside the app.  Just select a VM, then click on the CPU or RAM field.  You see usage as well as re-configure sliders.  Cool!!

I also forgot to mention vMotion...that's one of the VM tasks.  Works perfectly!

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…