- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Issues with Vshpere Virtual Server (Lync Client no...
Categories
Company
Local Language
Forums
Discussions
Forums
- Data Protection and Retention
- Entry Storage Systems
- Legacy
- Midrange and Enterprise Storage
- Storage Networking
- HPE Nimble Storage
Discussions
Discussions
Discussions
Forums
Discussions
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
- BladeSystem Infrastructure and Application Solutions
- Appliance Servers
- Alpha Servers
- BackOffice Products
- Internet Products
- HPE 9000 and HPE e3000 Servers
- Networking
- Netservers
- Secure OS Software for Linux
- Server Management (Insight Manager 7)
- Windows Server 2003
- Operating System - Tru64 Unix
- ProLiant Deployment and Provisioning
- Linux-Based Community / Regional
- Microsoft System Center Integration
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Discussion Boards
Community
Resources
Forums
Blogs
- Subscribe to RSS Feed
- Mark Topic as New
- Mark Topic as Read
- Float this Topic for Current User
- Bookmark
- Subscribe
- Printer Friendly Page
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
03-16-2013 05:34 AM
03-16-2013 05:34 AM
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
Thanks
- Tags:
- LACP
- Virtual Connect
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
04-02-2013 01:26 PM
04-02-2013 01:26 PM
Re: Issues with Vshpere Virtual Server (Lync Client not logging on) / Virtual Connect / LACP /
VC for Cisco Admins on page 18 talks about LACP load balancing and which work with VC.
http://h20000.www2.hp.com/bc/docs/support/SupportManual/c01386629/c01386629.pdf
I work for HPE