I am excited for the release of vSphere. Hopefully soon (very very soon) I will get some more knowledge on the topic so I can then relay my knowledge to the all of you. Although, I really won’t be able to say anything new from what is already being written until I can play with the software for a while.
I need a Notepad by the Shower
I am working on another blog post and the other day in the shower I had a perfect point to make in the post. Well you can tell from the subheading the idea is gone. I hope if I force myself to work on it the idea will spring back to my mind.
I have a job! Some may know via twitter and facebook, but I will rejoin the ranks of the employed next week.
I am excited to be going to a great place where I will learn a ton about Virtualization and Storage in the Datacenter.
So if you are in the Atlanta area make sure you find me. The family and I hope to be there by the end of May.
Next in the order of commands is esxcfg-hwiscsi. This command according to the iSCSI SAN configuration guide will let you set certain settings as required by your SAN on your hardware iSCSI HBA.
esxcfg-hwiscsi -h – this is the help. Not a ton there but enough.
esxcfg-hwiscsi -l – lists the current settings.
esxcfg-hwiscsi -a – allow arp redirection on the HW iSCSI HBA. This is used be some sans to move traffic between ports.
esxcfg-hwiscsi -j – Will enable a jumbo frame (MTU 9000 bytes) when it is disabled the frame is 1500 bytes.
I will bet if these settings are required you till be directed to use them be the SAN vendor or HBA vendor. IF something bizarre is happening on your iSCSI SAN with hardware HBA’s one of these might not match the SAN.
I have really forgot to keep up on my VCDX study path. So today a quick tidbit on the esxcfg-firewall command. Many of us today will use the vCenter Client to change firewall ports on the ESX. One instance where I exclusively mess with the firewall from the command line using esxcfg-firewall is when I install Dell OpenManage. I am already in the console to install the agents so I might as well open the firewall from the console too. This really applies to any kind of agent or software you add to your ESX installation. So if you find yourself already in the console why not save a step and do it from the cli?