Per you drawing, this behaviour is OK since you have layer 2 links between the MRUCOLOPRODSW1 switch and MRUMADCORPSW1 switch. Try sourcing your trace from your vlan 24 interface on switch MRUCOLOPRODSW1. This trace should go through MRUCOLOCORPSW1.
What you are seeing is normal. It's simply a behavior of the ARP and CAM entries in the participating switches.
Let's do a packet walk:
1) Packet is sent to the default gateway on that segment 10.30.24.5
2) The packet is Layer3 switched over to Vlan1. You have a trunk between the 2 switches and it will list all remote MAC addresses in order. I'm pretty sure Vlan1 will be seen first. (show mac-address-table)
3) On running the traceroute again, 10.30.19.101 won't respond because your gateway knows the egress port for the destination device. Do a show arp and it will be listed in your switch. If you wait a few minutes for the ARP to timeout, you will see the same first traceroute again.
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...