Virtual Connect and HP A-Series switches (A5820) IRF Integration Guide

Virtual Connect module failure

VM1 has a continuous ping to its default GW 192.168.1.1. Under normal conditions, the vSwitch

hashes the traffic from this VM to the vmnic3, which is mapped to the VC2 and enters the Bridge-

Aggregation 3 interface in IRF the logical switch.

The test uses the “power off” button on OA (Onboard Administrator) to shut down VC2 to simulate

module failure.

Test Result:

 VC2 down: About one second packet loss

 VC2 up: About six seconds packet loss

(Please note: VC 3.30 will have the enhancement to reduce the convergence time to less than 1 sec

upon VC module coming up. VC3.30 is currently scheduled to be available by the end of 08/2011.)

Note:

The VC2 up event had more convergence time because the vmnic3, which is mapped to VC2, was

up. Therefore, the vSwitch started to send traffic to VC2 before VC2 was ready internally for

switching traffic.

VC2 down