All posts by Shawn Cannon

I have been in IT since 1996. I am our Executive Senior Blogger with experience in VMware, Microsoft, EMC storage, Veeam and Dell servers. I love technology and love to blog about it!

vBrainstorm and vExpert 2014

VMware-vExpert-2014-400x57

The new class of vExperts have been announced today by VMware.  I am happy to announce that Roger Lund and myself were once again selected as vExperts.  This is a huge honor and humbling to know that our peers in the field believe we represent VMware and virtualization n a positive light.  I know that both of us are passionate supporters of VMware and the community. I am an end user of VMware products and I manage them on a daily basis.  VMware is a major part of my job and it makes my job so much easier!  The complete list of vExperts can be found at the link below.  Congratulations to everyone that was selected as vExpert 2014.  This is going to be a great year!

vExpert 2014 announcement: http://blogs.vmware.com/vmtn/2014/04/vexpert-2014-announcement.html

Welcome to the new vBrainstorm

You may have noticed some changes here at vBrainstorm. We have changed hosts and platforms with plans to bring you a better experience. The changes are not complete as the theme may change but the content will continue to be what you expect from us. We are excited and hope you are as well. Roger and I have a new blog series starting very soon so stay tuned.

EMC Elect 2014 Judge

I am proud to announce on vBrainstorm.com  and vTech411.com that I was selected to be one of the judges that will choose the 2014 EMC Elect!  I was selected as EMC Elect 2013 which was the inaugural year of the program.  Some of you may be asking what the EMC Elect is.  Head on over to this site to answer that question:  https://community.emc.com/community/connect/emc_elect

I was chosen as an EMC Elect due to my community contributions to Twitter, blogs and EMC Community Network (ECN) participation.  We will be contacting all of those nominated soon and start the judging process thereafter.  Those selected as 2014 EMC Elect will be notified in January.
I am excited for this opportunity to give back to the EMC community.  I have never been a judge for anything so it will be a learning process.  It will be tough narrowing the nominations down but anything challenging is always rewarding.  If you have been nominated, I wish you good luck!  I cannot wait to help pick the next round of EMC Elect champions!

Clearing the ARP cache table in ESXi 5.5

A new feature has been added in the new 5.5 release of ESXi.  You can now clear the ARP cache on an ESXi server.  This is a very useful feature that should have always been part of ESXi.  This feature ONLY works with ESXi 5.5.  The KB article contents are below and were copied from http://kb.vmware.com/kb/2049667

Clearing the ARP cache table in ESXi 5.5 (2049667)

Purpose

This article provides information on the new esxcli command introduced in vSphere 5.5 to clear the ARP table. ESXi 3.x, 4.x, and ESXi 5.0/5.1 do not include any mechanism to clear the ARP table.

For more information, see Troubleshooting network connection issues using Address Resolution Protocol (ARP) (1008184).

Resolution

vSphere 5.5 introduces the a new esxcli network ip neighbor remove command to clear the ARP cache table.

To clear the ARP cache table in ESXi 5.5, use this command:

esxcli network ip neighbor remove [fusion_builder_container hundred_percent="yes" overflow="visible"][fusion_builder_row][fusion_builder_column type="1_1" background_position="left top" background_color="" border_size="" border_color="" border_style="solid" spacing="yes" background_image="" background_repeat="no-repeat" padding="" margin_top="0px" margin_bottom="0px" class="" id="" animation_type="" animation_speed="0.3" animation_direction="left" hide_on_mobile="no" center_content="no" min_height="none"][options]

Where options includes:

  • -i string or --interface-name=string

    Where string is the name of the VMkernel network interface from which the neighbor entry must be removed. If this option is not specified, the neighbor is removed from all interfaces.

  • -a address or --neighbor-addr=address

    Where address is the IPv4/IPv6 address of the neighbor. This is mandatory.

  • -N instance or --netstack=instance

    Where instance is the network stack instance. If unspecified, the default netstack instance is used.

  • -v number or --version=number

    Where number is the IP version and can either be 4 or 6. This is mandatory.

For example, to delete the ARP entry for address 10.131.0.103:

  1. Connect to the ESXi 5.5 host using SSH. For more information, see Using Tech Support Mode in ESXi 4.1 and ESXi 5.x (1017910).
  2. View the current ARP table using this command:

    # esxcli network ip neighbor list

    You see output similar to:

    Neighbor      Mac Address        Vmknic    Expiry  State  Type
    ------------  -----------------  ------   -------  -----  -----
    10.131.0.103  00:1c:c4:a9:6f:fc   vmk0     908 sec        Unknown
    10.131.0.179  00:1e:0b:bf:7a:50   vmk0    1062 sec        Unknown

  3. To delete the ARP entry for address 10.131.0.103, run one of these commands:
    • # esxcli network ip neighbor -v 4 -a 10.131.0.103
    • # esxcli network ip neighbor --version=4 --neighbor-addr=10.131.0.103
  4. View the ARP table again using this command:

    # esxcli network ip neighbor list

    You see output similar to:

    Neighbor      Mac Address        Vmknic    Expiry  State  Type
    ------------  -----------------  ------   -------  -----  -----
    10.131.0.179  00:1e:0b:bf:7a:50   vmk0    750 sec        Unknown

[/fusion_builder_column][/fusion_builder_row][/fusion_builder_container]