Good morning,
We are working in a project where we need to connect a WinCC OA server to 2 different switches. Using NIC teaming would be a preferable option but I've noticed in the manual that WinCC OA does not work with NIC teaming. Could you explain this further please? What would be the issues we would encounter if we used NIC teaming with a WinCC OA server?
regards,
Dimitris
NIC teaming
- leoknipp
- Posts:2928
- Joined: Tue Aug 24, 2010 7:28 pm
Re: NIC teaming
If you want to use a redundant network connection between machines where WinCC OA processes (for 1 project) are running you can configure redundant network connections in WinCC OA.
NIC teaming is officially not supported because for NIC teaming you need specific hardware and there are no tests made at ETM for NIC teaming networks.
Best Regards
Leopold Knipp
Senior Support Specialist
NIC teaming is officially not supported because for NIC teaming you need specific hardware and there are no tests made at ETM for NIC teaming networks.
Best Regards
Leopold Knipp
Senior Support Specialist
- gschijndel
- Posts:376
- Joined: Tue Jan 15, 2019 3:12 pm
Re: NIC teaming
leoknipp wrote: ↑ Mon Sep 28, 2020 12:03 pmNIC teaming is officially not supported because for NIC teaming you need specific hardware and there are no tests made at ETM for NIC teaming networks.
Microsoft has introduced NIC teaming with Windows server 2012 and works with general hardware. It can even be used without configuring switches for this (switch independent). NIC teaming seems to be a way to share a single IP address with multiple network interface cards. I do not think NIC teaming works with redundant independent networks.
I guess they want to use the switch independent NIC teaming option, since they want to connect to 2 different switches.
.
Could you elaborate on with which NIC teaming option these problems occurred?leoknipp wrote: ↑ Mon Nov 27, 2017 10:11 amIn the past some problems occured when using NIC teaming and the project configuration must be modified.