Was purchased 2 Dell VRTX with the same equipment - (R1-2401, 2xM620). VRTX first went into production immediately after unpacking: installed ESXi 5.5. Update2 (VMware-VMvisor-Installer-5.5.0.update02-2068190.x86_64-Dell_Customized-A01.iso).
Within two or three days started having problems with the network: packet loss, temporary disable the internal network interfaces R1-2401.
VRTX with servers replaced with a spare. Migrated virtual machines and it worked on the new hardware without errors.
Problem vrtx servers and update the software on the latest from the site of Dell.
Switch R1-2401 f/w | 2.0.0.46 |
PowerEdge M620 (VRTX) | |
1.66.65 (Build 07) | |
Total System Memory | 32.0 GB |
Started load testing dell vrtx with a generator TCP / UDP traffic iperf. It was suggested that a number of different test configurations:
1. Server with iperf (ubuntu 14.04) is connected to the external port R1-2401 at 1 Gbit / s. Both Dell M620 installed ESXi 5.5 Update2. Iperf client part running on virtual machines c Ubuntu 14.04.
2. Server with iperf (ubuntu 14.04) is connected to the external port R1-2401 at 1 Gbit / s. On one of the Dell M620 running Windows 2012 Server, on the second M620 by ESXi 5.5 Update2. Iperf client part running on virtual machines c Ubuntu 14.04, Windows Server 2012.
3. Iperf server running on Windows Server 2012 (M620 №1), a client on a virtual machine with Ubuntu 14.04 on M620 №2. R1-2401 switch is disconnected from the external network.
Use different operating systems due to excluding the impact of drivers under Windows / ESXi.
Switch log:
31-Dec-2014 08:02:15 %LINK-W-Down: gi1/1
31-Dec-2014 08:02:15 %LINK-I-Up: gi1/1
31-Dec-2014 08:02:15 %LINK-W-Down: gi1/1
31-Dec-2014 08:02:15 %LINK-I-Up: gi1/1
31-Dec-2014 08:02:15 %LINK-W-Down: gi1/1
31-Dec-2014 08:02:15 %LINK-I-Up: gi1/1
31-Dec-2014 08:02:16 %LINK-W-Down: gi1/1
31-Dec-2014 08:02:16 %LINK-W-Down: gi1/2
31-Dec-2014 08:02:16 %LINK-I-Up: gi1/1
31-Dec-2014 08:02:16 %LINK-I-Up: gi1/2
31-Dec-2014 08:02:16 %LINK-W-Down: gi4/1
31-Dec-2014 08:02:16 %LINK-W-Down: gi4/2
31-Dec-2014 08:02:16 %LINK-I-Up: gi4/1
31-Dec-2014 08:02:16 %LINK-I-Up: gi4/2
31-Dec-2014 08:02:17 %LINK-W-Down: gi4/1
31-Dec-2014 08:02:17 %LINK-W-Down: gi4/2
31-Dec-2014 08:02:17 %LINK-I-Up: gi4/1
31-Dec-2014 08:02:17 %LINK-I-Up: gi4/2
31-Dec-2014 08:02:17 %LINK-W-Down: gi4/2
31-Dec-2014 08:02:17 %LINK-I-Up: gi4/2
31-Dec-2014 08:02:17 %LINK-W-Down: gi4/2
console#sh interfaces counters GigabitEthernet 1/1
Port InUcastPkts InMcastPkts InBcastPkts InOctets
---------------- ------------ ------------ ------------ ------------
gi1/1 799019045 2265 4110 115722558417
2
Port OutUcastPkts OutMcastPkts OutBcastPkts OutOctets
---------------- ------------ ------------ ------------ ------------
gi1/1 483922423 1230188 943567 583945537894
Alignment Errors: 0
FCS Errors: 4
Single Collision Frames: 0
Multiple Collision Frames: 0
SQE Test Errors: 0
Deferred Transmissions: 0
Late Collisions: 0
Excessive Collisions: 0
Carrier Sense Errors: 0
Oversize Packets: 0
Internal MAC Rx Errors: 13718
Symbol Errors: 0
Received Pause Frames: 0
Transmitted Pause Frames: 0
Question: What can fail in this situation?