HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
BladeSystem Virtual Connect
Showing results for 
Search instead for 
Did you mean: 

Issues with Vshpere Virtual Server (Lync Client not logging on) / Virtual Connect / LACP /

Occasional Collector

Issues with Vshpere Virtual Server (Lync Client not logging on) / Virtual Connect / LACP /

Hi guys,


Issue: Lync client on Virtual Dektop on ESX host not being able to log on when using LACP on the HP virtual connect module i.e. 2 Uplinks to the Virtual Connect Modules.  


Design: in this C7000 Chassi, we have half height blade servers, two 10 GB virtual connect modules, 2 LACP (20 gig each) , shareduplinksetA (bay1) & shareuplink set (bay2), all the networks/vlans are mapped to both SUS’s


Each ESX has 6 FleNics assigned – 3 teams,

 1. Vmotion

2. Management

3. Multiple Networks (VLANs being mapped to this)


We are having a very strange issue where when we remove/disable one of the uplinks on Cisco Nexus Switch which forms the LACP – the Lync clients works straight away i.e. logs in.


When we have both uplinks enabled, it seems – the route is not being found/returned.


We have been in discussions with the Cisco guys, VMware guys, HP Guys and still struggling to establish, why this could be happening with 2 uplinks and not with 1.


Has anyone comes across a similar issue? Or could someone with their experienced / trained eye spot something basic we might be missing?


This is affecting only some of the VLAN’s (which the network team calls routed VLAN’s); also if the client is on the same network / VLAN of the lync server we do not experience this issue.


Guys any help / pointers would be useful.


So basically


VM à Portgroupà DVswitchà 2 NIC’s from half height Blade (Team)à Server Profile (Mutiple Networks) 1 from SUS_A & 1 from SUS_B à


SUS_A = Bay1 – Virtual Connect – 2 x 10GB (LACP) à Cisco Nexus (cross switch Vpc)àf5 load balancer à Lync Server


SUS_B = Bay 2 –Virtual connect – 2 x 10 GB (LACP) à Cisco Nexus  (cross switch Vpc)à f5 load balance à Lync Server




Frequent Advisor

Re: Issues with Vshpere Virtual Server (Lync Client not logging on) / Virtual Connect / LACP /

What LACP mode are you running in and what load balancing method is being used?

VC for Cisco Admins on page 18 talks about LACP load balancing and which work with VC.