- Community Home
- >
- Servers and Operating Systems
- >
- HPE BladeSystem
- >
- BladeSystem - General
- >
- Tunnel mode, NIC teaming, Windows - same MAC on al...
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
Forums
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
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
08-23-2011 11:14 AM
08-23-2011 11:14 AM
Tunnel mode, NIC teaming, Windows - same MAC on all NICs
Michael had a customer question:
*********************
Hello experts,
A customer is using VC Tunnel mode with a tagged network to support multiple VLANs needed for ESX and bare-metal WS 2008 in the same enclosure. ESX is a non-issue; works great. The Windows servers use HP NIC Teaming, and a new NIC pair is created for every VLAN. That, too, works fine and system administrators are happy.
The problem is that all the Windows NIC Teams (one for each VLAN) reference the same MAC address. This causes lots of SQL Cluster validation errors as SQL sees multiple NICS with the same MAC. DBAs are not happy, as they say they cannot install SQL server with failed validation tests.
Question: Is there any way in this scenario to have a unique MAC for each VLAN team? Anyone have a similar scenario and know of a clever workaround?
***********************
From Robert:
****************
To my knowledge, there is no way to generate virtual mac addresses from the Network Configuration Utility (NCU). NCU creates miniport adapters when teams and subsequent vlans are created. Each Vlan assumes the mac addresses of the physical adapter it is associated with. This should not cause an issue, as mac duplication is only an issue at layer 2. As long as the mac addresses are not duplicated in the same broadcast domain, you should be fine.
******************
Any other comments or suggestions on this problem?