We are debating whether to enable link state tracking for servers with teamed NIC to detect upstream uplink failures between switches.
If the switch the server with teamed NIC is directly connected to have multiple uplinks to different distribution switches in port-channel, the question we need answer to "Is link state tracking required"? Personally I don’t think link state tracking is needed in my scenarios with multiple redundant uplinks.
If you do NIC teaming on your server (LACP) and connect each NIC to a different stacked 3750, you now have NIC redundancy and switch redundancy. I tested this with 6500 VSS and it works really well. When we pulled one link from the switch. The traffic used the other NIC going to the other switch without loosing a ping. You do not need any link state tracking at all.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...