1. If you are talking about NLB like HP Teaming for network card on a server, then it depends on what you have setup on the server. If it's load balancing or failover redundancy. You can either connect both interfaces into same VLAN, or you can create etherchannel for those ports.
2. If you are talking about Cluster solutions, that use same MAC on both interfaces, than the only way I know of to cleanly solve the problem is to create a separate VLAN for that cluster. The rule is that no two same MAC addresses can exist on two ports (for unicast) therefore, switch creates a "virtual" MAC for the ports, that does not exist in reality. That means that all packets that go to the cluster are broadcast to all hosts in the VLAN. Since VLAN separates broadcast domains, one VLAN per server cluster is the cleanest sollution. Maybe a bit harder from administration point of view.
We use HP Teaming for network card on a server for failover redundancy with two cisco 3020, we connect both interfaces in the same VLAN, but when we use NLB unicast mode it isn't work properly, we haven't answer if we ping to other host or default gateway from inside the server but dedicated IP or virtual IP its respond ok, what can we do?
We are pleased to announce availability of Beta software for 16.6.3.
16.6.3 will be the second rebuild on the 16.6 release train targeted
towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are
looking for early feedback from customers befor...
Introduction Featured Speakers Luis Espejel is the Telecommunications
Manager of IENova, an Oil & Gas company. Currently he works with Cisco
IOS® and Cisco IOS XE platforms, and NX to some extent. He has also
worked as a Senior Engineer with the Routing P...
In this session you can learn more about Layer 3 multicast and the best
practices to identify possible threats and take security measures. It
provides an overview of basic multicast, the best security practices for
use of this technology, and recommendati...