You will need to SSH into the host to perform these commands.
This is the basic syntax
vmkping -4 -d -I <vmk-number> -s <packet-size> <address> This is an example using vmk3 and vmk4, which we will assume is used for storage. We will use a packet size of 8400 bytes (can’t use 9000 b/c there won’t be enough room to allow for IP overhead) We will assume 192.168.1.10 is the address of the storage interface vmkping -4 -d -I vmk3 -s 8400 192.
Stay tuned for more content as I continue to migrate posts from my old blog (vMotioned.com) over to this one. In short, I’m migrating away from a Wordpress hosted platform over to Hugo, hosted on GitHub.
I’m also going to try to add some fresh content, once the migration is complete.
As part of a new initiative, of sorts, I wanted a way to record daily accomplishments, which is something that I have thought about doing for quite some time, but never got enough motivation to actually do anything about it. That said, I decided to revisit, take action and come up with some requirements on what a workable solution would look like (for me):
It needs to be easy to record entries (if it’s hard or cumbersome, it won’t have sustainability) It needs to fit into my daily workflow The format needs to be somewhat open/easy to move between different platforms (Mainly Windows & Mac OS) If possible, pick a solution that can sharpen a skill-set, in the process Given each of those, my final solution ended up being quite simple: GitHub and GitHub Flavored Markdown (GFM) files.
Recently, I was called in to help a client out with a vCenter 5.1 install and came across the somewhat common issue of being locked out of vCenter (which is most common after the upgrade process). After some investigation, it appeared the proper Identity Sources were configured and SSO, in general, looked okay. After scratching our heads a bit, I decided to take a look inside the vCenter DB and verify account/group access.
This is a recent HTML Disk Space report that I created which outputs a generic HTML report that contains server disk/partition space details. I schedule it to run weekly, but obviously you can use as you wish. In short, in reads in a list of servers from a text file, queries WMI for disk space detail, uses some expressions to format and calculate the space and then outputs the results into a report, sorted in ascending order by the percent of free space, per partition.
A while back I created a note about how to fix the slow mouse issue that sometimes happens even after installing VMware tools on a Server 2008 guest. The process is as follows:
1. Make sure VMware tools is up to date
2. You may need to update the VM hardware versions if this fix does not work.
3. On the guest, open up the device manager and expand the Display adapters.
An often overlooked and less prioritized thought in vSphere environments is backing up the actual host configuration. I figured it was worth a quick post, given the fact that it’s a fairly simple process via PowerCLI. This command should be the same for all versions of vSphere/PowerCLI, but I have only tested on 4.1-5.1.
Aside: This is just the basic command; there are plenty of other ways to automate this or use it in conjunction with another PowerCLI script; I’ll leave that up to you.
I got real sick and tired of the left click getting stuck in my MBR Align guest, midway through a vmdk alignment. While I did see some fixes, all I really needed was SSH enabled so I could run the necessary utilities from the command line.
To enable SSH on the MBR Align Suse VM, do the following:
Open the shell
Enter the below command:
sudo /etc/rc.d/./sshd start Thats it; done.
I have been meaning to post something about this for a little while. When deploying the Nexus 1000v, don’t forget to set the ‘Max-Ports’ setting for each of your port-profiles. By default, the 1000v sets each port-profile up with only 32 ports. This presents a problem, for example, when you try to deploy your 33rd guest and you get an error that says that you are out of virtual ports. Not to worry, the fix easy and non-disruptive to anything already running in your environment.
When using or scripting anything from the PsTools suite it can sometimes be an inconvenience to have the EULA appear the first time you run any given tool on a system. In order to avoid this, simply append the /accepteula switch to your command and it will automatically accept and allow the script/command to run.