Creating a Windows Server 2012 Failover Cluster - Clustering and High-Availability - Site Home - MSDN Blogs

Creating a Windows Server 2012 Failover Cluster - Clustering and High-Availability - Site Home - MSDN Blogs:

'via Blog this'

VMware KB: Broadcom 5719/5720 NICs using tg3 driver becomes unresponsive and stops traffic in vSphere

VMware KB: Broadcom 5719/5720 NICs using tg3 driver becomes unresponsive and stops traffic in vSphere

Allow ICMP though Windows 2008 r2 firewall

By default the Windows 2008 r2 firewall blocks PING / ICMP, this command can used to allow ICMP through the windows firewall via an elevated command prompt.

netsh advfirewall firewall add rule name="All ICMP V4" protocol=icmpv4:any,any dir=in action=allow

Firmware updates for Dell servers running ESXi

Here are good step by step video demo of how to apply updates from USC repository manager and from USB key:

Dell Repository Manager - Creating a Bootable ISO

http://en.community.dell.com/techcenter/m/videos/20098390.aspx

If you want to update all components and don’t have internet access (to access ftp.dell.com) you can download the whole repository on a USB device.

Updates using USB with Lifecycle Controller

http://en.community.dell.com/techcenter/systems-management/w/wiki/updates-using-usb-with-lifecycle-controller.aspx

Dell OMSA LiveCD download for ESX firmware patching

When you need to apply firmware update to a Dell server and the Life Cycle controller isn't playing ball or the server doesn't have a Life Cycle Controller you can download and use the Dell OMSA LiveCD. It's a bit bloaty for a firmware update platform.

http://linux.dell.com/files/openmanage-contributions/

7.1 seems to be the latest.

http://linux.dell.com/files/openmanage-contributions/omsa-71-live/OMSA71-CentOS6-x86_64-LiveDVD.iso

Dell PowerConnect 7024 stack reload time

It took 01:33 for traffic to start flowing over the stack after a reload. Usefull for calculating outages in iSCSI environment.

Some thoughts on interrupt moderation

Most 1GbE or 10GbE Network Interface Cards (NICs) support a feature called
interrupt moderation or interrupt throttling, which coalesces interrupts from the NIC
to the host so that the host does not spend all its CPU cycles processing interrupts.
However, for latency-sensitive workloads, the time that the NIC delays the delivery
of an interrupt for a received packet or for a packet that has successfully been sent
on the wire, is time adding to the latency of the workload.
Most NICs also provide a mechanism, usually with the ethtool command, to
disable interrupt coalescing. VMware recommends to disable physical NIC interrupt
moderation on the VMware ESXi™ host as follows:

# ethtool -C vmnicX rx-usecs 0 rx-frames 1 rx-usecs-irq 0 rx-framesirq 0

Where vmnicX is the physical NIC as reported by the ESXi command:

# esxcli network nic list

You can verify that your settings have taken effect by issuing the command:

# ethtool -c vmnicX

Note that although disabling interrupt moderation on physical NICs is extremely
helpful in reducing latency for latency-sensitive virtual machines, it can lead to
some performance penalties for other virtual machines on the ESXi host, as well as
higher CPU utilization to deal with the higher rate of interrupts from the physical
NIC.
Disabling physical NIC interrupt moderation can also defeat the benefits of Large
Receive Offloads (LRO), because some physical NICs (such as Intel 10GbE NICs)
that support LRO in hardware automatically disable it when interrupt moderation is
disabled, and the ESXi implementation of software LRO has fewer packets to
coalesce into larger packets on every interrupt. LRO is an important offload for
driving high throughput for large message transfers at reduced CPU cost, so this
trade off should be considered carefully. Additional details are available in the
knowledge base article, Poor TCP performance can occur in Linux virtual machines
with LRO enabled: kb.vmware.com/kb/1027511.

If the ESX host is restarted the above configurations must be reapplied.