This is the best design practice that I always follow by making disti to core as layer. This will avoid unncessary broadcast traffic, extension of spanning-tree protocol and its traffic to core and unecceasry processing of rlayer 2 traffic at the core. This will improve the eprformace of the core and using the routing protocl you can use load-balancing and seemless traffic fail-over.
No HSRP at core for the L3 links. As every link is configured as a separate L3 subnet, just configure the EIGRP and have all the subnets advertised using EIGRP. If you are doing intervlan routing for some vlans on core switches, then run HSRP for those vlans on the core switches.
If you are getting only L3 uplinks then just use EIGRP for routing.
so would I use hsrp on the dist switches, then have 2 layer 3 ports from each dist switch to say 2 core switches, 1 going to each for failover, then just advetise as usual on the dist and core switches ?
I like to do Layer 3 everywhere. Simply route down to the access layer. There is no HSRP to configure--all layers are routed layers. It is nice for management too--with the exception of adding downlinks for switches, you never have to configure the core/dist switches.
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 custome...