if this is your physical setup, you already have (the potential for) redundancy. From what I can tell from your drawing, all switches have redundant connections, if you have Spanning Tree enabled, that alone would take care of redundancy. You might want to configure the core switches as the primary and secondary root for your VLAN's (with the command 'spanning-tree vlan x root primary/secondary').
You could also use Spanning Tree load balancing, in order to make use of the redundant trunks, check this document:
VLAN Load Balancing Between Trunks Using the Spanning-Tree Protocol Port Priority
indeed, just start out with letting spanning tree choose the active and redundant (blocked) ports. Just make sure that your core switches are the root for your VLAN's, as described in my previous post. As for HSRP, if you implement inter-VLAN routing (on your core switches), that would indeed be an option, to introduce further redundancy into your network...
a flat network makes implementation rather easy: just connect the switches, everything will be in the default VLAN (1), and spanning tree, as said before, will take care of the redundancy. Make sure you configure the core switches as primary and secondary root for VLAN 1.
Be aware though not to put too many hosts into that VLAN, the general rule of thumb is to limit a VLAN to roughly the size of a class C subnet (254 hosts). If you have more than that number of hosts, your network might slow down, and you will eventually have to introduce additional VLAN's (and everything else involved, such as trunks, inter-VLAN routing, VTP)...
in spanning tree, one switch is always selected as the root switch for the tree, all data flows through that switch, that is why it is important to select the most powerful and most central switch as the root. In your case, these are most likely the core switches. By configuring the core switches with those commands, you influence the root selection process, and you make sure that the core switch actually does become the root...
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...