Hi, In my environment have four hosts with the ESX Server 3.0.2, building July 2007. My infrastructure support HBA, SAN, fiber optic network and Gigabit. When saw the exchange of Firewall and implemented the function of the accelerator TCP / IP network is now out packages (size). At the site of VMware identified a patch for the ESX Server version 2.5 - http://www.vmware.com/support/esx25/doc/esx-253-200606-patch.htmI suppose that the ESX Server version 3.0.2 had already been incorporated into the correction made in version 2.5. I correct? Any additional patch to be applied? Not found in patches download version 3.0.2 ESX Server description of the problem of network - discard packages ethernet frames.
Help is welcome. Thank you / Bed

• - - - - - - - -

"MAC0 IP" Error on NP2 hardware

Some or all network interfaces appear to drop certain packets from specific applications, such as VMWare ESX

clusters and Nortel Alteon application switches.

The "MAC0 IP Error" counter for the network interface may also increment, which you can view using the following

diagnostic CLI command:

1. diag hardware deviceinfo nic AMC-SW1\/1

Driver Name: NP2
Version: 0.92
.
.
.
MAC0 IP Error: 231

This issue only affects Fortinet products with NP2 hardware accelerated network interfaces.

Components

* FortiGate-3016B, FortiGate-310B
* FortiGate-ASM-FB4, FortiGate-ADM-FB8 and FortiGate-ADM-XB2 AMC modules

Steps or Commands

This issue occurs when network applications produce frames not conforming to the IEEE 802.3 3.2.7 specification.

According to that specification, if padding has been applied in an Ethernet frame, the length of the frame should

be exactly 64 bytes, the minimum frame length for Ethernet. Frames that both are longer than the minimum frame

length and contain padding are not conforming to the specification, and are therefore dropped by NP2 interfaces.

Typically, you might observe this issue with TCP SYN or SYN-ACK signals, where frames require padding. UDP packets

are generally not affected, as the packet is greater or equal to minimum frame length, and therefore does not

require padding to meet the minimum frame length.

Network applications known to produce non-conforming frames include:

* VMware ESX clusters running 3.01, 3.02

There is a patch available on VMware's web site for older code versions:

http://www.vmware.com/support/esx25/doc/esx-253-200606-patch.html

Summary :
...

This patch refines runt-packet padding behavior in order to accommodate relatively rare circumstances where

Ethernet frames are dropped and/or flagged as suspicious by a network security appliance.
...

http://kc.forticare.com/default.asp?SID=&Lang=1&id=3659