Guys, thanks for the replies
First of all I should say that the FlexFabric environment concerned is on a customer site and I'm not there at the moment, however I can ask guys down there to run tests.
I have a similar type of config (with respect to SUS / network assignment) running on my own Flex-10 kit and the same failover tests work fine for me. For example if I perform a module reset in OA:
1) on my (Flex-10) kit I lose no more than one or two pings to blades, whilst failover takes place, if I reset the module carrying the active SUS uplink. If I reset the module carrying the standby SUS uplink I see no pings lost at all
2) on the customer (FF) kit if I reset either module all pings are dropped for approximately 70 seconds until the reset module becomes available again
The only difference between my deployment and the customers (other than the fact that its Flex-10 vs FF) is that I am pinging ESXi hosts and the customer is pinging Windows 2008 R2 hosts.
I have asked them to build some ESXi blades meanwhile so we can determine if this is host OS specific - if it is then this points towards an issue with Windows / HP NIC teaming driver rather than VC itself.
I asked the customer to perform a NIC failover by changing the NCU NFT preference yesterday and although a handful of pings were dropped in this process (more than I would expect) the traffic could be made to pass through both modules. Also we could fail the SUS uplinks between the modules.
Interestingly if we power off both VC modules and then bring one of them online, everything works normally. It's only when we are running with two modules - and we remove one of them - that the whole thing crashes.
To confirm the NIC / network configuration we have one shared uplink set with active/standby links comprising a 4x10Gbps LACP port group from each module. We have defined one ethernet network, associated it with the SUS, and created a simple server profile with 2xEthernet ports and 2xFCoE ports. The ethernet ports (1a / 2a) are associated with the single ethernet network.
As stated connectivity works exactly as expected both between blades and in/out of the VC domain (pinging to/from gateway for example) and we can fail over server NICs and SUS uplinks to prove that both modueles are passing traffic. The minute we drop a module ALL communication fails. The same test on my seperate Flex-10 environment results in seamless failover.
